How to Use Audiobookshelf: The Beginner's Guide (First Compose, the Three Mounts, the Root-User Rule, and M4B Chapters)

CodexFuse Team · 2026-10-31T11:01:13.748Z · 15 min read

Learn how to use Audiobookshelf: install with Docker Compose, set up the three mounts, create your first library, match metadata, merge books to M4B, and connect the phone apps.

How to Use Audiobookshelf: The Beginner's Guide (First Compose, the Three Mounts, the Root-User Rule, and M4B Chapters)

Learning how to use Audiobookshelf is how you finally own your audiobooks instead of renting them. Audiobookshelf is a free, open-source, self-hosted audiobook and podcast server (advplyr/audiobookshelf on GitHub, GPL-3.0, about 14,867 stars, v2.37.2 at the time of writing) that runs in Docker and turns a folder of audio files into a private streaming library with progress syncing, chapters, and phone apps — the whole Audible experience, except the books live on your machine. This audiobookshelf tutorial runs the complete beginner arc in one sitting: the Docker Compose install, the three volume mounts beginners get wrong, the root-password-first login rule, your first library (Books vs Podcasts), automatic metadata matching, the built-in merge-to-M4B tool that gives multi-file books real chapters, podcast subscriptions, and the official mobile apps. You will need Docker, so start with our Docker beginner guide if containers are new to you.

How do you set up Audiobookshelf for the first time?

The fastest beginner path is: create a project folder with four directories, write a small Docker Compose file with the official image and four volume mounts, bring the container up, open the web UI at port 13378, log in as root and set a password, create a standard user for daily listening, add your first library, and let the metadata scan fill in covers and descriptions. After that you connect a phone app and your books are everywhere you are. The whole arc takes about thirty minutes if Docker is already installed — the compose file and the folder layout are the only parts that trip people up, and this guide walks them in order.

What is Audiobookshelf (the self-hosted audiobook server)?

Audiobookshelf is an open-source media server built specifically for audiobooks and podcasts: it scans your audio files, stacks multi-file books into one continuous timeline, fetches covers, narrators, and series info from online sources, remembers your exact position to the second, and streams to a web player plus native phone apps with offline downloads. It is GPL-3.0 software with no account, no subscription, and no cloud dependency — your files stay on your own disk, which is the entire point for people leaving Audible-style rental models. If you already run a video server, our Jellyfin beginner guide covers that lane — Jellyfin streams movies and TV, Audiobookshelf streams books and podcasts, and this guide draws that line so you pick the right server for the right media.

What does the first install need before you write anything?

The install needs Docker plus a plan for four folders, because Audiobookshelf keeps its database, its cover art cache, and your actual media in separate mounts that you must get right on the first boot. Start by creating the project home and the four directories (this example uses /opt/audiobookshelf):

mkdir -p /opt/audiobookshelf
cd /opt/audiobookshelf
mkdir audiobooks podcasts config metadata

The three mounts — config, metadata, and your media folders — are the beginner decision, so here is what each one holds and the rule for each:

That local-disk rule for /config is the one beginners violate most: the database lives there, so pointing it at a flaky network share is how you corrupt the library you just spent an hour building. If you do not have a server yet, a what is VPS hosting primer covers the cheap machines most beginners run Audiobookshelf on, and it runs comfortably on a Raspberry Pi 4 or 5 if you would rather host at home.

How do you install Audiobookshelf with Docker Compose?

You install Audiobookshelf with a short Compose file using the official image ghcr.io/advplyr/audiobookshelf, publishing port 13378 and mounting the four folders. Write this docker-compose.yml next to your directories:

services:
  audiobookshelf:
    image: ghcr.io/advplyr/audiobookshelf:latest
    container_name: audiobookshelf
    restart: unless-stopped
    ports:
      - 13378:80
    volumes:
      - ./audiobooks:/audiobooks
      - ./podcasts:/podcasts
      - ./config:/config
      - ./metadata:/metadata
    environment:
      - TZ=America/New_York
      - PUID=1000
      - PGID=1000

Change TZ to your own timezone — scheduled tasks like backups and podcast auto-downloads run on it. PUID and PGID tell the container which system user owns the files it writes; match them to your user id and group id or you will hit permission errors the moment the scanner tries to write cover art into your folders. Bring it up:

docker compose up -d
docker ps

You should see audiobookshelf with status Up. Open http://your-server-ip:13378 (or http://localhost:13378 on the machine itself) and the initial server setup screen appears.

Why must you log in as root first — and then never use root again?

Audiobookshelf's first-run screen logs you in with the default username root and asks you to set its password, because the root account is the admin key that creates every other user — and because it is also the account you must abandon for daily listening. Set a strong password immediately; anyone on your network can reach the setup screen, and root can change libraries, users, and settings. Then, before touching any media, create your real listening account: click the gear icon, open Users in the sidebar, click Add User, fill in the details, and click Create. Repeat for family or friends — everyone gets their own progress, bookmarks, and permissions, so your partner's thriller never overwrites your place in a history book. Log out of root and log back in as your new user. From here on, root only comes out for admin chores.

