Skip to content

KOReader For Readers Who Want Open-Source Formats

KOReader For Readers Who Want Open-Source Formats

KOReader on Android: F-Droid vs GitHub APK update realities, manual book-folder storage setup, and optional progress sync—not automatic cloud.

App summary

App
KOReader
Developer
KOReader contributors
License
AGPL-3.0-only
Version
unknown
Size
unknown
Price
Free

KOReader Android Without Google Play: F-Droid vs GitHub APK Update Reality

If you search for KOReader on the Play Store and come up empty, that is not a mistake on your end. The project distributes its Android build mainly through F-Droid and through APK releases on GitHub. Its official site is koreader.rocks, and that is where you should start. There is no store listing in the documented distribution path, and the app is free either way.

The practical cost of that choice shows up later, at update time. F-Droid users get updates through the F-Droid client, the same way they get updates for anything else in that catalog. GitHub APK users generally download a new APK and install it over the old one. Neither path is hard, but neither is the “open the store, tap update” loop most Android users have been trained on.

What I cannot tell you is which version you will get or how large the download is. The fact data marks the latest stable version number and the APK download size as unknown. That matters more than it sounds: without a version number, nobody can tell you whether a specific bug was fixed in the build you are about to install. Check the project’s own release notes rather than trusting a number quoted in a review, including this one.

Pick one channel and stay on it. Mixing an F-Droid install with a GitHub APK sideload is a reliable way to end up with two installs, confusing update prompts, or a version you did not intend. If automatic updates matter and you do not want to think about it again, F-Droid is the closer fit. If you want the newest build the moment it lands, GitHub releases are the other documented option. People who expect the Play Store to handle this for them are simply outside KOReader’s documented Android path, and no amount of hoping changes that.

KOReader Android Storage Access: Why Book Folders May Need Manual Setup

Storage is where Android’s own rules start to matter more than the app’s feature list. KOReader is an Android app, but the fact data does not state a minimum supported Android version. That single omission has a real consequence: nobody can say from the documented facts how the app behaves under Android 13’s storage model, because we do not know which Android releases it officially targets.

The fact data also does not describe storage permissions, folder access, or how the app interacts with the Storage Access Framework. So if your books do not appear after install, I am not going to hand you a five-step fix and call it verified. The honest answer is that the documented facts stop short of that, and the right move is to check the project’s own documentation at koreader.rocks rather than apply a workaround copied from a forum post.

What the fact data does support is a general expectation of setup friction. Some KOReader features require network access and manual configuration. An app that expects you to configure things is an app that may also expect you to point it at your library rather than scan your whole device. That is consistent with its profile, not a contradiction of it.

A reasonable approach: keep your books in one folder you can identify, install the app, and see what it can see before you start moving files around. If the folder is invisible, treat it as an unresolved question and go to the official documentation. Do not assume a permission toggle you read about applies to your Android version, because the fact data does not confirm which versions are in scope.

KOReader Progress Sync: Optional Manual Setup, Not Automatic Cloud Sync

The most common wrong assumption about KOReader is that it syncs your place in a book the way a Kindle app does. It does not work that way by default. Progress sync is an optional feature, and the fact data describes it as optional progress sync — not an account-backed cloud service that switches on when you install the app.

That distinction matters because there is no account. KOReader requires no account, and its optional network features contact external services only when you enable them. So sync is something you turn on and configure, not something that quietly happens in the background tied to an email address.

The specific mechanics of cross-device sync, including how to set up sync between an Android phone and a Kindle, are not specified in the fact data. I am not going to invent a server address or a menu path. What can be said is that the setup is manual by design, and that anyone promising a two-tap Android-to-Kindle sync is describing something the documented facts do not support.

Treat sync as a project you opt into. If you read on one device, ignore it entirely; nothing breaks. If you read across devices, budget time for configuration and expect to consult the official documentation. The same logic applies to connecting to a Calibre library over Wi-Fi: the fact data does not cover that workflow, so any instructions you follow should come from the project itself, not from a review.

Skip KOReader If You Need DRM Kindle Books or Zero-Setup Reading

Let’s be direct about the boundary. KOReader supports EPUB, PDF, DjVu, CBZ/CBR, and FB2 among other formats. DRM support is not listed anywhere in the fact data. That is not the same as saying it definitively cannot open a DRM-protected file; it means the documented facts give you no basis to expect it will, and you should not install on the assumption that it does.

So if your library is mostly Kindle Store purchases or Adobe DRM-protected EPUBs, KOReader is the wrong tool and the official Kindle Android app is the right one for those files. This is not a knock on KOReader. It is a statement about what the app is documented to do.

The second boundary is patience. The interface can be complex for new users, and Android distribution through F-Droid and GitHub APK is less convenient than a store install. Those two weaknesses compound: you pay a setup cost before you read a single page, and then you meet a UI that assumes you will dig into settings.

Name the wrong audiences plainly. Readers who mainly buy DRM-protected Kindle Store books. Casual users who want zero-setup, one-tap reading. Audiobook listeners expecting built-in audiobook sync. iOS users looking for an iPhone or iPad reading app — the platform listed here is Android. People who require official commercial customer support from a vendor. And users who expect automatic Play Store updates. No ads and no account requirement are genuine advantages, but they do not turn KOReader into a one-tap replacement for the official Kindle app, and pretending otherwise wastes everyone’s time.

Format Coverage That Most Android Readers Skip

The format list is the reason many people find KOReader in the first place. EPUB and PDF are table stakes on Android. DjVu, CBZ/CBR, and FB2 are where the list gets less ordinary. If your library was assembled over years from different sources, the odds are good that some of it sits in formats a mainstream reader will not touch.

