Analytics cookies only (Google Analytics, PostHog). No ad networks, no cross-site tracking. See our privacy policy.
upstream: github.com/booklore-app/booklore (opens in new tab) · github.com/Kareadita/Kavita (opens in new tab)
Pick BookLore
If your collection is mostly ebooks and you want Magic Shelves and reviewed imports, and can accept maintenance mode.
Pick Kavita
If manga or comics matter, you want an actively developed project, and prefer the lighter, simpler install we measured (~327 MB idle RAM against ~908 MB, 1/5 difficulty).
BookLore and Kavita are both self-hosted reading servers that handle ebooks and comics, with shelves or collections, OPDS, Kobo sync and multiple users. Kavita's README leads with manga, webtoons and comics and lists books alongside them; BookLore is built around shelves and a drop-folder import. The practical difference today is project status: BookLore's README says it is entering maintenance mode, while Kavita's repository is actively developed.
BookLore's README describes "a self-hosted app that brings your entire book collection under one roof": smart shelves, automatic metadata, a built-in reader for PDFs, EPUBs and comics, Kobo and KOReader sync, OPDS and BookDrop imports. Our catalog lists a Java (Spring Boot) and Angular app with MariaDB.
Kavita's README calls it "a fast, feature rich, cross-platform reading server", serving "Manga/Webtoons/Comics (cbr, cbz, zip/rar/rar5, 7zip, raw images) and Books (epub, pdf)". It is a C# and .NET application with an Angular front end.
BookLore's README says: "BookOrbit is the next chapter of BookLore", "BookLore's official successor and the home of active development", and "BookLore is entering maintenance mode and will continue to receive occasional maintenance, bug fixes, and security updates." The repository is not archived. We have not tested BookOrbit. Our BookLore snippet pins the v2.4.0 image.
Kavita is under active development, though its README still says it "should be considered beta software until the 1.0.0 release".
Kavita's README lists collections, reading lists with CBL import, "Want to Read", smart filters, webtoon and continuous reading modes, and epub annotations and highlights. Its wiki has separate scanner sections for manga, comics and epub, so check the naming rules for your kind of files before you import.
BookLore leans on shelves, including rule-based "Magic Shelves", and on fetching covers, descriptions and ratings from Google Books, Open Library and Amazon. Files dropped into the BookDrop folder are detected and queued for review before import.
Both support OPDS and Kobo sync, and both work with KOReader (BookLore syncs progress with it; Kavita's wiki lists KOReader under third-party clients). Kavita's wiki also covers other third-party clients such as Mihon and Paperback. For accounts, BookLore mentions "local or OIDC authentication"; Kavita's README lists "rich Role-based management for age restrictions, abilities within the app, OIDC, etc".
Kavita splits its feature set. Its README says metadata download, reviews, ratings, recommendations, scrobbling and smart collections are "available via Kavita+", which it describes as a paid subscription. The core reader and server are GPL-3.0 and need none of it. BookLore's README lists no gated features.
BookLore is AGPL-3.0 and Kavita is GPL-3.0. Both are open source; for Kavita the Kavita+ features above are the gated part.
BookLore's installation docs state "2 GB RAM minimum, 4 GB+ recommended". Kavita documents no minimum: its wiki only says users have reported running it "on as little as a single-core 1Ghz CPU and 256MB RAM", so our catalog's 512 MB for Kavita is our estimate. In our install check (GCP e2-standard-2, Ubuntu 26.04), idle at first boot with the default install snippet and no real library, BookLore used ~908 MB of RAM and ~934 MB of disk (November 2026), and Kavita used ~327 MB of RAM and ~859 MB of disk (September 2026). The readings are from different months, and neither includes a scanned library or active readers.
Kavita is 1 out of 5: one docker run of the official image on port 5000, and
the first account you register becomes admin. BookLore is 2 out of 5: a
two-service compose file with MariaDB, the web UI on port 6060, and books and
bookdrop folders.
Choose Kavita if manga, comics or webtoons are a main part of the collection, you want the lighter install we measured, and you want a project that is still actively developed.
Choose BookLore if your collection is mostly ebooks, you want Magic Shelves and a review step on imports, and you are comfortable with a project in maintenance mode.
For comics specifically, see Kavita vs Komga.
Both installs are verified on Ubuntu 26.04; the files are on the BookLore and Kavita pages. Both listen on plain HTTP in our snippets, so add a reverse proxy with TLS before exposing either.
Kavita lists a lower minimum: 512 MB vs 1024 MB for BookLore.
No. BookLore is AGPL-3.0, Kavita is GPL-3.0.
Kavita for manga, comics and a lighter, one-container install (~327 MB idle RAM in our first-boot check). BookLore for a book library with Magic Shelves and a drop-folder import (~908 MB idle), with the caveat that its README says maintenance mode.
Its README says BookLore is entering maintenance mode and names BookOrbit as its official successor and the home of active development. Occasional maintenance, bug fixes and security updates continue.
A paid subscription through which Kavita's README says metadata download, reviews, ratings, recommendations, scrobbling and smart collections are available. The core server and readers are GPL-3.0 without it.
BookLore needs MariaDB, which our install runs as a second container. Our Kavita install is a single container with its config folder.
Paid link — we earn a commission if you shop through it.
A standalone ebook library with a drop folder and built-in reader, or a web front end for an existing Calibre database.
Epub highlights and a lighter footprint vs. MIT licensing and Kobo Sync.
A whiteboard-and-docs workspace on a plain Compose file vs. native apps on a commercial server.