English
Audiobookshelf Hosting
Organize and stream audiobooks and podcasts with progress syncing across devices.
No setup fees-
One click deploy -
1 GB RAM Memory needed -
15 GB Disk Space Needed -
From 2 € Price
Official links
Audiobookshelf’s official links and original website
Audiobookshelf Website
More
Tech
- Docker image
- ghcr.io/advplyr/audiobookshelf:latest
- Default port
- 80
How Audiobookshelf works
Audiobookshelf scans configured media folders and builds libraries for audiobooks, podcasts, and supported ebooks. It reads file and folder metadata, can obtain covers or details from configured providers, and presents the collection through a web interface and supported mobile clients. Playback progress, bookmarks, users, and library settings remain associated with the server.
Podcast libraries can follow feeds and download episodes according to configured rules, while audiobook tools help manage chapters and metadata. The server does not provide commercial audiobook access. Users must supply files they are entitled to store, and external metadata or podcast sources retain their own availability, terms, and rate limits.
Key Audiobookshelf features
Separate libraries keep audiobooks, podcasts, and ebooks organised, while user permissions limit which collections each account may access. Progress synchronisation helps a listener continue on another approved device, and supported mobile applications can download media for offline listening. Chapter and metadata tools improve navigation through long recordings.
Automatic podcast downloads and metadata matching need review. Feeds can disappear, publishers can change episode files, and metadata providers may return inaccurate or incomplete results. Large audio collections also consume storage quickly, especially when several podcast feeds retain many episodes.
Who uses Audiobookshelf
Families can share an audiobook collection with separate progress, collectors can replace folder browsing with a searchable catalogue, and podcast listeners can archive approved feeds on their own server. It also fits small clubs that distribute recordings they have permission to share.
The application is not a storefront, subscription catalogue, or digital-rights bypass. Users remain responsible for copyright, account permissions, source terms, and the security of any media exposed through the server.
Self-hosting Audiobookshelf: requirements and cost
Audiobookshelf resource use is driven by library size, scans, metadata, cover art, podcast downloads, simultaneous streams, mobile synchronisation, and audio processing. The catalogue says a separate database is Not required; persistent volumes hold configuration, metadata, and media. Storage, rather than application memory, is usually the practical limit for a growing collection.
AvaHost maps Audiobookshelf to Plan 1 at €2. Audiobookshelf includes one-click setup, automated HTTPS for its custom domain, application updates, and scheduled backups. The plan does not include audiobooks, podcasts, ebooks, or metadata-provider subscriptions. For a meaningful audio library, 50 GB on Plan 3 is a realistic starting point, while 100 GB on Plan 4 better suits a large collection.
F.A.Q
Audiobookshelf starts at €2 on Plan 1. Library size, scans, artwork, podcast downloads, simultaneous streams, mobile synchronisation, and audio processing affect demand. Storage is the main constraint: Plan 3 includes 50 GB, while Plan 4 provides 100 GB for a larger audiobook or podcast collection.
Not required. The catalogue deployment uses persistent volumes for configuration, metadata, and media without a PostgreSQL or MariaDB container. Protect those volumes together because library records, covers, progress, and audio files form one service. Scheduled backups are included, but users should retain independent lawful copies of irreplaceable source media.
A custom hostname can serve Audiobookshelf with automated HTTPS once DNS points to AvaHost. Enter the final server address in supported clients and verify sign-in, streaming, downloads, progress sync, covers, and podcast feeds. After changing domains, remove obsolete addresses from devices so users do not continue connecting to the earlier endpoint.
The hosting plan supplies the server application, not a media catalogue. Users must upload audiobooks, podcasts, and ebooks they are entitled to store, or configure permitted podcast feeds and metadata sources. Provider accounts, source availability, copyright clearance, and mobile application behaviour remain separate. Large libraries should begin with more storage than the minimum plan.