Why there is no iOS version

Tachiyomi was written in Kotlin for Android (from 2014), and Mihon continues that codebase for Android. Apple’s platform rules also make sideloaded, extension-based readers hard to distribute the way Android allows. The successor projects put their effort where the codebase lives: Android.

The independent iOS readers

• Aidoku — an open-source iOS manga reader with its own source system.
• Paperback — an iOS reader built around its own extension model.
• Mangayomi — a cross-platform reader (iOS and Android) with its own extension approach.

Note: These are independent apps, not Tachiyomi ports. Whether any of them can import a .tachibk backup differs per app and per version — check the app’s own documentation before counting on it; do not trust download sites that promise one-tap Tachiyomi migration on iOS. The reliable bridge is a tracker account: keep your list on AniList or MyAnimeList (setup guide) and your progress is portable to any reader on any platform.

The server route: read your Mihon-style library on iPhone

If what you really want is your library on your iPhone, run Suwayomi on a computer at home and open its web UI in Safari — no app install needed, and the library, extensions and progress live on the server. Self-hosted libraries such as Kavita and Komga offer the same browser/OPDS pattern for local collections (compared here).

Safety: the fake iOS download trap

Because demand exists and supply does not, “Tachiyomi for iOS” is a magnet keyword for scam pages: subscription traps, profile-install prompts, and “human verification” loops. No legitimate Tachiyomi or Mihon iOS build exists to download — if a page claims otherwise, close it. The projects’ only homes are their GitHub repositories, all Android.

Related: all forks & successors · best Android manga readers

What Suwayomi is

Suwayomi (Suwayomi/Suwayomi-Server, MPL-2.0; latest v2.4.2366, September 2026) is an independent reimplementation — it is explicitly not a fork of Mihon/Tachiyomi — that runs the same extension ecosystem from a server. You read in a browser WebUI on the same machine or anywhere on your network, and it offers OPDS feeds, FlareSolverr support for challenged sources, and backup interoperability with Mihon.

Who Suwayomi is for

• Readers who want their library, downloads and progress on a PC or home server instead of (or mirrored with) a phone.
• Big local collections: pair it with the local files approach, or compare dedicated library servers in Suwayomi vs Kavita vs Komga.
• Anyone tired of emulator workarounds for reading on a big screen.

The emulator route, honestly

You can run Mihon inside an Android emulator on a PC, and many “Mihon for PC” pages quietly mean exactly that. It works, but: the emulator itself must run Android 8.0+ for current Mihon, performance and extension behavior vary, and emulator bundles from download sites are a common malware vector. If you go this route, install the emulator from its maker’s own site and Mihon from GitHub (hashes here) — never a pre-bundled “Mihon PC installer”, which does not exist officially.

Getting started with Suwayomi

1. Download Suwayomi Server from its official GitHub releases for your platform.
2. Run it and open the WebUI it serves locally in your browser.
3. Add extension repositories inside Suwayomi the same way you would in Mihon (guide).
4. Optionally point your phone’s Mihon at the server, and keep a backup routine for the server’s data (cloud backup guide).

Related: all forks & successors · what about iPhone?

Kotatsu was never a Tachiyomi fork

A common misconception: Kotatsu did not descend from Tachiyomi’s code. It was an independent reader with its own source-parser system, which is why its catalog behaved differently from the Tachiyomi/Mihon extension world. That independence cuts both ways — Kotatsu libraries and source lists do not drop into Mihon the way Tachiyomi-family backups do. What carries over is your list itself (titles and progress), best moved via a tracker account such as AniList or MyAnimeList (tracking guide).

Doki, the successor

• Repository: DokiTeam/Doki, created in June 2025; GPL-3.0 licensed; still being worked on in 2026.
• Doki does not currently publish a simple “latest release” version the way the Mihon family does, so check the repository for its current state and builds rather than trusting version numbers on download sites.
• For Kotatsu users, Doki is the natural first stop: same lineage and philosophy, actively maintained.

Kotatsu vs the Mihon family, if you are choosing fresh

