eBooks.com Rebuilds Its Apps on Readium LCP: 2026 Guide

Published September 13, 2026

On September 11, 2026, eBooks.com — one of the oldest independent ebook stores on the web — announced that it had replaced its iOS and Android reading applications with a completely new pair of apps. That sounds like routine app maintenance. It is not. The interesting part is not that the apps are new; it is what they are built on.

The new apps were developed through an Australian-European partnership and are built on Readium LCP, a vendor-neutral DRM standard maintained by the European Digital Reading Lab (EDRLab). The rendering engine comes from Sweden's Colibrio. The desktop sibling of the same stack is Thorium Reader. Together they represent a retail ebook store migrating away from a proprietary, single-vendor DRM silo and toward an open, standards-based reading platform — and that shift is more consequential for ordinary readers than any single app update.

The announcement was reported by Good e-Reader on September 11, 2026, quoting eBooks.com founder Stephen Cole describing the platform's "clear focus on accessibility, simplicity and interoperability."

What eBooks.com Actually Shipped

The launch is not a single app but a platform renewal spanning three surfaces: the new native iOS and Android apps, a rebuilt browser-based Online Reader, and support for the Thorium desktop application. All three now share the same underlying reading technology.

The format support list is specific and worth reading closely, because it separates a "reader app" from a "reading system." According to the announcement, the new apps handle fixed-format EPUB, audio-visual content, manga, and textbooks with complex layouts and specialized fonts. That is a materially wider range than reflowable text alone — manga and fixed-layout textbooks are exactly the categories that break naive EPUB readers.

Note what is absent from that table: any mention of a proprietary container format, a vendor-specific app lock-in, or a requirement to create a third-party account to open your own purchases. Those omissions are the story.

Why Readium LCP Matters More Than the App

Most ebook DRM in circulation is proprietary. The license server, the encryption scheme, and the reading application all come from one vendor, which means a store that adopts it is renting its distribution channel rather than owning it. If the vendor changes terms, the store's customers are affected whether the store likes it or not.

Readium LCP is different in kind, not just in degree. Per EDRLab's own documentation, it is a modern DRM solution that supports multiple business models including library lending and bookstore sales, and it is an ISO International Standard, referenced as ISO/IEC 23078-2:2024. Several of its architectural properties come directly from being a standard rather than a product:

• Interoperable by design. Any publishing company can become an LCP license provider, and any technical organization can build an LCP-compliant reading app. The store is not tied to one app vendor, and the app is not tied to one store.
• Vendor-neutral governance. The publishing industry leads the operation of the DRM through EDRLab, a non-profit — not a single technology company.
• No per-transaction cost. The only cost for license providers is a yearly fee tied to the certification of their solution, which is what makes the model viable for small independent stores rather than only for giants.
• No third-party account required. Readers do not need to create an account with a DRM vendor to open books they bought — a detail that matters enormously for privacy and for long-term access.
• Decentralized data architecture. The encryption tool and the license server are deployed by the license provider itself, so no third party gains access to user data, usage statistics, or unencrypted ebook content.
• Library-lending friendly. LCP supports loan extension and advanced return of a loaned ebook, which is the operational reality of public library systems.
• Accessibility-compatible on purpose. LCP does not break the accessibility requirement in the EU Accessibility Directive. DRMs that block screen readers from accessing content are no longer marketable in Europe — a constraint that effectively forces proprietary systems to choose between compliance and lock-in.

That last point connects directly to what eBooks.com shipped. The announcement emphasizes assistive-technology integration on both platforms — VoiceOver on iOS and TalkBack on Android — and adds reader-controlled typography: text size, typeface, spacing, alignment, colours, margins, and other aspects of the page. The company also states it developed reading options intended to make ebooks more comfortable for people with dyslexia and other reading or visual preferences.

The Engineering Behind the Rendering

Readium LCP answers how the file is protected. It does not answer how the page is rendered. That job falls to the Colibrio Reader Framework, and its public documentation describes an architecture built on the modern web platform, written in TypeScript with native development kits in Kotlin and Swift.

The design choice worth understanding is the format adapter model. An adapter takes a publication — EPUB, PDF, audiobook, web publication — and exposes its contents to the reading system in a generalized way. EPUB3, PDF, Web Publication and audiobooks are supported out of the box, and the framework's own documentation notes that "any future format is just a new adapter away." DRM, annotation and bookmarking services are also adapter-based.

