Enable OPDS access in Binge Reader, copy the private catalog URL, and add it as a new catalog in an OPDS-compatible app. Enter the Binge Reader credentials requested by the app, browse the feed, and download one supported book.
Use the catalog URL, not the homepage
An OPDS client expects the exact feed address shown in Binge Reader. Copy it instead of typing the normal web address. Treat credentials and private catalog links as account access, especially on shared devices.
Prove browsing and download separately
First confirm categories and search results appear. Then download a small EPUB and open it. An empty feed can mean an incorrect URL, blocked authentication, missing permission, or a reader that expects another OPDS version.
Know what OPDS does not carry
OPDS standardizes catalog discovery and acquisition. The receiving app normally owns its reading position and highlights. Use a supported Binge Reader reader, Kobo, or KOReader workflow when shared state matters.
The details, at a glance.
| Consider | What to look for |
|---|---|
| Catalog | Browse Binge Reader publications |
| Acquisition | Download a supported file |
| Reading | Handled by the receiving app |
| Progress and notes | Require a separate supported sync route |
A few things worth asking.
Does OPDS sync my reading position?
Not by itself. It delivers catalog information and files; progress depends on a separate integration.
Why does the catalog open as an empty page?
Recheck the exact OPDS URL, authentication, account permission, and whether a network login proxy is intercepting device requests.
Go to the source
Documentation consulted for the routes and terminology on this page. Product behavior can change; verify your exact setup.
OPDS specificationsWritten by Binge Reader. Our comparisons explain documented workflows and practical tradeoffs; they are not independent product benchmarks.