Suwayomi-Server: Running Mihon (Tachiyomi) Extensions as a Self-Hosted Manga Server

What Suwayomi-Server solves for Mihon (Tachiyomi) users

Mihon (Tachiyomi) extensions are small packages that know how to talk to a specific manga site: search it, list chapters, fetch pages. They were written for an Android app. Suwayomi-Server takes those same extension packages and runs them on the JVM, then exposes the results over HTTP so any browser or client on your network can read them.

The README is explicit that this is not a fork: Suwayomi is an independent Mihon (Tachiyomi) compatible software. That distinction matters for expectations. You are not getting the Mihon app ported to desktop. You are getting a server that loads the extension format and reimplements the surrounding features: a library, categories, automated library updates, automated chapter downloads, backups, tracking through MyAnimeList, AniList and MangaUpdates, and OPDS output at /api/opds/v1.2.

The audience is narrow but real. It is for people who read from extension sources, want the reading state on a machine they control, and are comfortable running a service. Anyone whose manga collection is a folder of CBZ files is in the wrong place; Suwayomi-Server is a source client, not a file library manager.

How the server, extensions and clients fit together

The architecture is three layers. At the bottom is the server, written primarily in Java with Kotlin in the stack (the repository topics list javalin and kotlin, and the build is Gradle via build.gradle.kts with a server module). It hosts the extension runtime, the library database, the downloader and the HTTP API.

In the middle are extensions. The README says the server installs and executes Mihon (Tachiyomi) extensions, so you get the same sources. Extensions are versioned against an Extension API; the v2.3.2243 release notes mention Extension API v1.6, which tells you extension compatibility is tied to server releases, not a frozen contract.

On top are clients. This is the part people miss. The README states plainly that you need a client/user interface app as a front-end for Suwayomi-Server. If you download the server directly from the releases page, you get a bundled Suwayomi-WebUI. Integrated clients (Suwayomi-WebUI and Suwayomi-VUI) are web apps that the server can keep automatically up to date. Other clients exist, including Tachidesk-JUI, Moku, Tachidesk-Sorayomi and a KOReader plugin, and the README files them under "potentially inactive or abandoned". Treat that list as a starting point for reading, not as a support promise.

The data flow is therefore: extension fetches from the source site, server stores metadata and downloaded chapters, client renders them. Backups are Mihon (Tachiyomi)-compatible, which is what makes migration between the Android app and this server plausible.

Installing Suwayomi-Server and running a first library update

The README offers OS-specific bundles that include the Java Runtime Environment, ElectronJS and the Suwayomi-Launcher, plus Docker, Arch Linux, Debian/Ubuntu and NixOS packages, and an advanced path of running the jar release directly. The README also warns that if a bundle for your operating system or cpu architecture is not provided, you fall back to another method, so check the releases page before assuming a bundle exists for your machine.

For a container deployment, the related searches point at Docker as a common route. The README lists Docker as one of the other methods of getting Suwayomi and does not print a full docker run command, an image tag or a port, so the exact container invocation has to come from the release assets rather than from this article. Start the container with whatever command the release page gives you, then open the port the server prints on startup in a browser.

Once the server is up, the bundled Suwayomi-WebUI is the first client to try. From there the workflow is: open the extensions section, install the sources you want, then add manga to the library. The README describes automated library updates that check for new chapters and automated download of new chapters, so the first real use is to add a title, let the library update run, and confirm that chapters appear and download. If a source returns nothing, the extension is the suspect, not the server.

For remote access, the README has a section on using Suwayomi remotely. That is a deliberate step, not the default, and it is where authentication and network exposure decisions get made.

Where Suwayomi-Server breaks down: Cloudflare, clients and extensions

The most concrete failure mode is Cloudflare. The README lists FlareSolverr support to bypass Cloudflare protection as a feature, which is an admission that some sources will not answer a plain HTTP request from your server. If you do not run FlareSolverr, those sources fail. If you do, you are adding another service to maintain and another moving part that can go stale when a site changes its challenge.

The second limitation is the client split. The server has no reading interface of its own. The README's note on features says the actual working support is provided by each front-end app, and directs you to their respective readmes. So a feature listed for the server may be unusable in the client you picked. The "other clients" list is labeled potentially inactive or abandoned, which means choosing a non-integrated client is a bet on a repository that may not keep pace with the server's Extension API.

The third is scope. Suwayomi-Server is not a tool for organizing files you already own. It has no path described in the README for importing a local CBZ collection as the primary library. If your reading is offline files, this is the wrong tool, and the maintenance cost of a Java service plus extensions plus possibly FlareSolverr buys you nothing.

Suwayomi-Server compared with Komga and Tachidesk

Komga and Suwayomi-Server are often mentioned in the same breath, and the related searches include suwayomi server vs komga. The difference in approach is the source of the content. Komga is a media server for files you already have: you point it at a directory of comics and it serves them. Suwayomi-Server fetches from extension sources and manages downloads itself. If your library is a folder, Komga is the closer fit. If your library is a set of site sources, Suwayomi-Server is.

The Tachidesk comparison is a naming question more than a technical one. The README's own repository topics include tachidesk and tachidesk-server, and several client projects still carry the Tachidesk name. Suwayomi-Server is the continuation of that line of work under the Suwayomi organization. Anyone searching for suwayomi server vs tachidesk is really asking whether the old name still applies; the repository layout and topics say the two names refer to the same project lineage.

A third option worth naming is using Mihon (Tachiyomi) on Android itself. The README documents syncing with Mihon (Tachiyomi) and Neko through a Suwayomi extension and tracker, or through the Suwayomi merge source in Neko. That is the pragmatic middle ground: keep reading on the phone, let the server do the downloading and backup.

Licence, release cadence and upgrade cost

Suwayomi-Server is licensed under MPL-2.0. That is a file-level copyleft licence: modifications to covered files must be made available under the same licence, while larger works that combine it with other code can be distributed under other terms. This is a summary of the licence identifier in the repository, not legal advice; if you plan to redistribute a modified server, read the LICENSE file and get proper advice.

The maintenance picture is active. The last push was on 2026-09-07, and the recent releases show a rapid patch rhythm around the v2.3.2243 line: v2.3.2232 on 2026-07-03, v2.3.2238 on 2026-07-05, and v2.3.2243 on 2026-07-13, with the release titles themselves carrying "Hotfix 2", "Hotfix 3" and "Fix 4". That is a project shipping fixes quickly after a feature release, and it also tells you the upgrade cost: the Extension API moved to v1.6 in that same release, so extensions and clients have to keep up.

Practically, the upgrade cost is not the server binary; it is the ecosystem around it. A server upgrade can change the Extension API, which can require updated extensions, and the integrated WebUI and VUI are designed to update automatically to absorb part of that. If you pin a jar or a container tag and stop upgrading, expect extension breakage over time. The CHANGELOG.md at the repository root is where the actual breaking changes are recorded.

Editorial conclusion

Adopt Suwayomi-Server if you already use Mihon (Tachiyomi) extensions and want the same sources on a desktop or home server with a browser front-end, automated backups and OPDS access. Do not adopt it if you want a single self-contained app, if your sources are behind Cloudflare and you will not run FlareSolverr, or if you need a manga library server that reads your own files rather than extension sources. Before committing, verify which bundle or Docker image matches your CPU architecture, confirm whether the bundled Suwayomi-WebUI is enough for your reading habits, and check the CHANGELOG.md and release notes for the Extension API version your extensions require.

Frequently asked questions

Official sources

1. Issues
2. License: MPL-2.0
3. README
4. Releases
5. Suwayomi/Suwayomi-Server on GitHub