If you notice audiobook progress not syncing across devices, save the furthest correct position first, then confirm every device uses the same account and edition. In Audible, check that Sync listening position is on in player settings; in Apple Books, check that Books is turned on in iCloud settings.［1］［2］ A stale phone can still upload an older timestamp when it reconnects, so random seeking on every device risks replacing the evidence and the correct place.

Key Takeaways

Save the correct chapter, timestamp, and nearby sentence before making changes.

Confirm the same account, marketplace, title, edition, and narration on every device.

Determine which device can write a new position to the cloud and which can read it back.

Keep stale or offline devices disconnected until one clean source of truth is established.

Clear data or redownload only after preserving bookmarks and confirming recovery.

The streaming troubleshooting hub links broader media diagnostics. If films and episodes—not an audiobook—lose their watched state, use the watch-history sync guide. If songs or a music library are affected, use the music-library sync guide.

1. With audiobook progress not syncing across devices, what is the furthest correct position?

Stop opening the book on additional devices. On the device with the most accurate state, record the full title, author, narrator, edition or release date, chapter name and number, elapsed timestamp, remaining time, playback speed, and a short non-sensitive description of the nearby sentence. Create a normal in-app bookmark if the service supports it.

Do not rely on chapter number alone. Editions can divide chapters differently, and an introduction can shift every later timestamp. A screenshot may help privately, but redact account names, notifications, and library details before sharing it.

Label each device's observed position without seeking: Phone 12:18, Tablet 09:42, Web 12:18. Also note the last playback time and whether the device was online. This identifies the likely newest writer and prevents an old device from looking authoritative merely because it opened last.

If a bookmark is separate from the resume position, record both. A service may sync one object successfully while the other remains local.

2. Are all devices using the same account and exact edition?

Confirm the signed-in account, marketplace or store region where applicable, active profile, and library entry. Compare cover, narrator, duration, publisher, language, abridged or unabridged status, and edition identifier. Two listings with the same title can maintain separate progress records.

Audible says its app syncs your listening position across devices automatically and offers a Sync listening position toggle under Profile, Settings, and Player.［1］ Use the current Audible menu for Audible only; another service may store the option elsewhere or sync automatically.

Apple explains that Books can sync reading position, bookmarks, notes, and highlights when each device is signed in to the same Apple Account and Books is turned on in iCloud settings.［2］ That makes account and iCloud state part of an Apple Books diagnosis, not proof of a universal cloud model.

If one device shows a sample while another shows the purchased book, or one uses a family-shared copy and another a personal copy, stop. Establish the identical library object before testing sync.

3. Is the current position local, uploaded, or downloaded?

Treat synchronization as two operations: the source device writes a position, and the destination device reads it. “Both devices have internet” proves neither operation. Use status indicators, recent activity, and controlled timestamps rather than assumptions.

On the source device, connect normally, open the exact book, play for two minutes past a memorable boundary, pause, and remain online. Close the player through the normal interface rather than force-stopping it immediately. Wait briefly for the app to save.

On the destination, do not press play yet. Refresh the library or reopen the app and inspect the proposed resume position. If it reads the new timestamp, cloud write and read succeeded. If the web player sees it but one phone does not, the phone's local cache is stronger. If no destination sees it, source upload, account, or service state is stronger.

A downloaded audiobook can still use cloud progress, but its media file and its resume record are separate. Do not delete the download just because the position is stale.

4. Can a controlled write-and-read test reproduce the problem?

Choose one primary device and one secondary device. Keep every other installation offline. Use a harmless test position a minute beyond the saved correct location, not a large jump near the end that might mark the book finished.

Run this sequence:

On the primary device, confirm the correct account and edition.
Play from the saved location for about two minutes.
Pause normally and create a temporary bookmark.
Leave the app open and online briefly, then close it normally.
Open the secondary device while online and refresh once.
Record the offered resume position before pressing play.
Play another minute on the secondary, pause, and close normally.
Reopen the primary and check whether the position returns.

This reveals directionality. Primary-to-secondary may work while secondary-to-primary fails. Repeat once only; repeated seeking creates competing writes and obscures the first failure.

5. Are cloud sync, app permissions, and connectivity ready?

Check the service's documented sync setting, the device's account and cloud-service state, background data restrictions, available storage, battery restrictions, and ordinary connectivity. Change one item at a time and record its original value.

For Apple Books, confirm the same Apple Account and the documented iCloud Books settings on each device.［2］ For Audible, confirm Sync listening position is enabled where the current app exposes it.［1］ Google Play says its audiobooks play on computers, mobile devices, Google Home, and Google Assistant, and that switching devices resumes where you left off at the closest natural stopping point.［3］ A resume point a few seconds earlier than your last word can therefore be expected behavior there, not a failed sync. Use only settings documented for the relevant service.

