OPDS describes publication catalogs that compatible clients can browse and use to acquire books. It helps a reader find a file; reading-state and annotation synchronization require separate supported capabilities.
Follow the route
Your library publishes a catalog. A compatible app connects to it, browses entries, and follows an acquisition link. The app then reads the downloaded file using its own reading engine and state.
Check the catalog version and access
A client and server must agree on the supported catalog format and authentication. Use the endpoint documented by the service. A homepage URL is not necessarily the catalog URL a reader expects.
Keep the boundaries clear
A working catalog proves browsing and acquisition. It does not prove bookmarks or highlights return to the server. Test those through the specific reader’s documented integration, if one exists.
The details, at a glance.
| Consider | What to look for |
|---|---|
| Library | Publishes publication records |
| Catalog | Describes titles and acquisition links |
| Reader app | Browses and downloads supported entries |
| State service | Separately handles positions or annotations |
A few things worth asking.
Is OPDS a file format like EPUB?
No. It is a catalog specification used to discover and acquire publications.
Will OPDS synchronize my chapter?
Not by itself. That depends on a separate compatible reading-state implementation.
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.