Replace Audible

What you are actually giving up#

The store. Audible's catalogue, the credit system that makes a twenty hour book cost the same as a four hour one, and Audible Originals, which are sold nowhere else. If a meaningful part of your listening is Originals, this is a partial migration and you should expect to keep the membership.

Also gone:

• Whispersync. Reading the Kindle text and listening to the same book, with position shared between them. There is no self-hosted equivalent because the other half is Amazon's.
• Returns. The exchange policy for a book you did not get on with.
• Discovery. Recommendations, curated lists, the preview button. You find books elsewhere now and bring them home.

What you get in exchange is better in one specific way, which is the reason to bother. Audiobookshelf tracks progress per user, per item, at second resolution, and syncs it between the web player and the mobile apps. Switch from the car to the kitchen mid-sentence and it resumes correctly. Two people can be at different points in the same book with their own bookmarks. Audible does none of that. Series handling is proper too: book order, series metadata and continue-where-you-left-off across a fifteen book series, rather than a flat list of purchases.

The DRM question, stated plainly#

Audible downloads are DRM-protected, in two shapes.

.aax is the older format. It is decrypted using a per-account value called activation bytes: one value, obtained from the account, opens every .aax that account owns.

.aaxc is what recent downloads use. The decryption key and initialization vector are delivered in a separate voucher file issued alongside that specific download, rather than derived from the account. Anything written around activation bytes therefore does not apply.

Tools exist in both directions. audible-cli authenticates to your account and downloads books in AAX or AAXC with metadata and chapters, and has an activation-bytes command. Audiobookshelf itself does not participate: it will not strip DRM and cannot play protected files, so whatever you do happens before the file reaches your library folder.

The legal position is separate from ownership. Anti-circumvention law in the United States, the EU and the UK restricts breaking a technological protection measure whether or not you paid, with narrow exemptions, and Audible's terms cover what you agreed to. That question is yours to answer, and better answered before you spend an evening on tooling.

The route that avoids the question entirely: buy DRM-free. Libro.fm and Downpour sell downloadable audiobooks without DRM, and many publishers sell direct. It costs more per book than a credit. It also gives you files that will still open in twenty years, which is most of the point of self-hosting.

Get your data out first#

1. Export the list of what you own. Your entitlement list is the one thing you cannot rebuild, and audible-cli can dump the library to a file. Do this even if you are not moving a single audio file yet.

2. Write down where you are. Playback positions do not export from Audible in any form. Note the books you are partway through, by hand, before you switch.

3. Aim for one .m4b per book with embedded chapters. Audiobookshelf handles multi-file books, but a single m4b with a proper chapter table is what makes the mobile apps and the car behave. Libation describes itself as downloading and removing DRM from your library, using AAXClean rather than ffmpeg, on Windows, macOS and Linux; its author's note is "use at your own risk".

4. Lay the folders out the way the scanner wants, first time.

/audiobooks/
  Terry Pratchett/
    Discworld/
      Vol. 03 - Equal Rites/
        Equal Rites.m4b
  Ursula K. Le Guin/
    The Dispossessed/
      The Dispossessed.m4b

Author/Series/Title/ is the layout Audiobookshelf's scanner is happiest with. Fixing structure later means a rescan rather than a rename in the UI, so spend the extra hour now.

Which one to pick#

There is no real competition here, which is unusual for this site. Audiobookshelf is one container, ghcr.io/advplyr/audiobookshelf, listening on 13378, idling around 200 MB, with built-in OpenID Connect and mobile apps that support the OIDC flow too.

Three deployment details that catch people. The container ignores PUID and PGID, which trips up anyone arriving from LinuxServer images: use the compose user: 1000:1000 directive and chown the volumes before first start, or it runs as root and writes root-owned files into your media tree. The /config volume holding absdatabase.sqlite must be on local disk, never NFS or SMB, or you get "database is locked" errors and eventually a corrupted file. And /metadata holds the archives from the built-in scheduled backup, so backing it up naively means backing up your backups: exclude metadata/backups from your own job.

What the migration actually costs#

For a 300 book library:

• Disk: call it 30 MB per hour at Audible's usual quality, so a twelve hour book is around 350 MB and 300 books lands near 100 GB. That estimate moves a lot if you buy FLAC or high-bitrate m4b.
• Download and conversion: an overnight job, plus decryption time. This is serial, rate-limited at the source and boring. Start it and go to bed.
• Tagging and structure: the real time sink. Author names, series numbering and cover art for 300 books is several evenings. Do it once, properly.
• Server: ~200 MB idle, ~450 MB typical, one container, one SQLite file. Ops load 2 out of 5.
• Ongoing, and this one matters: keep it current. The authentication system was rewritten in 2.26.0, and releases since have patched weak OIDC protocol validation, an authentication bypass via refresh tokens, and bulk downloads that skipped item-level access checks. An internet-facing instance pinned to a 2.2x or early 2.3x tag is running known-bad auth code. 2.36.0 added a sessions table and a "log out all devices" button. Track releases; see An update strategy that does not lose data.
• Backup: absdatabase.sqlite holds users, libraries, every playback position, bookmarks and API tokens, and it is the irreplaceable part. Covers and metadata come back from a rescan; six hours into a book does not. Use SQLite .backup or stop the container, and ship it off-box with restic.

What breaks and how to tell early#

A book re-imported under a different path starts from zero. This is the failure everyone hits: you reorganize folders, the scanner treats the file as a new item, and the person who was six hours in loses their place. Settle the folder structure before you import at scale, and be careful with any bulk rename afterwards.

OIDC can lock out every account, including root. If you enable OpenID Connect and disable local login, a broken provider configuration leaves nobody able to sign in, and the documented recovery is editing the SQLite database by hand. Back up absdatabase.sqlite before touching auth settings, and keep local login enabled until you have signed in through the provider at least once.

The car. Test whatever you use while driving with one book, in week one. That is where audiobooks are actually consumed and it is the integration most likely to disappoint.

The household tell. Someone opens the Audible app out of habit and finishes the book there. Ask at the two week mark whose position is out of sync, and check the per-user progress in the admin view rather than taking their word for it.

The point of no return#

There is no destructive step here, which is the nice thing about this migration. You keep the Audible account, keep the library, and stop the credits. So the test is about whether the new arrangement is actually better for you:

1. Your three most-listened books are in Audiobookshelf with correct chapters and covers.
2. You have listened for two weeks on the device you actually use, in the place you actually use it, and position sync has survived at least one switch between devices mid-book.
3. Every listener in the house has an account and their own position, and none of them has quietly gone back to the Audible app.
4. You have restored absdatabase.sqlite into a scratch container and confirmed the progress came back with it. Untested, that file is the only copy of everyone's place in every book.

Then cancel the membership rather than the account. The books you bought stay where they are, and the door stays open for the next Original you want.

Next: Replace Spotify is the music half of the same problem and Replace Plex the video half. If this is going to be reachable from outside the house, do Reverse proxy and TLS and Remote access without port forwarding before you open anything, and size the backup with the Backup planner. The rest of the category is Media.