Do not permanently disable privacy or security controls. A short comparison on a trusted alternate connection can identify a blocked sync path, but it should not change account country or title rights.

Check service status if all devices stop updating at the same time. A server incident cannot be fixed by deleting local data.

6. Could an old or offline device overwrite the newer position?

An offline device may hold a valid older timestamp and upload it when it reconnects. Keep every stale device in airplane mode or signed out of the app—not erased—while establishing one authoritative position. Include cars, smart speakers, e-readers, tablets, and web tabs.

After the primary writes and the secondary reads the correct timestamp, reconnect one stale device at a time. Before playback, inspect the proposed resume location. If it jumps backward, cancel playback, preserve the evidence, and refresh according to the service's documented flow.

Do not drag the playhead to the end to force completion. That can change finished status, recommendations, and automatic downloads. Likewise, do not repeatedly mark the book unread or finished unless support explicitly asks for that controlled test.

If offline listening is essential, finish the offline session, reconnect the source, allow it to sync, and verify the cloud position before resuming elsewhere.

7. How should you refresh without losing the right place?

Use a least-destructive ladder:

Preserve chapter, timestamp, nearby sentence, and bookmarks.
Refresh the library and reopen the same book.
Fully close and reopen the app.
Restart the affected device normally.
Install ordinary app and system updates.
Toggle the documented sync control only after recording its state.
Sign out only after confirming credentials and cloud/library recovery.
Redownload or reinstall only when the book and bookmarks are recoverable.

After every step, perform the same short write-and-read test. Do not clear all app data on both devices at once because that destroys the ability to identify the stale side.

Use the normal authorized connection as the baseline and compare the official app and account state if synchronization appears blocked. VPN routing does not decide which playback timestamp wins, and changing that route cannot restore progress that has already been overwritten.

8. What evidence should you give support?

Prepare a table with anonymous device labels, operating systems, app versions, account marketplace, exact edition, streamed or downloaded state, sync-setting state, observed position, last playback time, and online or offline status. Include the controlled test direction and result.

State whether bookmarks sync, whether the web player shows the newest position, and whether reconnecting a particular device causes a rollback. Give timestamps with time zones. This lets support distinguish account records, edition mapping, stale local cache, and conflicting writers.

Do not send passwords, payment details, full library exports, session cookies, device serial numbers, or private annotations. A short excerpt describing the nearby sentence is enough; do not reproduce copyrighted pages or audio transcripts.

Summary

Freeze the furthest correct position before opening more devices.
Verify the identical account, marketplace, title, edition, and narrator.
Test cloud write and cloud read as separate operations.
Isolate stale and offline devices until one source of truth is stable.
Preserve bookmarks and recovery details before clearing or reinstalling.

FAQ

Why does my audiobook jump backward after another device reconnects?

That device may upload an older local timestamp. Keep it offline while establishing the correct cloud position, then reconnect it without starting playback.

Can two editions of the same book share progress?

Do not assume so. Abridged, unabridged, remastered, translated, or differently narrated editions can be separate library objects with different chapter timing.

Does downloading the book disable sync?

Not necessarily. The audio package can be local while progress remains cloud-based. Test streamed and downloaded playback separately.

Should I delete and redownload first?

No. Preserve the correct place and test cloud write/read first. Deleting media may not repair the progress record and can remove offline access.

Why do bookmarks sync but the resume position does not?

They may be separate records or save on different triggers. Report both results because they narrow the faulty object.

Can playback speed cause the wrong timestamp?

Speed changes elapsed listening time but should not change the media position. Record speed because some interfaces show time remaining differently.

How long should I wait before checking another device?

Pause and close normally, remain online briefly, then refresh the destination once. The provider may not promise an exact interval, so record the elapsed time instead of assuming instant sync.

What if all devices stopped syncing together?

Check account and service status before resetting clients. A common server or cloud-account problem is more likely than simultaneous local corruption.

Why is Audible not syncing between devices?

First confirm that Sync listening position is on in each Audible app; Audible suggests turning the toggle off and back on if syncing misbehaves.［1］ Record the setting first, then check that every device uses the same account and marketplace before you reset anything else.

Sources

Audible Help, Listen in the app — https://help.audible.com/s/article/listen-in-the-app?language=en_US
Apple iPhone User Guide, Access books on other Apple devices — https://support.apple.com/guide/iphone/access-books-on-other-apple-devices-iphb886e1752/27/ios/27
Google Play Help, Buy and listen to audiobooks — https://support.google.com/googleplay/answer/7572879/buy-amp-listen-to-audiobooks-android?co=GENIE.Platform%3DAndroid&hl=en

Sources checked 4 October 2026.

Audiobook Progress Not Syncing Across Devices? Fix It Safely