Comics are the clearest case. CBZ and CBR are archive-based comic formats, and a reader that opens them without a conversion step saves you work that otherwise happens on a desktop. Whether KOReader’s comic handling suits you is a separate question from whether it opens the file, and the fact data does not describe page-fit behavior, so judge that yourself once installed.

FB2 tends to appear in libraries built around Russian-language sources, and DjVu in older scanned technical material. I am not going to claim KOReader renders either perfectly; the fact data says it supports them, full stop. What that does mean is you can consolidate a scattered library into one app instead of keeping three readers installed for three file types.

One thing the fact data does not settle is dictionary format. The app offers dictionary and Wikipedia lookup, but whether that means Android system dictionaries, StarDict files, or something else is not specified. If dictionary behavior is a deciding factor for you, verify it against the official documentation before you commit.

Customization Depth Is Also the Source of the Complexity

Two items in the fact data sit in tension, and both are true. The reading experience is highly customizable. The interface can be complex for new users. Customizable reading and page layout is listed as a core function, which means the settings exist because the app is trying to let you shape the page, not because the developers ran out of restraint.

On a phone, that depth has a cost. A screen the size of a palm leaves less room for chrome, and every control you add has to live somewhere. The result is an app where the first session involves hunting. Users coming from ReadEra, which the fact data describes as having a simpler interface for casual reading, will notice the difference immediately.

The tradeoff is worth naming honestly. If you want to set up a page once and never think about it again, the complexity is pure friction. If you care about layout and want the app to respect your preferences rather than impose a house style, the same complexity is the feature. There is no version of KOReader that is both this configurable and instantly obvious.

One related question the fact data leaves open is stylus handwriting. Annotations, highlights, and bookmarks are listed features, but handwriting input with a stylus on a PDF is not described. Do not assume it. Test it, or ask the project, before you plan a workflow around it.

The License, the Missing Account, and What Optional Network Access Means

KOReader is licensed AGPL-3.0-only and it is free. For a reader, the license mostly matters as a guarantee: the source is open, maintained in the koreader/koreader GitHub repository, and nobody can take the app closed-source and charge you for the same code. It also means support comes from contributors and documentation rather than a support desk.

The no-account design is the more immediately useful property. There is no sign-in, no profile, no advertising identifier to argue with. For an app that opens personal documents, that is a meaningful default: your library is not tied to an identity, and there is nothing to delete when you stop using it.

The caveat is the word optional. Some features require network access and manual configuration, and when you enable them the app may contact external services. That is the documented privacy note, and it is a fair description: the app is quiet until you ask it to talk to something, at which point it talks to that something.

Practically, this means you can run KOReader entirely offline and lose nothing but sync and lookup. If you want the network features, enable them deliberately and know what you enabled. That is a healthier arrangement than an app that phones home by default, but it does put the configuration burden on you.

It Is Not a Jailbroken-Kindle-Only Tool

A persistent misconception is that KOReader exists only for hacked e-readers. The fact data contradicts that directly: KOReader is available for Android as well as e-ink devices such as Kindle, Kobo, and PocketBook. Android is a listed platform, not an afterthought port.

The e-ink lineage explains the design. An app built to run on devices with slow refreshes and physical buttons tends to favor dense menus and explicit controls over gesture-driven minimalism. That heritage is visible in the Android build, and it is part of why the interface reads as complex to someone who has only used phone-native reading apps.

The other misconception worth killing is that KOReader is a bare PDF viewer. It handles annotations, highlights, bookmarks, dictionary and Wikipedia lookup, optional progress sync, and OPDS catalog support. That is a reading environment, not a file renderer. Whether it manages a library the way you want is something to judge in use, since the fact data does not describe library management in detail.

What the fact data does not describe is jailbreak requirements for Kindle or Kobo hardware. It lists those devices as supported platforms and stops there. So the accurate statement is narrow: KOReader is not Android-only and not e-ink-only, and anyone telling you it requires a jailbroken Kindle is describing one installation route, not the app’s scope.

Verdict

KOReader is a capable free, open-source, ad-free Android reader for people who accept a manual install and update path and are willing to configure the app before it suits them. The format coverage is broad — EPUB, PDF, DjVu, CBZ/CBR, FB2 and more — and the customization depth is real. So is the complexity.

It is not for you if you buy DRM-protected Kindle books, want one-tap reading, expect Play Store updates, need commercial support, listen to audiobooks with sync, or read on iOS. Those are not edge cases; they describe most casual readers, and KOReader is not aimed at them.

The unknowns are worth repeating because they shape the decision: no confirmed version number, no confirmed APK size, no confirmed minimum Android version, no confirmed storage or sync mechanics in the documented facts. If those gaps bother you, that is information too. Start at koreader.rocks, pick one distribution channel, and go in expecting to configure.

Pros

  • Open source and free
  • No ads and no account required
  • Highly customizable reading experience

Cons

  • Interface can be complex for new users
  • Android distribution is mainly via F-Droid and GitHub APK, which may be less convenient for some users
  • Some features require network access and manual configuration
Download from the official source

The link goes straight to KOReader contributors. We do not host app files.

Open official page →

Frequently asked questions

Is KOReader free?

The recorded pricing model is Free.

What license does it use?

It is listed under AGPL-3.0-only.

Where can I download the official version?

The official link points to https://koreader.rocks/.

This article was drafted with AI assistance using official developer documentation, release notes, privacy policies, and public data, then reviewed by an editor. We do not claim lab testing. The full method is on our Review Method page.