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/janeczku/calibre-web (opens in new tab)
Pick BookLore
If you have no Calibre library, want a BookDrop import folder, Magic Shelves and OIDC, and accept that its README now says maintenance mode.
Pick Calibre-Web
If you already manage books in Calibre or need LDAP or Google/GitHub OAuth, and want the lower idle RAM we measured (~147 MB against ~908 MB).
BookLore and Calibre-Web both give you a web library for ebooks with shelves,
OPDS, per-user accounts and Kobo sync, but they start from different places.
Calibre-Web is a front end for a Calibre database (metadata.db) you already
have. BookLore is a standalone library with its own database, its own import
folder and a built-in reader. One more thing to know before you pick: BookLore's
own README now says the project is entering maintenance mode (see below).
BookLore's README describes "a self-hosted app that brings your entire book collection under one roof", with smart shelves, automatic metadata, a built-in reader for PDFs, EPUBs and comics, Kobo and KOReader sync, and OPDS. Our catalog lists it as a Java (Spring Boot) and Angular application that stores its data in MariaDB.
Calibre-Web's README calls it "a web app that offers a clean and intuitive interface for browsing, reading, and downloading eBooks using a valid Calibre database". It is a Python and Flask application. Its README lists the Calibre desktop program as an optional tool, recommended for conversion and metadata editing.
BookLore's README opens with a notice: "BookOrbit is the next chapter of BookLore", described as "BookLore's official successor and the home of active development". It continues: "BookLore is entering maintenance mode and will continue to receive occasional maintenance, bug fixes, and security updates." The repository is not archived and still accepts commits, but new feature work is happening in BookOrbit, which we have not tested. Treat a new BookLore install as a choice for a slow-moving app, not a growing one. Our snippet pins the v2.4.0 image.
Calibre-Web's repository is not archived; its latest commit is from September 2026.
Calibre-Web needs a Calibre library. Our install downloads the blank
metadata.db from upstream's repository, and you point the admin page at the
folder that holds it. Its README lists "eBook metadata editing and deletion
support", "Metadata download from various sources (extensible via plugins)",
"eBook conversion through Calibre binaries", upload of new books and "Calibre
Custom Columns support". Our snippet leaves out the optional Calibre layer the README
describes for the linuxserver image, so conversion needs that added first.
BookLore keeps its own library in MariaDB. Its README lists rule-based "Magic Shelves", metadata pulled "from Google Books, Open Library, and Amazon", and BookDrop: "Drop files into a watched folder and BookLore detects, enriches, and queues them for import automatically." If you have no Calibre library and do not want one, that is the simpler start. If you do have one, Calibre-Web uses it in place.
Both offer in-browser reading, OPDS and Kobo sync, and both can send a book to an e-reader. BookLore's README adds KOReader progress sync and one-click sending to a Kindle or an email address; its comic support is part of the built-in reader. Calibre-Web lists "Send eBooks to E-Readers with a single click" and "Sync Kobo devices with your Calibre library".
For accounts, BookLore's README mentions "local or OIDC authentication", and its docs add forward auth from a reverse proxy. Calibre-Web lists fine-grained per-user permissions, public registration, content hiding by category per user, and "LDAP, Google/GitHub OAuth, and proxy authentication". Calibre-Web also has a "Magic Link" login "for easy access on eReaders".
BookLore is AGPL-3.0 and Calibre-Web is GPL-3.0; both are open source, with no gated features that we found in their READMEs.
BookLore's installation docs state "2 GB RAM minimum, 4 GB+ recommended". Calibre-Web's
README gives no RAM figure, so our 512 MB for it 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 or users,
BookLore used ~908 MB of RAM and ~934 MB of disk (November 2026), and
Calibre-Web used ~147 MB of RAM and ~1.1 GB of disk (September 2026).
The readings are from different months. Disk is docker system df for each
install, which for BookLore includes the MariaDB image.
Both are 2 out of 5. BookLore's snippet is a two-service compose file
(the app and MariaDB), with the web UI on port 6060 and books and bookdrop
folders. Calibre-Web is one docker run of the linuxserver image on port 8083,
plus the metadata.db download; the default login is admin / admin123, which
you must change.
Choose BookLore if you want a library that does not depend on Calibre, a drop-folder import flow, Magic Shelves and OIDC, and you accept that upstream has moved active development to BookOrbit.
Choose Calibre-Web if you already manage books in Calibre, want the much lower idle RAM we measured (~147 MB against ~908 MB), and want LDAP or Google/GitHub OAuth sign-in.
If your collection is mostly comics, see BookLore vs Kavita.
Both installs are verified on Ubuntu 26.04; the files are on the BookLore and Calibre-Web pages. Both listen on plain HTTP in our snippets, so put a reverse proxy with TLS in front before exposing either, and change Calibre-Web's default password first.
Calibre-Web lists a lower minimum: 512 MB vs 1024 MB for BookLore.
No. BookLore is AGPL-3.0, Calibre-Web is GPL-3.0.
Calibre-Web if you already keep books in Calibre or want the lower idle RAM (~147 MB in our first-boot check). BookLore if you want a standalone library with a drop-folder import and a built-in reader (~908 MB idle), knowing its README says it is entering maintenance mode.
Its README says BookLore is entering maintenance mode, with occasional maintenance, bug fixes and security updates, and names BookOrbit as the official successor and the home of active development. The repository is not archived.
It needs a Calibre database (metadata.db). Upstream's README links a blank sample database, and conversion features use Calibre binaries; you do not need the Calibre desktop app to browse and read.
Yes. Both READMEs list OPDS and Kobo sync, and both can send books to an e-reader.
Paid link — we earn a commission if you shop through it.
A book library with Magic Shelves and a review queue, or a reading server that leads with manga and comics.
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.