Where Does KMReader Store Servers and Downloads?
KMReader Komga client servers, offline policies and progress sync on Apple devices.
Last updated
KMReader is a native Komga vault for iPhone, iPad, Mac and TV: saved servers (password or API key), per series offline policies (manual, latest, all) and reading state in app storage with iCloud assisted sync. The Komga host stays the master library.
Offline policies decide what survives without signal. Downloads run in the background with Live Activity on iOS, and progress syncs back in real time or queues while offline. Admin tools (metadata edits, scans, metrics) act on the server, never on local files.
Where KMReader stores this, by platform
App sandbox and iCloud (servers, offline policies and cache)
Add servers by URL with password or API key; HTTPS preferred outside LAN. Per series policy controls what stays downloaded. Incognito mode keeps progress off the server when wanted.
App sandbox and iCloud (Mac native build)
Same vault and reader as iOS with DIVINA and EPUB readers, custom fonts and external display support. Three tier caches (pages, books, thumbnails) with adjustable limits and auto cleanup.
Frequently asked questions
how do I keep a series offline in KMReader
Open the series and set its offline policy: manual for handpicked books, latest for new arrivals, all for the full run. Downloads continue in the background; read lists and collections stay available too.
do KMReader downloads sync between devices
Policies and progress sync; the downloaded pages do not transfer directly. Each device fetches its own copies under the same policies. The Komga server holds the canonical read state.
Notice an outdated path? Let us know.