Choose between accessing the library through a browser and exporting books into an iOS reading app. Those routes differ in availability, reading state, and where future metadata edits should happen.
Choose access or a separate copy
Browser access keeps you near the source library. Exporting creates a reading copy in another app. Both can be useful, but they solve different jobs and have different update behavior.
Test the book you actually read
A simple novel does not test a technical PDF or a fixed-layout illustrated book. Try footnotes, diagrams, search, and font changes on the actual iPhone or iPad you use.
Keep metadata edits predictable
Decide whether title and author corrections originate in Calibre. If you re-export a corrected file, confirm whether the destination updates the existing entry or creates a new one.
The details, at a glance.
| Consider | What to look for |
|---|---|
| Content server | Browser route from a running Calibre server |
| Exported EPUB | Independent reading copy in an app |
| Managed import | Provider-specific upload or plugin workflow |
| Annotations | Check export and continuity separately |
A few things worth asking.
Do I need to move the whole library?
No. A current-reading shelf is a good starting point.
Does importing a book transfer every Calibre field?
Field support varies. Check series, tags, and custom columns with a sample.
Go to the source
Documentation consulted for the routes and terminology on this page. Product behavior can change; verify your exact setup.
Calibre Content server documentation BookFusion: Calibre plugin and sync directionWritten by Binge Reader. Our comparisons explain documented workflows and practical tradeoffs; they are not independent product benchmarks.