Short answer: Mihon and Doki are not versions of each other. Mihon continues Tachiyomi: community extension repositories, .tachibk backups, and the largest support ecosystem. Doki continues Kotatsu — an independent reader with its own built-in source-parser approach — after the Kotatsu repository was archived. Pick Mihon for ecosystem and migration tooling; pick Doki if you are a Kotatsu user who wants its line to continue.
| Mihon | Doki | |
|---|---|---|
| Lineage | Tachiyomi successor (same team members) | Kotatsu successor (DokiTeam) |
| Sources | Extensions you install from repositories | Kotatsu-style built-in parser system |
| Backups | .tachibk, shared with the whole fork family | Its own system; no .tachibk interchange |
| Releases | Versioned releases, latest v0.21.2 | Repository-led; check GitHub for current builds |
| License | Apache-2.0 | GPL-3.0 |
For Kotatsu users, specifically
Your app is archived software now — still runnable, no longer maintained. Doki is the intended continuation (background in our Kotatsu → Doki explainer). If instead you are considering a jump to Mihon, know what does not transfer: source lists and in-app data are not backup-compatible across the families. A tracker account (AniList/MyAnimeList) is the bridge — sync your list, then rebuild in the new app with the tracker as the map.
For new readers
Start where the documentation and community are: Mihon. The extension-repository model means more sources, more guides, and forks (SY, AZ, J2K, Komikku, Yokai) that all read the same library if you ever switch. Doki’s appeal is real but narrower: Kotatsu’s design, continued.
Downloads: Mihon from GitHub via our Mihon page (with hashes); Doki from the DokiTeam GitHub repository.
Related: all comparisons · server software compared