Audiobookshelf on Raspberry Pi: Install with Docker (2026 Guide)
July 17th, 2026
Audiobookshelf is a self-hosted server designed specifically for audiobooks and podcasts. It provides a central location for storing media files while offering features normally associated with commercial streaming platforms.
Unlike a basic network folder, Audiobookshelf keeps track of books, authors, narrators, covers, descriptions, listening progress, and other information. Users interact with the server through a graphical interface rather than manually browsing directories.
Because the software is self-hosted, this self-hosted audiobook server keeps the media library and user data on hardware controlled by the server owner.
Main Features
One of the most useful Audiobookshelf features is playback progress synchronization. A listener can begin an audiobook on one device and continue from approximately the same position on another.
The platform also supports multiple users, individual listening histories, bookmarks, playback statistics, and metadata management. Administrators can create separate libraries and control which users have access to them.
Additional capabilities include chapter navigation, variable playback speeds, sleep timers, podcast subscriptions, and automatic library scanning. These functions make Audiobookshelf more suitable for spoken-word content than general-purpose media servers.
Supported Media Formats
In this Audiobookshelf tutorial, you'll see that Audiobookshelf works with common audio formats used for audiobook collections, including MP3, M4A, M4B, AAC, FLAC, OGG, and OPUS files.
M4B is particularly useful for audiobooks because a single file can contain chapters and embedded metadata. However, collections stored as multiple MP3 files are also supported.
The server can additionally work with ebook files associated with audiobook entries. The exact playback capabilities available to users may depend on the client device and application.
Audiobooks vs. Podcasts
| Feature | Audiobooks | Podcasts |
|---|---|---|
| Content source | Files stored on the Raspberry Pi or an external storage device | Centralized organization and access to a personal audiobook collection |
| Library management | Audiobookshelf scans directories and adds books to the library | Audiobookshelf retrieves podcast information and manages episodes |
| Storage | Audio files are already available locally | Episodes can be downloaded and stored on the server |
| Main advantage | Centralized organization and access to a personal audiobook collection | Greater control over podcast subscriptions and archived episodes |
Web Interface and Mobile Apps
After installation, Audiobookshelf can be controlled through a web interface. From a computer on the same network, users can browse books, manage libraries, edit metadata, and listen to content.
Mobile applications provide a more convenient experience for smartphones and tablets. Depending on the client and platform, users can stream content from the server or download files for offline listening.
Mobile applications provide a more convenient experience for smartphones and tablets. Depending on the client and platform, users can stream content from the server or download files for offline listening.
Why Run Audiobookshelf on Raspberry Pi?
Running Audiobookshelf Docker Raspberry Pi is an excellent choice because audio streaming is generally less demanding than video transcoding.
A Raspberry Pi 4 can provide adequate performance for a small home server. The Raspberry Pi 5 offers additional processing power and faster storage options, making it preferable for larger collections and more demanding installations.
Power consumption is another advantage. The device can operate continuously without the energy requirements of a conventional desktop computer.
Self-hosting also provides greater control. The size of the collection depends mainly on available storage, and media files remain under the owner's control.
Hardware Requirements
•Raspberry Pi 4 or Raspberry Pi 5 with at least 4 GB of RAM.
•Compatible power supply.
•microSD card for the operating system or, preferably, an SSD. If you're using Raspberry Pi 5, our guide on optimizing Raspberry Pi SSD performance can help you achieve better reliability and faster storage.
•External USB SSD or hard drive for larger audiobook collections.
•Ethernet connection recommended for stable network performance.
Software Requirements
•64-bit Raspberry Pi OS.
•Active network connection.
•Next, create the Compose configuration. If you're new to Compose, the official Docker Compose documentation explains how the configuration file works.
•SSH for optional remote management of a headless Raspberry Pi.
Installing an audiobookshelf with Docker on Raspberry Pi
Before installing Docker on Raspberry Pi, start by updating the package information and installed software:
sudo apt update
sudo apt upgrade -y
Install Docker using our full tutorial: Raspberry Pi Docker Installation Guide.
How to Install Audiobookshelf on Raspberry Pi with Docker Compose
1.Create a directory for the project:
mkdir -p ~/audiobookshelf
cd ~/audiobookshelf
Create the required directories:
mkdir config metadata audiobooks podcasts
2.Next, create the Docker Compose Raspberry Pi configuration:
nano compose.yaml
Add the following content:
services:
audiobookshelf:
image: ghcr.io/advplyr/audiobookshelf:latest
container_name: audiobookshelf
ports:
- "13378:80"
volumes:
- ./audiobooks:/audiobooks
- ./podcasts:/podcasts
- ./config:/config
- ./metadata:/metadata
restart: unless-stopped
3.Save the file and start the container:
docker compose up -d
Check its status with:
docker compose ps
Your Audiobookshelf Docker Compose deployment should now be available through port 13378 of the Raspberry Pi.
First-Time Setup
Continue following this Audiobookshelf installation guide by opening a browser and entering the Raspberry Pi IP address followed by port 13378.
For example:
http://ip_raspberrypi:13378
The initial screen allows you to create the administrator account. Use a strong password, especially if remote access will eventually be enabled.
After logging in, create your first library and select the corresponding media directory. Audiobook content stored in the Compose example should use the /audiobooks path inside the container.
Start a library scan, and Audiobookshelf will process the available files. You can also refer to the official Audiobookshelf documentation for advanced library settings.
Organizing Your Audiobook Library
Good file organization improves scanning and metadata identification. Avoid placing every audiobook file inside one large directory.
Separate books by author and title whenever possible. Consistent filenames are also helpful, particularly for collections containing hundreds of items.
Before importing a large existing collection, correcting obvious naming and folder problems can save considerable administration work later.
Recommended Folder Structure
A simple structure might look like this:
audiobooks/
├── George Orwell/
│ └── 1984/
│ └── 1984.m4b
├── J.R.R. Tolkien/
│ └── The Hobbit/
│ ├── 01 - Chapter One.mp3
│ └── 02 - Chapter Two.mp3
This hierarchy makes the collection easier for both Audiobookshelf and the server administrator to manage.
Performance Tips
Use an SSD when possible, particularly for the operating system and application data. It provides better responsiveness and reliability than relying entirely on a microSD card.
A wired network connection can reduce interruptions during streaming and large library scans.
Avoid running unnecessary containers and services on a Raspberry Pi with limited memory. Monitoring CPU, RAM, storage space, and temperature can help identify problems before they affect playback. If you're running multiple Docker containers, you may also find our Raspberry Pi Portainer guide useful for visual container management.
Backup Strategies
A complete backup plan should protect more than the original audiobook files. Audiobookshelf also stores configuration information, user data, metadata, and listening progress.
The safest approach is to back up application data and media files separately.
•Back Up Configuration Files
The /config directory contains important application information. Back it up regularly to another storage device or computer.
For example:
tar -czf audiobookshelf-config-backup.tar.gz ~/audiobookshelf/config
Stop the container before creating critical backups when consistent application data is required.
•Preserve Metadata Database
The metadata directory contains downloaded covers and other library-related information. Losing this directory may require parts of the collection to be processed again.
Include both config and metadata in the regular backup routine:
tar -czf audiobookshelf-data-backup.tar.gz \
~/audiobookshelf/config \
~/audiobookshelf/metadata
Store at least one backup outside the Raspberry Pi. Following the 3-2-1 backup strategy is also recommended for protecting important media collections.
•Back Up Your Audiobook Library
Original audiobook files are usually the largest and most valuable part of the installation. They should not exist on only one physical drive.
Consider maintaining a second copy on a NAS, external disk, or another computer. For large collections, incremental backup tools can copy only new and modified files.
A backup connected permanently to the same Raspberry Pi offers limited protection against hardware failure, accidental deletion, or electrical damage. An independent second copy provides better protection.
Common Problems and Solutions
×This Audiobookshelf tutorial recommends that if the container does not start, inspect its status and logs:
docker compose ps
docker compose logs
×When Audiobookshelf cannot find media files, verify the Docker volume paths and Linux file permissions.
×If another device cannot connect, confirm the Raspberry Pi IP address, check that the container is running, and verify that port 13378 is reachable on the local network.
×Slow library scans are often related to storage performance, very large collections, or metadata processing. Moving application data to an SSD can improve responsiveness.
Finally, update the container periodically:
docker compose pull
docker compose up -d
With suitable storage, regular backups, and a well-organized media collection, Audiobookshelf can turn a Raspberry Pi into a practical audiobook and podcast server that remains available throughout the home.
Conclusion
Audiobookshelf and Raspberry Pi make an excellent combination for anyone looking to build a private audiobook and podcast server. With Docker, the installation process is straightforward, while Raspberry Pi provides an energy-efficient platform capable of running 24/7. Whether you're managing a small personal library or a growing collection shared with family members, Audiobookshelf offers an intuitive interface, reliable playback synchronization, and powerful library management features.
As your collection grows, you can further enhance your setup by using an SSD for faster storage, implementing regular backups, and expanding your available disk space with external drives or a NAS. With just a little maintenance, your Raspberry Pi can become a dependable self-hosted media server that keeps your audiobooks and podcasts organized, accessible, and entirely under your control.