If you are not already a Kotatsu user, the choice is between Doki’s independent ecosystem and the Mihon family’s shared extension repositories and backups. The Mihon side has the larger community and the migration tooling this site documents; Doki keeps Kotatsu’s approach alive for its existing fans. Our Mihon vs Doki comparison lays out the trade-offs.

Moving off Kotatsu safely

1. Sync or export your list to a tracker (AniList/MAL) before anything else — that list is portable everywhere.
2. Install Doki from its GitHub repository and set up your sources there; or, if you are switching families, install Mihon (download) and rebuild the library with tracker links as your map.
3. Keep Kotatsu installed until the new app’s library matches — archived does not mean instantly broken, but it does mean no future fixes.

Related: all forks & successors · Mihon vs Doki

Komikku

Komikku (komikku-app/komikku) builds on the Mihon and TachiyomiSY feature base. Forks in this corner of the family iterate quickly on reader and library conveniences; because their feature lists change release by release, check the project’s current GitHub README and release notes for the exact set before choosing — that is the authoritative list, and it is where you should download from.

Yokai

Yokai (null2264/yokai, Apache-2.0) is a Mihon fork with its own release cadence — its latest stable, v1.10.2, landed in September 2026 and the repository was still active in October 2026. As with Komikku, the project’s README is the source of truth for its current distinguishing features.

Why the smaller forks exist — and when to pick one

• A big library or a specific annoyance in Mihon is often what sends readers exploring; a fork may already have fixed exactly your issue.
• Forks are also insurance: because they share repositories and backups, the ecosystem survives any single project slowing down — the lesson of January 2024.
• The trade-off is cadence and scrutiny: smaller teams ship on their own schedule and get fewer eyes. Back up before switching (guide) and the experiment is risk-free.

How they relate to the big names

Think of the family as layers: Mihon is the base (download), SY adds the largest feature set (guide), and Komikku/Yokai explore their own branches from that base. Our Android reader roundup places them all side by side.

Related: all forks & successors

How Aniyomi works

Like Mihon, Aniyomi itself ships empty: manga sources and anime sources both arrive as extensions from repositories you add. Manga reading behaves the way Tachiyomi users expect — library, categories, tracking, .tachibk backups — and anime entries get episode lists and a video player alongside. If you only read manga, stock Mihon is the leaner choice; Aniyomi earns its place when you genuinely do both.

The 2024 Sony DMCA — what actually happened

In June 2024, a DMCA notice from Sony led Aniyomi’s maintainers to remove around 200 extensions from its extension repository, as reported by TorrentFreak. Two clarifications matter: the notice hit the extension repository, not the app itself, which was never taken down; and the notice was broad enough to sweep in extensions related to legitimate services. The practical lesson for users is the same as everywhere in this ecosystem: extensions live and die at the repository level, while the app and your library (with a backup) survive.

Who Aniyomi is for

• Readers who track anime in the same habit loop as manga and want one library metaphor for both.
• Users migrating from Tachiyomi who also used separate anime apps and want to consolidate.
• Not ideal if: you want the reference reader with the fastest update cadence (that is Mihon), or the maximum manga-specific feature set (that is TachiyomiSY). Our Mihon vs Aniyomi comparison goes deeper.

Getting started

1. Back up your current library if you are migrating (guide).
2. Install Aniyomi from its GitHub releases only — never from “Aniyomi Premium” style sites; the app is free.
3. Add repositories for manga and anime extensions (repository guide — the mechanics are the same), install what you use, then restore your backup.
4. Connect trackers (AniList covers both anime and manga lists for most users — tracking guide).

Related: all forks & successors · Mihon vs Aniyomi

A quick history, because the name confuses people

AZ predates Mihon: it was a feature fork in the original Tachiyomi era, and other forks (including early SY) drew from it. After Tachiyomi ended in January 2024, AZ rebased onto Mihon like most survivors. So “TachiyomiAZ” today is best understood as “Mihon, plus the AZ team’s selection of extra features and fixes” — the same repositories, extensions and backup format as the rest of the modern family.

