Skip to content

Instantly share code, notes, and snippets.

@infyProductions
Created May 11, 2026 01:17
Show Gist options
  • Select an option

  • Save infyProductions/e7fdc41f1b1fffdec566d25e0b6bc84d to your computer and use it in GitHub Desktop.

Select an option

Save infyProductions/e7fdc41f1b1fffdec566d25e0b6bc84d to your computer and use it in GitHub Desktop.
How to convert a Mihon backup file using Nekotatsu-mobile

Kotatsu Mobile conversion guide

Requirements:

  • Nekotatsu Mobile
  • A Tachiyomi/Mihon backup file (ends in .tachibk or .proto.gz)

Installing and Configuring Nekotatsu Mobile

  1. Download the latest Nekotatsu mobile release here and install it just like any android app.
  2. Tap the Cog (⚙️) on the top left and tap Settings.
  3. For the "Tachiyomi Sources URL", you can keep the default (which used the Keiyoushi extension repo) or any other extension repo that ends in index.min.json.
  4. For the "Kotatsu Parsers URL", you can use either the following:

Tip

You can long tap (or right-click) the hyperlink and tap/select Copy link in order to be copied on the clipboard.

  1. You can keep the "Fixer Script URL" by default.
  2. Don't forget to tap "Save" at the bottom...

How to Convert a Mihon backup to a Kotatsu compatible one:

Note

If you're on the "Settings" page still, you can go back to the main screen by tapping the Cog (⚙️) on the top left and tap "Convert".

  1. Tap "Pick Backup" and select the Tachiyomi/Mihon backup you've just created. The file extension must end in either .tachibk or .proto.gz.
  2. Then tap the "Pick Save Path" and select the place where to put the resulting Kotatsu compatible backup file (usually ends in .zip).
  3. Tap "Convert" to save the file.

How to load the newly created backup and restore it

  1. Tap the three-dots on the top right and tap on Settings.
  2. Then tap on "Backup and Restore" and "Restore from backup".
  3. Select the newly converted backup file and finally tap "Restore" from the "Restore from backup" screen.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment