Audiobookshelf: Self-Hosting Your Own Audiobook & Podcast Server

What Is Audiobookshelf and Why Ditch Plex for It?

Audiobookshelf is a self-hosted, open-source server for audiobooks and podcasts, designed from the ground up for that purpose. If you have a growing audiobook or podcast library, you want a purpose-built tool—not one that treats your files like a video. Plex and Jellyfin handle audiobooks awkwardly: they lack native chapter support, podcast subscription management, and reliable playback-position sync across devices. Audiobookshelf fixes all of that in a lightweight package that runs on almost any homelab hardware.

This guide covers the full Audiobookshelf setup—from Docker Compose with the critical path gotcha to mobile app configuration for offline syncing. By the end, you’ll have a dedicated audiobook and podcast server that syncs your position across every device in your home.

Why a Self-Hosted Audiobook Server Beats Plex or Jellyfin

Plex and Jellyfin are fantastic for movies and TV, but audiobooks are a square peg in a round hole there. Plex requires third-party agents for metadata, lacks native chapter support, and won’t remember where you stopped if you switch from phone to browser mid-chapter. Jellyfin is slightly better with plugins, but its podcast support is nonexistent and audiobook metadata matching is inconsistent.

Audiobookshelf was built specifically for these two media types. It supports audiobook chapters (M4B, MP3 with embedded chapters), embedded metadata (cover art, author, series), and podcast subscriptions with automatic episode downloads. Playback position syncs instantly across web, mobile, and desktop apps. No plugin hunting, no workarounds.

Audiobookshelf Setup Guide: Docker Compose on Your NAS or Server

Audiobookshelf is container-native and runs smoothly on any Docker-capable system—TrueNAS SCALE, Unraid, Proxmox, or a dedicated Docker server. The official Docker image is well-maintained and the setup takes under 10 minutes if you avoid the one mistake that trips up most users.

The Critical Container-Path Gotcha (Most Guides Bury This)

When you mount your audiobook and podcast folders into the Audiobookshelf container, you must use the internal container path for the volume mapping, not your host path. The Audiobookshelf web UI asks for a path to your library folders—and it expects the path inside the container, not the path on your NAS or server.

Here’s the mistake: you mount your host folder /mnt/nas/audiobooks to /audiobooks inside the container. Then in the Audiobookshelf web UI, you type /mnt/nas/audiobooks as the library path. That fails because the container doesn’t see your host filesystem. The correct path in the UI is /audiobooks—the container-side path.

Docker Compose File (Minimal Working Example)

Create a docker-compose.yml file on your Docker host. Adjust the volume paths (/path/to/your/audiobooks, /path/to/your/podcasts, /path/to/your/config) to match your NAS or server’s actual paths.

version: "3.7"
services:
  audiobookshelf:
    image: ghcr.io/advplyr/audiobookshelf:latest
    container_name: audiobookshelf
    ports:
      - "13378:80"
    volumes:
      - /path/to/your/audiobooks:/audiobooks
      - /path/to/your/podcasts:/podcasts
      - /path/to/your/config:/config
    restart: unless-stopped

Run docker compose up -d and access the web UI at http://your-server-ip:13378. Create an admin account on first visit, then add your libraries using the container-internal paths (/audiobooks and /podcasts).

Deploying on TrueNAS SCALE or Unraid

If you run TrueNAS SCALE, you can deploy Audiobookshelf via the Apps catalog (look for the community version) or manually via the “Custom App” option using the Docker Compose above. For Unraid, navigate to the Apps tab, search “audiobookshelf,” install the community template, and adjust the volume mappings to match your share paths. Both platforms use the same container-path rule.

For more on deciding between these platforms, see our TrueNAS vs Unraid comparison. If you’re building a dedicated Docker host, our Best Docker Server Build guide covers hardware picks that handle Audiobookshelf plus a dozen other containers.

Setting Up Book vs Podcast Libraries and Organizing Files

