# Kototoro: an all-Compose Android reader for manga, novels and video > Kototoro is an Apache-2.0 Android app that puts manga, novels and video behind one reader, with local OCR translation, Anime4K video upscaling and WebDAV sync. This review covers what the documentation actually specifies, how setup works, and where the design runs into trouble. **Kototoro-app/Kototoro** — Manga, Novel, and Video reader for Android. Kototoro Kototoro is an open-source Android app that brings manga, novels, and video into one reader. - Repository: https://github.com/Kototoro-app/Kototoro - Stars: 587 · Forks: 46 - Language: Kotlin - License: Apache-2.0 - Published: 2026-08-08 · Updated: 2026-08-18 · Language: en - Canonical page: https://hysenlabs.com/projects/kototoro-app-kototoro ## What Kototoro is for, and who it is aimed at Kototoro is an Android application that reads manga, novels and video in a single app. The README frames the audience indirectly: the feature list assumes you already consume all three formats and are tired of switching between them. Someone who only reads manga gains little from the video player and the Anime4K upscaling path, and someone who only watches video gains little from the CBZ and EPUB importers. The more specific audience is the reader who cares where content comes from. Kototoro does not bundle content. The disclaimer states that the application hosts and bundles zero content and that all parsing is provided by user-installed, third-party extensions and sources. That is a deliberate architecture, not a legal footnote: it means the app ships as a shell and the user supplies the sources. The README lists Mihon, Aniyomi, IReader, Legado, TVBox and Cloudstream3 extension ecosystems as supported, plus dynamic parsers, and links to named extension repositories for each. A third group is served by the translation stack. Local OCR plus machine translation runs inside the reader, which matters for untranslated manga and raw text. The README calls this local, and the documentation site has a dedicated page for it. Whether the translation models download at setup or ship with the APK is not stated in the README, so budget for the possibility that first use requires an additional download. ## How the entity system and Spaces actually work The organising idea in Kototoro is the entity. The README describes an entity system that keeps favorites, history, tracking and source projections under stable work identities. In practice this means a single work can be reached through several sources, and the app tries to treat those as projections of one entity rather than as unrelated entries. The documentation site has a dedicated page covering works, projections, duplicate cleanup and source binding, which suggests the merge behaviour is configurable and occasionally needs manual correction. Spaces sit on top of that. Kototoro ships built-in Manga, Novel and Anime spaces, and lets users define scopes filtered by content type, language and source. A Space is therefore a saved view over the entity store, not a separate library. If you follow a series in two languages, a language-filtered Space should separate them without duplicating the underlying work. Tracking is discovery-oriented rather than merely a progress export. The README lists MAL, Kitsu, AniList, Bangumi, Shikimori and MangaUpdates as supported services, and separately mentions site favorites import and synchronization for supported services. Two caveats are worth flagging. First, the README does not state which tracking services support two-way sync and which are import-only. Second, the duplicate cleanup tools exist precisely because entity resolution is imperfect; a reader with a large existing library should expect to spend time in the entity guide before the library looks tidy. ## Installing the Kototoro APK and completing the setup wizard Kototoro is not distributed through an app store in the documentation provided. The README's Start Here section says to download the latest APK from the GitHub Releases page, so installation is a sideload. Recent releases are tagged v2.0.4, v2.0.3 and v2.0.2, with v2.0.4 pushed on 2026-08-27. Because the app is sideloaded, Android will require you to allow installation from the source you use to fetch the file. The README is explicit that the in-app setup wizard should be completed right after installation. It configures GitHub mirrors, downloads core source plugins and sets content types. That ordering matters: on a network where GitHub is slow or blocked, the mirror choice is the difference between a working install and a wizard that stalls. ```bash # The README points to the Releases page for the APK: # https://github.com/Kototoro-app/Kototoro/releases # No command-line install is documented; the APK is sideloaded. ``` After the wizard, the README directs new users to the Getting Started page for detailed wizard instructions and next steps, and to Source Integrations for adding extension repositories. The extension repositories named in the README are the practical starting point. For Mihon sources it lists Keiyoushi Extensions, Yuzono Tachiyomi Extensions and LittleSurvival CopyManga Copy20; for Aniyomi sources, Kohi-den Extensions Source and Yuzono Anime Extensions; for Legado, XIU2 Yuedu; and for Cloudstream, recloudstream/extensions. Adding one of these as a repository is the step that turns an empty app into a usable one. ```bash # Extension repositories named in the README, added through the app's # source integration screen rather than from a shell: # https://github.com/keiyoushi/extensions # https://github.com/yuzono/tachiyomi-extensions # https://github.com/recloudstream/extensions ``` For local content, the README lists CBZ, EPUB, TXT, MKV and MP4 among supported import formats. A first real use is therefore straightforward: import one EPUB or CBZ file, confirm the reader renders it, then add one extension repository and open a series from it. If the second step fails, the problem is almost always the repository or the mirror, not the reader. ## Where Kototoro gets in its own way The zero-content design is the largest practical limitation. A fresh install does nothing useful until the wizard runs, a mirror responds, and at least one extension repository is added. Every failure in that chain is a failure the user has to diagnose, and the README routes those users to separate FAQ and Troubleshooting pages rather than resolving them in the app. Compare that with a reader that ships with a default catalogue: Kototoro asks more of you before the first page renders. The second constraint is the extension dependency itself. Because parsing is delegated, the app's usable catalogue is exactly as good as the third-party repositories you add. The README states plainly that the developers do not maintain or govern any extension repository. When an extension breaks after a site change, the fix has to come from that repository's maintainers, and Kototoro has no control over the timeline. The third is the entity system's own complexity. Duplicate cleanup and source binding exist as documented features because merging works across sources is hard. A user with a small library may never notice. A user migrating years of history from another reader should expect the first import to produce duplicates that need manual binding. Finally, the built-in browser advertises Cloudflare challenge bypass, with background handling credited to kotatsu-redo as inspiration. This is a moving target by nature. The README does not describe a fallback when a challenge type changes, and the acknowledgement of another project's implementation suggests the behaviour is inherited rather than independently maintained. One more boundary is worth stating: nothing in the README indicates an iOS build. It describes an Android app and the releases are APKs. ## How Kototoro differs from Mihon and Aniyomi The closest comparison is Mihon for manga and Aniyomi for anime, both of which Kototoro credits in its acknowledgements and whose extension ecosystems it consumes. The difference is scope. Mihon reads manga; Aniyomi reads manga and plays anime. Kototoro adds novels, and treats all three as first-class content types through the Spaces system rather than as a manga reader with a video tab bolted on. The second difference is the UI stack. The README claims Kototoro may be one of the first genuinely all-Compose manga, novel and video reading apps, and states that the reader and video player themselves are Compose, with legacy XML, Fragment and transitional hybrid layers largely removed. That is a claim about implementation, not about features, and it has a practical consequence: a Compose reader and player can be themed and animated as one surface, which is harder when the player is a separate view hierarchy. It also means the project carries the maintenance cost of keeping up with Compose changes across the whole app. The third difference is the media processing. Anime4K and NCNN video super-resolution, DLNA casting, and subtitle and audio track selection are built in. Neither Mihon nor Aniyomi is described in the README as offering that combination. If you watch anime on a phone and care about upscaling, that is the feature that separates Kototoro from the alternatives; if you do not, it is weight you carry. Against Legado and IReader, which are primarily novel readers that Kototoro also supports as source ecosystems, the difference runs the other way: Kototoro is a media reader that can consume their sources, not a novel reader that added images. ## Maintenance, updates and the Apache-2.0 licence The repository is not archived, and the last push was on 2026-08-27, the same date as the v2.0.4 release. The release cadence is tight: v2.0.2, v2.0.3 and v2.0.4 all landed within three days of each other in late August 2026. That pattern is consistent with a project iterating quickly on a recent major version, and it also means point releases can arrive faster than a user wants to install them. Updates are handled in-app. The README describes fast pure-Kotlin OTA delta updates using bspatch, so an update downloads a patch rather than a full APK. That reduces bandwidth on metered connections. The README does not document a rollback path, so a user who sideloads a bad build has the Releases page as the only recovery route. The project is licensed under Apache-2.0, with the copyright line reading 2024-2026 Kototoro Open Source Project. Apache-2.0 permits redistribution and modification and includes an explicit patent grant. It also requires that you keep the licence and notice files and state significant changes if you redistribute a modified build. That matters here because the app loads third-party extensions: the licence covers Kototoro's own code, not the extension repositories, which carry their own terms. The README's disclaimer adds that the developers have no affiliation with content providers and assume no liability for content accessed through user-configured endpoints. This is a description of the project's stated position, not legal advice; if you plan to redistribute a build, read the licence text and the terms of the extensions you bundle. ## Conclusion Kototoro fits Android users who already juggle a manga reader, a novel app and a video player and want one Compose-based shell with local OCR translation and WebDAV sync. It is the wrong tool if you want a store-distributed app, an iOS build, or a reader that works before you have configured anything. Before adopting it, verify three things: that the setup wizard can reach a GitHub mirror from your network, that your preferred source ecosystem has a working extension repository, and that the entity system groups your existing library the way you expect rather than fragmenting one work into several entries. ## FAQ ### What is Kototoro? Kototoro is an open-source Android app that reads manga, novels and video in one reader. It is built around Jetpack Compose, supports several extension ecosystems, and adds local OCR translation, video super-resolution and WebDAV sync. ### Where do I get the Kototoro APK? The README's Start Here section says to download the latest APK from the GitHub Releases page. Releases listed there include v2.0.4, v2.0.3 and v2.0.2. ### Does Kototoro bundle manga or video content? No. The disclaimer states that the application hosts and bundles zero content, and that all parsing is provided by user-installed, third-party extensions and sources. ### Is there a Kototoro iOS version? Kototoro is described as an Android app and its releases are APKs, so no iOS build is documented. The README does not mention an iOS target. ## Sources - [Official README](https://github.com/Kototoro-app/Kototoro#readme) - [Project repository](https://github.com/Kototoro-app/Kototoro) - [Release notes](https://github.com/Kototoro-app/Kototoro/releases) --- Hysen Labs editorial analysis, written from the project's own repository and release notes. Cite the canonical page: https://hysenlabs.com/projects/kototoro-app-kototoro