Is KMReader compatible with Komga?
Yes. KMReader works with any Komga 1.20.0 or later server, including KMServer.
Komga compatibility, migration, offline reading, and platforms.
Yes. KMReader works with any Komga 1.20.0 or later server, including KMServer.
No. Point KMServer at your existing library directories and it scans them in place. Your files stay where they are.
Yes. KMServer reuses your existing library structure; there is nothing to reorganize or re-import.
Yes. Point it at an existing komga data directory and it upgrades database.sqlite in place with byte-for-byte Flyway migrations. The Java version can still open the result, so you can switch back at any time.
Yes. KMServer speaks the same API: REST, OPDS v1.2/v2, SSE, Kobo and KOReader sync. Your existing clients reconnect without changes.
Yes. Downloaded books stay fully readable offline: pages, covers, metadata and progress are stored locally.
Yes. Progress is tracked offline first and synced to your server when you reconnect, so it follows you across devices.
Yes, on iOS and macOS, with themes, fonts, and layout controls.
Yes, on iOS and macOS.
Yes, on every platform: iOS, macOS, and tvOS.
Yes. KMReader is a native macOS app (macOS 14.0 or later) with dedicated reader windows, menu bar actions, and keyboard-first controls.
Yes. KMReader is a native tvOS app (tvOS 17.0 or later) with remote-first DIVINA reading.
Yes. Save several servers, switch between them at any time, and sign in with a password or an API key.
Yes. Every kmworks project is MIT licensed: KMServer, KMReader, and the web UI.
No. kmworks is built for the Komga ecosystem but is independent of it, and is not affiliated with the Komga project.
kmrs is the technical name of KMServer: the repository, the Docker image, and the binary are all called kmrs. The product is KMServer.