Who AZ suits

• Long-time Tachiyomi users who used AZ before 2024 and want the closest continuation of that experience.
• Readers who like the Mihon base but want a fork team’s curation of features gathered from sister projects (historically including J2K-style touches).
• Anyone whose device runs Android 8.0+ — older Android versions are not supported by the current line.

AZ vs the alternatives

Against stock Mihon, AZ trades the main project’s release cadence for extra bundled features. Against SY, the difference is emphasis: SY pushes its own headline features (recommendations, entry merging — see the SY guide), while AZ positions itself as a broad collection. There is no wrong answer; all three read the same libraries. Compare the philosophies in our Android reader roundup.

Installing AZ

1. Back up your library first (.tachibk guide) — and mind the 0.21.x restore window described in the migration guide.
2. Download AZ only from its official GitHub repository (az4521/TachiyomiAZ).
3. Add extension repositories (guide), install extensions, then restore your backup.

Related: all forks & successors

An independent line, not a Mihon skin

Unlike SY or AZ, J2K descends directly from the original Tachiyomi as its own fork (repository: Jays2Kings/tachiyomiJ2K) and has kept its own design language ever since. The important practical point for 2026 is that it has not been left behind by the ecosystem’s format changes: 1.8.x tracks the same new extension format and repository index format the Mihon family uses, so current community repositories work.

What defines J2K

• Interface first: a redesigned, card-based UI — 1.8.0 rebuilt it around Material 3 Expressive, which is the main reason long-time users stay.
• Modern extension support: tachiyomix 1.6 extensions and index.pb-based repositories.
• Android 8.0 minimum: the 1.8 line ended support for Android 6/7 devices. If your phone is that old, J2K is no longer an option (and neither is current Mihon — see migration notes for old devices).

Who J2K is for

Readers who liked Tachiyomi’s feel but want a fresher, more designed interface without switching ecosystems. If you want maximum features, SY (guide) goes further; if you want the reference implementation everything else follows, that is Mihon (download page). J2K sits between: curated, current, and independent.

Installing and moving over

1. Export a .tachibk backup from your current app (guide).
2. Install J2K from its official GitHub releases only.
3. Add your extension repositories, install your extensions, then restore the backup.
4. Set the reading mode per format — J2K’s reader handles manga and webtoon styles like the rest of the family (reader settings).

Related: all forks & successors · TachiyomiAZ

Where SY comes from

SY began in the old Tachiyomi era (historically derived from TachiyomiAZ) and, like the rest of the surviving family, has rebased onto Mihon. That means the modern extension ecosystem, repositories and .tachibk backups carry over: most readers moving from Mihon or Tachiyomi can restore their library and carry on. The repository is jobobby04/TachiyomiSY on GitHub — download only from there.

What SY adds over Mihon

• Recommendations built from your library and tracker data (MyAnimeList/AniList-style suggestions inside the app).
• Automatic webtoon detection, switching suitable series into long-strip reading without manual per-series setup.
• Custom categories for sources, so a wall of extensions can be grouped the way you actually browse.
• A lewd filter to keep adult covers and entries out of casual browsing.
• Enhanced EH/ExHentai support for readers who use those sources.
• Merging duplicate entries: combine the same series from several sources into one library entry with chapters from all of them — the cleanest answer to source-hopping.

Who should pick SY, and who should not

Pick SY if your library is large, you read from many sources, or recommendations drive your reading. Stay on stock Mihon if you value the fastest updates from the main project and the simplest possible app — SY’s extra surface means its releases follow its own schedule (see Mihon vs TachiyomiSY for the side-by-side). Both need Android 8.0+ in current versions.

Moving to SY

1. Back up in your current app (.tachibk guide). Mind the version window: restoring a Tachiyomi backup is smoothest while apps are on the Mihon 0.21-compatible line.
2. Install SY from its GitHub releases.
3. Add your extension repositories (guide), then restore the backup.
4. Explore the SY-only settings: recommendations, source categories, and entry merging.

Related: all forks & successors · Mihon vs SY · Komikku and Yokai