calibre

An e-book manager for Windows, Mac and Linux, started by Kovid Goyal on 31 October 2006 and still shipping. Read from its own About page on 2026-08-29.

Two things make it worth a page in a corpus otherwise built from GitHub repositories. It is by a wide margin the oldest and most-installed project here — the page claims more than 3 million active installs across over 200 countries — and it is the first source in the spoke that is a project's self-description rather than a repository, so there is no commit count, no fork count, no issue tracker and, on this page, no licence field.

Where it came from

The origin story is a compatibility problem, told in the first person:

calibre started life on 31 October, 2006, soon after the release of the SONY PRS-500, the first e-ink based reader to be sold commercially in the US… The PRS-500 did not work at all with Linux, my operating system of choice, so I decided to reverse engineer the USB protocol that it used, to get it working on Linux.

The project was called libprs500 for its first eighteen months. Goyal then wrote a converter to the SONY reader's LRF format because nothing adequate existed, and the converter — not the device driver — is what got adopted, including by publishers producing the first generation of LRF books. The graphical library manager came third, when his own collection outgrew the command line. libprs500 was renamed calibre in mid-2008, named by Goyal's wife Krittika; per the page, "The libre in calibre stands for freedom."

Goyal states the motive plainly, and it is the clearest statement of this spoke's founding posture anywhere in the corpus:

one of my goals has always been to prevent either the fragmentation or the monopolization of the e-book market by entities that care solely for short-term goals… hopefully it will always present an alternative for people that love to read e-books and want to be in control of their own digital libraries.

What it does

Eight capabilities, in the page's own grouping: library management with editable metadata and three views; conversion between dozens of formats, with target-device detection, table-of-contents generation and style fixes; device sync over cable or wirelessly, said to work with "almost every single e-reader"; a viewer with highlighting, bookmarks, read-aloud, search and embedded fonts; scheduled news and RSS delivery from hundreds of sources; a content server that hosts the library over HTTP for reading in a browser, which the page says works offline; a built-in editor for EPUB and Kindle internals; and a plugin explorer offering hundreds of one-click plugins.

Two of those land directly on concepts this spoke already holds. The content server is self-hosting in its smallest form — one binary, no container, no reverse proxy, and the operator is the same person as the reader. And the conversion pipeline is a compatibility-layer argument made about content rather than programs: it exists so a book runs on a device its publisher never targeted, and the project began by reverse-engineering a device protocol for exactly that reason. The register is the same, the object is not, and the page is worth reading as evidence that the register is broader than the two runtimes that opened it.

The numbers, and what they are worth

3 million active installs is the figure this page turns on, and the one nobody outside the project can check. It is self-reported, undated, and the page defines neither "active" nor how it is counted — calibre updates itself, so a version check is the obvious mechanism, and the page does not say. But it is the first install count in this spoke, and installs are precisely the measure projectrank cannot see: that metric ranks repositories on releases, contributors, licence and stars because "monthly downloads do not exist for software that ships as an app." Calibre ships as an app, has no star count worth quoting, and would score poorly on a metric built for libraries — while reporting a user base larger than anything else here.

Also stated: over 200 countries, translations into a dozen languages by volunteers, hundreds of plugins, and support turnaround where "most issues are resolved in a week." Funding is donations — a Patreon and PayPal.

Three problems with this source

It contradicts itself on how many people build it. The feature section says "Hundreds of motivated volunteers develop calibre" and repeats the claim as "hundreds of developers." Goyal's own account, further down the same page, says calibre is "a vibrant open-source community with half a dozen developers and many, many testers and bug reporters." Both claims are recorded here rather than reconciled. The likeliest reading is that the marketing block counts everyone who has ever contributed anything, including translations and bug reports, and the essay counts people writing code — but the page gives no basis to choose, and a factor of fifty is not a rounding difference.

Half of it is seventeen years old. Goyal's history is signed "Kovid Goyal, November 2009" and has evidently not been revised: it describes the community in the present tense as of 2009 and predates every install figure quoted above it. The feature section around it is current enough to say "over fifteen years." So the page mixes a 2009 memoir with present-day marketing under one URL and flags neither. No published: date is recorded in this page's frontmatter for that reason — dating the whole document to 2009 would misdate the statistics, and dating it to today would misdate the essay.

The licence is never named. Every other project in this spoke leads with one — Apache-2.0, AGPL-3.0, GPL-3.0-only, MIT, CC0. Calibre's About page says only that it is "a free and open source product, modifiable by all." (Checked against Wikipedia's Calibre article on 2026-08-29, which states GPL-3.0-only, original release 31 October 2006, and current stable 9.14.0 dated 2026-08-28 — a T3 corroboration from outside the project, recorded because the primary source omits the fact, and worth replacing with the project's own licence file.)

Related

foss-application · self-hosting · compatibility-layer · project-quality-score · open-source-alternative · synthesis