How to Self-Host Audiobookshelf
Audiobookshelf self-hosted audiobook and podcast server with chapter-aware playback, mobile apps, library scanning, progress sync, and downloads. It was added to SelfHub after appearing in What I Self-Host, What I Don't, and Why; the product facts below were checked against the project's official site and source repository.
When Audiobookshelf is a good fit
Choose Audiobookshelf when you want this capability on infrastructure you control and are prepared to own updates, access control, monitoring, and recovery. Review the upstream documentation before selecting a version because deployment requirements can change between releases.
Deployment notes
Run the official container with separate persistent mounts for configuration, metadata, audiobooks, and podcasts. Keep media mounts read-only unless the server must manage files.
Place any browser-accessible interface behind HTTPS. Pin a release rather than an unqualified latest tag, apply updates deliberately, and keep the service reachable only from the networks and users that need it.
Data and recovery
Back up configuration and metadata together; the media library can follow a separate large-file backup policy.
Write down the restore sequence, required secrets, exposed ports, and external dependencies. A scheduled backup is not complete until a clean host can restore it and pass a functional check.
Important limitation
Large library scans and transcoding can be I/O intensive, so place metadata on fast storage and monitor free disk space.
Production checklist
- Pin and record the deployed version.
- Persist every documented data and configuration path.
- Terminate TLS at a maintained reverse proxy or trusted tunnel.
- Restrict administrative interfaces and rotate default credentials.
- Monitor uptime, disk space, certificate expiry, and failed jobs.
- Test an off-host backup with a real restore.
