Audiobookshelf is a self-hosted media server for audiobooks and podcasts. It can also handle basic ebook support. Instead of uploading your library to a commercial platform, you run Audiobookshelf on your own server, PC, NAS, or Docker setup and stream your files from there.
That makes it a good choice for people who want full control over their audiobook library, user access, listening progress, metadata, and storage. This guide explains what Audiobookshelf is, what it does, and how it works in real use.
Quick Answer
Audiobookshelf is an open-source self-hosted server for audiobooks and podcasts. You install it on your own system, point it to your media folders, let it scan your files, and then stream your library through a web browser or mobile app while it tracks progress, metadata, and covers.
What Is Audiobookshelf?
Audiobookshelf is an open-source platform that turns your personal audiobook and podcast files into a private streaming library. It gives you a clean interface to browse titles, play audio, track progress, manage users, and organize metadata like authors, narrators, chapters, and series.
In simple terms, it works like a personal audiobook server. You keep the files. Audiobookshelf organizes them and delivers them to your devices.
What Can Audiobookshelf Do?
Audiobookshelf includes several features that make it more than a simple folder browser.
It can:
- Stream audiobooks and podcasts
- Track listening progress for each user
- Sync progress across devices
- Support multiple users with custom permissions
- Pull in metadata and cover art
- Edit or manage chapters
- Support offline listening in mobile apps
- Handle backups
- Offer basic ebook support, including EPUB and PDF formats
How Audiobookshelf Works
1. You add your media files
First, you store your audiobook or podcast files in folders on your server or storage device. These can be audiobook folders, podcast folders, and ebook folders depending on how you set up your libraries. Audiobookshelf supports common audiobook and ebook formats, and its docs show folder-based library structure as an important part of how the scanner works.
2. You point Audiobookshelf to those folders
When you install Audiobookshelf, you map or assign directories for your audiobooks, podcasts, config, and metadata. In Docker setups, this is usually done with mounted folders such as /audiobooks, /podcasts, /config, and /metadata.
3. It scans and builds your library
After that, Audiobookshelf scans your folders and reads metadata from local files. It can pull information from folder names, audio tags, and local metadata files like desc.txt, reader.txt, and.opf files. It can also use embedded cover art when there is no separate image in the book folder.
This scan is different from online matching. A scan reads what is already in your local files and folders. Matching is a separate step used to connect the book to online metadata providers.
4. It stores app data in config and metadata folders
Audiobookshelf keeps important server data in dedicated paths. The /config path stores the database, users, libraries, and settings. The /metadata path stores cache, streams, covers, downloads, backups, and logs. This is one reason these two folders matter so much in setup and troubleshooting.
5. You open it in a browser or app
Once the server is running, you access your library through the Audiobookshelf web client or companion mobile apps. The official docs list Android and iOS apps, with offline listening support described as beta in the feature list.
6. It streams your audio and tracks your progress
When you press play, Audiobookshelf serves the audiobook or podcast from your server to your device. It also saves your listening position and syncs that progress per user across devices. That means you can stop on one device and continue on another.
How Metadata, Covers, and Chapters Work
Audiobookshelf reads metadata from several places depending on your file structure and settings. It can use ID3 tags from audio files for details like title, author, narrator, year, description, genre, and series. It can also pull chapters from supported metadata markers.
For cover art, it usually prefers image files in the book folder first. If there are no folder images, it can extract embedded cover art from the audio file. Online matching can also help apply metadata and cover art from providers when you choose to use that feature.
Where People Usually Run Audiobookshelf
Audiobookshelf can be installed in several ways depending on your setup. The official docs cover Docker, Docker Compose, Linux packages, Podman, reverse proxy setups, and mobile app access. Many users run it on home servers, NAS devices, or small always-on systems.
Common setups include:
- A home server
- A NAS
- A mini PC
- A Raspberry Pi style setup
- A Docker container on Linux or another host
Why People Use Audiobookshelf Instead of Cloud Services
People choose Audiobookshelf because it gives them more control.
Some of the biggest reasons are:
- You keep your own files
- You are not locked into one platform
- You can manage a private family library
- You get better control over metadata and organization
- You can self-host your media instead of relying on a subscription app
- You can combine audiobooks and podcasts in one system
A Simple Real-World Example
Say you have a folder full of audiobook files on your NAS. You install Audiobookshelf with Docker, map your audiobook folder, plus separate config and metadata folders, and let it scan the library. Then Audiobookshelf builds a browsable library with titles, authors, covers, and chapters. From there, you open the web client or mobile app and start listening. Your progress is saved automatically to your account. This workflow matches the official deployment and feature model in the docs.
What You Need to Use It
You do not need a huge server, but you do need a few basics:
- A device to host the server
- Your audiobook or podcast files
- Storage for config and metadata
- A browser or mobile app to listen
- A basic install method such as Docker or a Linux package
Final Thoughts
Audiobookshelf is a private media server built for people who want to organize and stream their own audiobooks and podcasts. It works by scanning your local files, building a library from metadata, storing app data in config and metadata folders, and then serving that content to your browser or mobile app.