For readers, the practical consequence is pagination quality. Colibrio advertises a layout system it calls Colibrio Reflow, designed to flow content across pages while preserving the author's original visual style, with configurable rules to avoid orphans, widows, and split boxes. Manga, textbooks, and illustrated children's books are the categories where this either works or visibly does not.

The accessibility feature list is equally concrete: media overlays, text-to-speech, and user-definable type and display settings, plus exposure of "low level" platform accessibility technologies so downstream developers can build further.

Where Thorium Fits

Thorium Reader is the third piece of the stack and the one you can use today without buying anything. It is an EDRLab application, available for Windows 10 and 11, macOS and Linux, and it is positioned as the EPUB reader of choice for desktop. It handles EPUB 2, EPUB 3, and EPUB 3 fixed-layout publications, PDF documents, and DAISY 2.02 and 3 accessible ebooks — LCP-protected or not.

Its relevance to this story is that it is free, open-source, has no ads and no private data leaks, and is localized in a large set of languages. For readers who want to test whether an LCP-protected title will open outside the store that sold it, Thorium is the reference implementation to try — and it is the reason "LCP support" is a meaningful claim rather than a marketing line.

Reading the DRM Landscape by Interoperability, Not by Name

If you are choosing where to buy ebooks and how to keep them long-term, the useful axis is not "which store" but how interoperable is the protection layer. That gives three broad tiers.

eBooks.com moving from the third row toward the second is a genuine improvement for its customers. It is worth being precise about what it does not mean, though: LCP titles are still encrypted, so owning an LCP-protected book is not the same as owning a DRM-free EPUB. The gain is in who controls access and how many applications can render it, not in removing protection entirely.

That distinction matters because the two most common questions readers ask — "can I convert this file?" and "will this still open in ten years?" — have different answers depending on which row of the table you are in. For a deeper look at how these layers interact, the site's EPUB vs PDF vs MOBI vs AZW3 comparison walks through the container formats themselves, and building a DRM-free EPUB library covers the fully portable end of the spectrum.

What to Do With This If You Own an Ebook Library

A store adopting an open DRM standard does not retrofit protection onto books you already bought elsewhere, and it does not change the format of your existing files. What it does is give you one more reason to check the protection layer before you buy — and one more compatible application to read with. A short, practical sequence:

1. Check what protects your existing purchases. Open one title in a reader you did not buy it from. If it opens, your protection layer is portable. If it refuses, you are in the single-vendor tier and should plan accordingly.
2. Keep an unencrypted EPUB as the master copy wherever the law allows it — for public-domain works, DRM-free purchases, and your own documents. Derive other formats from that master rather than re-converting converted files.
3. Prefer stores whose DRM is a standard you can name. "Readium LCP" is a specific, ISO-referenced answer you can verify. "Our own secure format" is not.
4. Test with Thorium. If a store claims LCP support, Thorium is the free, open-source desktop reader you can use to confirm the claim on your own machine.
5. Fix structure before you convert. Whether the destination is another reader, a PDF, or an audiobook, clean heading hierarchy and a correct navigation document survive the trip. Conversion tools can repair metadata, but they cannot infer a chapter structure that was never there — see editing EPUB metadata in Calibre for the cleanup pass.

If you need to move files between formats yourself, a browser-based converter keeps the file on your own device: try the EPUB converter on converter-epub.com — nothing is uploaded to a server.

The Larger Pattern

The most interesting thing about this announcement is that it is not being framed as a feature war. eBooks.com is not claiming a better screen, a faster chip, or an exclusive title. It is claiming interoperability, accessibility, and standards compliance — the vocabulary of infrastructure, not of marketing.

That is what a mature market looks like. When stores compete on which vendor's DRM they rent, readers bear the migration cost every time a vendor changes course. When they compete on how open and accessible their reading stack is, readers keep the books they paid for and can open them in more places. The EU Accessibility Directive, which makes screen-reader-blocking DRM unmarketable in Europe, is quietly pushing the entire industry in the same direction.

For anyone who has watched ebook DRM tighten over the past two years — older Kindles losing download support, KFX encryption extending to more devices, library loopholes closed — an independent store voluntarily moving toward an open standard is a genuine counterexample. It will not reverse the closed-ecosystem trend on its own. But it demonstrates that the open path is commercially viable, and that is the precondition for it ever becoming the default.