Start here.
Confirm both readers use a compatible state service and the same edition. Then check accounts and offline changes. File synchronization alone does not establish reading-position synchronization.
Identify the same book
Compare source files or identifiers. A new conversion may rearrange internal chapters or locators. Keep a chapter and a short nearby phrase so you can recover your place when exact position mapping is unavailable.
Check the handoff order
Allow device A to finish saving and syncing before opening device B. If both were used offline, inspect their saved positions before choosing one. Automatically preferring the furthest page may be wrong when you were reviewing earlier material.
Test one clean scenario
Use a single small book with one reader session at a time. If that works, introduce the offline step or problematic edition. A controlled sequence reveals where the failure begins.
The details, at a glance.
| Consider | What to look for |
|---|---|
| Different files | Compare editions and internal structure |
| Different accounts | Confirm the active reader identity |
| Offline conflict | Review both locations before selecting one |
| Unsupported route | Use a compatible shared-state workflow |
A few things worth asking.
Is the furthest percentage always the correct place?
No. Revisiting a chapter or skimming ahead can make that heuristic wrong.
Why did conversion break the position?
The internal document structure can change, so an old locator may no longer point to the same passage.
Go to the source
Documentation consulted for the routes and terminology on this page. Product behavior can change; verify your exact setup.
W3C EPUB 3.3 specificationWritten by Binge Reader. Our comparisons explain documented workflows and practical tradeoffs; they are not independent product benchmarks.