Audiobookshelf supports two library types: Books (audiobooks) and Podcasts. You’ll create at least one of each. The library type affects how metadata is matched and how the player handles episodes.

Books Library: Folder Structure for Perfect Metadata Matching

Audiobookshelf matches metadata using folder names and filenames. The recommended structure is one folder per book, with the folder name matching the book title (and optionally the author). Inside each folder, place your audio files.

• Single-file books (M4B, MP3): Name the file exactly as the book title. Example: /audiobooks/The Hobbit/The Hobbit.m4b.
• Multi-file books (MP3 chapters): Name files in order, e.g., 01.mp3, 02.mp3. Audiobookshelf will merge them into one book with chapters.
• Embedded metadata: M4B files with embedded chapters, cover art, and author tags work best. Audiobookshelf reads these automatically.

If metadata fails to match, you can manually edit it in the web UI—right-click the book, select “Edit Metadata,” and fill in author, series, and cover art. For series, name the folder like Series Name - Book 1 or use the metadata editor.

Podcasts Library: RSS Feeds and Automatic Downloads

For podcasts, you add RSS feed URLs directly in the Audiobookshelf web UI under the Podcasts library. The server will fetch episodes, download them automatically, and manage storage. You can set download limits per podcast (e.g., keep the latest 10 episodes) and schedule updates.

If you already have downloaded podcast files (e.g., from a manual download), place them in your podcasts folder with a folder structure like /podcasts/Podcast Name/Episode Title.mp3. Audiobookshelf will scan them in and treat them as local episodes, though RSS-based subscriptions get full metadata automation.

Mobile App Setup for Offline Listening and Sync

Audiobookshelf offers native mobile apps for iOS and Android. The apps are free, open-source, and support offline downloads, playback-position sync, and sleep timers. Setting them up takes about 60 seconds.

Playback-position sync is seamless. Start a book on your phone during your commute, pause, and resume on your desktop browser at home—Audiobookshelf remembers the exact second. This works because sync is tied to your user account, not the device.

Resource Requirements: How Lightweight Is It?

Audiobookshelf is remarkably efficient. The server process typically uses under 200MB of RAM at idle, and CPU usage is near zero until you trigger a library scan or stream audio. Even during a full library scan with thousands of files, it rarely exceeds 1 CPU core at 50% utilization.

Storage-wise, the application itself (config, database, metadata cache) takes about 200-500MB. Your library storage depends entirely on your audiobook and podcast collection—a single audiobook in M4B format is typically 200-400MB for a 10-hour book. Podcast episodes vary widely from 20MB to 150MB each.

You can run Audiobookshelf comfortably alongside other containers—Jellyfin, Plex, Home Assistant, or your NAS management tools. For example, a system with 8GB RAM and an Intel N100 can handle Audiobookshelf, Jellyfin (with hardware transcoding), and a dozen other containers without breaking a sweat. See our Best Docker Server Build guide for hardware that handles this workload.

Which Should You Choose: Audiobookshelf vs Plex for Audiobooks

This is the most common question for homelab users who already run Plex. The answer is straightforward: use Audiobookshelf for audiobooks and podcasts, keep Plex for movies and TV. They coexist perfectly on the same hardware.

If you absolutely must use one app for everything, Plex with the Audiobook Agent plugin is workable but frustrating. You’ll lose chapters, podcast support, and reliable sync. Audiobookshelf solves all of these problems with a dedicated, lightweight server that adds zero complexity to your existing setup.

Bottom Line: Audiobookshelf Is the Easiest Self-Hosted Audiobook and Podcast Server

If you own audiobooks or subscribe to podcasts, Audiobookshelf is the single best self-hosted solution available. It’s free, runs on nearly any hardware, syncs playback perfectly across devices, and handles both media types natively. The setup takes under 10 minutes once you know the container-path rule.

Start with a Docker Compose deployment on your existing NAS or server. Add your book and podcast folders, set up the mobile app, and you’re done. For most homelab users, this is one of the most rewarding self-hosted apps you’ll ever install—simple, fast, and it works exactly as expected.