How do you create your first audiobook library?

You create a library from Libraries → Add Library, and the one choice that matters is the Media Type: Book for audiobooks or Podcasts for shows. Name the library (for example, "Audiobooks"), pick a metadata provider like Google Books, browse to the /audiobooks folder, and click Create. Then run the first scan — Audiobookshelf reads the directory structure, filenames, and embedded ID3 tags, stacks multi-file books into single timeline entries, and pulls covers, descriptions, narrators, and publication years from its sources. If the covers stay blank, check the scan completed before you panic: large first imports can take several minutes, and the library fills in as the scan walks the folders.

How does Audiobookshelf get book metadata and covers?

Audiobookshelf fetches metadata automatically at scan time from a roster of online providers — Audible, Google Books, iTunes, Audnexus, and Open Library — and falls back to a bulk match plus a manual fix for anything it misses. The two-pass routine beginners should learn: first the bulk fix (Settings → Libraries → the three-dot menu on your library → Match Books), which re-queries providers for every unmatched book at once and usually populates most covers and descriptions in one go; then the manual fix for the stubborn few (click the pencil icon on the book's cover → the Match tab → pick the best result, ideally one carrying an ISBN). Providers vary in coverage — a 2024 self-published title might match perfectly on Google Books while a 1970s radio drama needs a manual match — so expect the last ten percent to need your judgment. Correct chapter markers and series ordering can also be fixed from the same edit screen, which is worth doing once for any series you own: Audiobookshelf keeps series in the right order automatically once the metadata is right.

M4B vs MP3 — which audiobook format should you use?

Use M4B whenever you have the choice, because M4B files carry chapter markers while MP3 chapter support is patchy across players. A single M4B per book gives you named chapters you can jump between, one file to back up, and metadata baked into the container; a folder of forty loose MP3s is a book that any app can lose its place in. Audiobookshelf plays both formats fine and even stacks a folder of MP3s into one smooth timeline at scan time — but it also ships a built-in merge tool in the web interface that permanently converts a multi-file book into a single M4B with the metadata baked in, so you only have to convert once. If your library is all MP3s today, merge your favorites first and chip away at the rest; you will feel the difference the next time you skip back to the start of a chapter instead of guessing which file held it.

How do you subscribe to podcasts in Audiobookshelf?

You subscribe to podcasts from a Podcasts-type library: open the library's search tab, type a show name (it searches the iTunes podcast directory) or paste an RSS feed URL directly, click the show, turn on Download automatically for new episodes, and submit. The important settings live on the show's edit screen: the episodes tab controls the back catalog — set a date far in the past and the episode limit to 0 if you want the entire archive, or keep a rolling set of the latest episodes for daily shows — and the schedule tab controls when the server checks for new episodes. Two rules beginners learn the hard way: only admins can add podcasts (non-admin users get a "copy the RSS link and send it to your server admin" message instead), and Audiobookshelf only downloads new episodes by default, so a fresh subscribe with no back-catalog settings gives you an empty library until the next episode drops. Once it is set, episodes download to the server on their own and sync to your phone like any other library item.

How do you listen on your phone (the Audiobookshelf app)?

The phone experience is the payoff: the official Audiobookshelf app is on the Google Play Store for Android, while iPhone users have historically faced a closed TestFlight beta that stays full — recent guides (Tony Teaches Tech, October 2026) point iOS users to Plappa from the App Store as the working alternative. To connect any app: open it, choose Audiobookshelf as the server type, enter your server address (your domain or http://server-ip:13378) and your standard-user credentials — never root — and log in. The apps are built specifically for spoken word: adjustable playback speed, silence skipping, a sleep timer, volume boosting for quiet recordings, offline downloads for commutes and flights, and progress that syncs back to the server the moment you reconnect. Pro tip: download before you leave Wi-Fi if your remote connection is slow — the server does not transcode, so a slow pipe can stutter a high-bitrate file.

How do you make Audiobookshelf available outside your home (reverse proxy)?

You make it available remotely by putting a reverse proxy with HTTPS in front of port 13378 — never expose the raw port to the internet. The quick version with Caddy:

books.example.com {
    reverse_proxy localhost:13378
}

Caddy fetches a TLS certificate automatically, so https://books.example.com just works — and your phone app connects with the HTTPS address. Our Caddy beginner guide covers the full install. If you would rather not open any ports at all, a private tunnel or mesh VPN works just as well: our Tailscale beginner guide shows the remote-listening branch that keeps the server off the public internet entirely. Either way, three rules: use your standard user on the phone (root stays on the LAN), keep the container on a pinned image tag once you are happy with a version, and remember backups start with the /config folder.

Audiobookshelf vs Audible — is self-hosting actually worth it?

It is worth it if you want to own books instead of renting access, and not worth it if you want the biggest catalog with zero effort. The honest comparison:

The legal-sources rule matters here: this guide is about books you actually own. Free public-domain audiobooks (for example Librivox's classics, MP3) and DRM-free stores like Libro.fm (M4B, and they support local bookstores) drop straight into the server; Audible's locked AAX files do not work without extra steps, which is a DRM problem, not a guide problem. Build the library from files you own and Audiobookshelf is the closest thing to a private Audible that exists.

What mistakes do Audiobookshelf beginners always make?

Every support thread about Audiobookshelf repeats the same short list. Skim it before you debug anything:

Sources

Every fact in this guide was verified against these sources on 2026-10-31. The GitHub releases API is the authority for the current version and star count; the independent beginner guides are the authority for the install arc and daily-use mechanics.

• GitHub API — advplyr/audiobookshelf (queried 2026-10-31): latest release v2.37.2 published 2026-10-23; ~14,867 stars; GPL-3.0; description "Self-hosted audiobook and podcast server".
• tonyteaches.tech — "How to Self-Host Audiobookshelf (Best Audible Alternative)" (30 days old, crawled 2026-10-31 10:57 UTC): the freshest install arc — compose file with ghcr.io/advplyr/audiobookshelf:latest, port 13378:80, four volume mounts, TZ/PUID/PGID, root first login then create-a-standard-user rule, Google Books metadata provider, Match Books bulk fix and manual match via the pencil icon, 25–50 MB-per-hour sizing, Cloudflare Tunnel remote access, Plappa as the iOS recommendation while the official app's TestFlight stays full, Pi 4/5 support.
• makeuseof.com — "My audiobooks deserved their own Plex, and this is it" (published Jun 20, 2026, crawled 2026-08-31): Plex's chapter/resume failures as the audiobook case, the built-in merge-to-M4B tool from the web interface, metadata providers (Audible, Google Books, iTunes, Audnexus, Open Library), scanner behavior (directories, filenames, ID3 tags), series ordering, phone-app features (sleep timers, speed, silence skipping, volume boosting, offline downloads, progress sync), PUID/PGID permission rule, Raspberry Pi 3 viability.
• xda-developers.com — "Host your own audiobook and podcast library with Audiobookshelf" (706 days old, crawled ~94 days ago): Proxmox VE helper-script install path, Docker alternative, web-UI library creation with Books-vs-Podcasts media type, scan-library step, port 13378, Calibre-Web as the e-book sibling lane.
• tonyedwardspz.co.uk — "How to subscribe to podcasts with Audiobookshelf" (1193 days old, crawled 5 days ago): podcast library search tab with iTunes search and RSS URL input, auto-download toggle, back-catalogue episode date/limit settings (limit 0 = full archive), schedule tab tuning.
• soundleafapp.com — Audiobookshelf podcast docs (13 days old, crawled 2 days ago): admin-only podcast adds, Discover tab with popular-by-country charts, "In this library" state, RSS feed sharing with the server admin.
• pimylifeup.com — "Raspberry Pi Audiobookshelf" (622 days old, crawled ~2 days ago): Pi compose path, TZ for backup scheduling, reverse-proxy and Tailscale remote-access branches.

Frequently asked questions

Is Audiobookshelf free to use?

Yes. Audiobookshelf is free and open-source under the GPL-3.0 license — no trial, no premium tier, no account needed. You pay only for the machine you run it on and the books you choose to buy.

Do I need a domain name to use Audiobookshelf?

No. On your home network, the server IP with port 13378 works fine. A domain becomes worth it when you want HTTPS and phone access from anywhere: point the domain at your server, put a reverse proxy with TLS in front, and connect the app to the HTTPS address.

Can I run Audiobookshelf on a Raspberry Pi?

Yes. It is one of the lightest media servers around — community guides run it on a Raspberry Pi 3, 4, or 5 with Docker. A small library fits in a few gigabytes (audiobook files run roughly 25–50 MB per hour), so even the Pi's modest storage goes a long way for a starter collection.

Should my audiobooks be M4B or MP3?

M4B, whenever you can get it. M4B files carry proper chapter markers; MP3 chapter support is patchy. If your library is MP3s today, use Audiobookshelf's built-in merge tool to convert multi-file books into single M4Bs from the web interface — one file, real chapters, metadata baked in.

Audiobookshelf vs Plex for audiobooks — which wins?

Audiobookshelf, and it is not close. Plex was built for music and video: it files books under Artist/Album/Track, fumbles chapters, and can dump you at the start of a file instead of resuming your position. Audiobookshelf treats the book as the unit from the ground up — chapters, narrators, series order, second-exact resume, and spoken-word player features. Run Plex or Jellyfin for video; run Audiobookshelf for books.