Managing media ownership with Audiobookshelf

Managing media ownership and server setup

Families wanting to own their media collections choose self-hosted servers like Audiobookshelf to manage audiobooks and podcasts. This software is a direct alternative to subscription models where companies like Amazon or Spotify rent content to users. Users can purchase DRM-free files from stores like Libro.fm or Downpour and upload them to a personal server. This method avoids the limitations of proprietary formats like Audible’s AAX files. A basic $6 per month DigitalOcean droplet with 1GB of RAM and 25GB of SSD accommodates roughly 500 hours of audiobooks, assuming files consume 25 to 50 MB per hour.

To start a server on a Linux distribution, users create a docker-compose.yml file using the nano editor and use the chmod utility to grant read and write permissions to that file. You can then run the docker compose command to deploy the container and access the interface via port 13378. For Proxmox users, a community-managed script exists to create an LXC container via the command bash -c "$(wget -qLO - https://github.com/community-scripts/ProxmoxVE/raw/main/ct/audiobookshelf.sh)". Setting up a dedicated user profile for family members allows everyone to maintain their own personalized bookmarks and progress. After logging in, users navigate to the Libraries tab, select Add Library, choose a folder path, and pick a media type like Podcasts or Books. Users then use the Upload button and the Choose files option to add content to the collection.

Features and mobile application status

The application manages multi-user environments where each person maintains custom permissions and independent listening progress. Recent updates, such as version 2.37.2 from October 2026, include improvements to the interface. The developers replaced old SVG icons with Material-Symbols to create a modern look. Version 2.29 added a chapter editor with bulk import capabilities and sorting options like "Progress: Started" or "Progress: Finished." While these features help organize large collections, some users reported issues with metadata retrieval where book covers appeared but synopsis and author data remained blank. Users can fix these issues by using the "Match Books" tool to scour the internet for metadata or by manually selecting a match via the ISBN number.

The mobile experience remains a primary development goal, though the status varies by platform. The development of the mobile application remains a primary focus for the project. Android users download the app from the Google Play Store, while iOS users must use TestFlight, which limits users to 10,000 beta testers. The Android app provides more features than the iOS version, but the team plans to standardize both. Users can also use a Progressive Web App (PWA) for access, though this method does not support offline use. If the iOS beta remains full, users can download Plappa from the App Store to connect to their server. One user reported that version 2.13.3 failed to save correct play status on Android Auto when switching between two different books.

Deployment and technical requirements

Deploying the server requires several technical steps depending on the chosen environment. Users can use the community-managed VE-Helper Scripts to create an LXC container on Proxmox by pasting a command into the terminal. For those using Ubuntu, the process involves installing the Docker engine and configuring a docker-compose.yml file. Users can deploy Audiobookshelf inside a Docker container on a Linux distribution by creating a docker-compose.yml file and using the chmod utility to grant the necessary read and write permissions to that specific configuration file. Secure remote access requires a domain name and the use of Cloudflare Tunnels to avoid opening ports on a home router. The application requires a websocket connection to function properly.

The project relies on a small team of developers working in their free time, so they prioritize human oversight for all code contributions. They do not accept or review pull requests that appear to be fully AI-generated with little or no human oversight. The team recently fixed a bug where the initial page load failed during token refreshes and addressed a folder browser issue on Windows 11 by replacing wmic with powershell. The software also supports merging audio files into a single m4b and fetching metadata from several sources. The project builds on NodeJs and allows for bulk uploads through a drag and drop interface. Will the current pace of updates continue as the project grows?