SD card and USB e-reader | Open the folder of an SD card or a plugged-in e-reader from your computer: see what’s on it, import files the cloud doesn’t have yet, or copy a ready version onto it. | A browser that supports File System Access, an HTTPS connection, the card or e-reader mounted on your computer, and your explicit read or write permission. | Inventory and copying need an open tab and permissions that are still valid. Folder access is granted to this browser only and doesn’t carry over to another device. |
|---|
Crosspoint on your local network | From your browser, connect to a Crosspoint e-reader on the same network: see what’s on it, send it EPUBs and, once you confirm, remove recognized files. | Compatible firmware, the Calibre Wireless screen open on the e-reader, the same local network, and a browser allowed to reach the e-reader on ports 80 (HTTP) and 81 (WebSocket). | The tab and the connection screen must stay open during the exchange. To bring files from the e-reader back to the cloud, use USB or the SD card: the local network connection can’t do that. |
|---|
Wireless Calibre from the server | Here the e-reader connects to the Calibre TCP server itself: it receives prepared books, reports the files it holds and carries out the removals you request. | A compatible wireless Calibre client, a reachable server address and port, a personal secret for the device, and a connection you explicitly open for a ten-minute window. | The Calibre TCP protocol encrypts nothing: titles, inventory and book contents can be intercepted on the network. On a shared network, use OPDS over HTTPS instead. This mode is separate from local-network Crosspoint mode. |
|---|
HTTPS OPDS catalog | Browse your library from a compatible reading app (recent books, authors, series, search, outbox, books shared with you) and download whatever you want to read. | A compatible OPDS client, an Internet connection, and the catalog address with the login and secret created for your device. | CrossPoint e-readers and generic OPDS clients only receive EPUBs. A download doesn’t prove the book is still on the device, and OPDS never sends files from the device back to the cloud. |
|---|
KOReader / kosync progress | Exchange your reading position with KOReader or another compatible client, and see the latest recognized progress, with its device and date, on the book’s page. | A client that accepts a custom kosync server, the mode switched on, and the device login with its secret. No account needs to be created from the e-reader. | This mode doesn’t transfer books, and the position may not land in exactly the same spot as in the Web reader. When it’s unclear which book a position belongs to, the progress is kept rather than attached to a book at random. |
|---|
Mobile API and Library Manager Reader | An authorized app can sync the catalog, download and import files, confirm its local copies and exchange progress. Library Manager Reader, the official open-source Android client, uses it to download your books and sync your reading position both ways in KOReader format. | An app that integrates the public API, OAuth authorization with PKCE and account consent, scopes matched to each action, and a local check of every copy before it is read. | This cloud release contains no mobile binary: Library Manager Reader is published separately, as an APK for Android, and isn’t distributed on iOS yet. An app confirming a copy doesn’t prove the file is physically stored, and a progress conflict requires an explicit choice. |
|---|