Audiobookshelf vs Plex for Podcasts: The Library That Isn’t a Movie

Plex will ingest a podcast folder the way it ingests a TV show: season-shaped, poster-shaped, progress that thinks in episodes you already finished on the TV app. Then you walk the dog and want last night’s position, a chapter skip, a 1.2x voice, and an offline download that is not a movie transcode. Plex can be bullied into some of that. Audiobookshelf was built for it. The library is not a movie. Treating it like one is how you get a beautiful grid and a rotten listen.

I ran podcasts in Plex because the server was already there. I moved them when sleep timer, playback speed, and “continue this book” mattered more than matching the rest of the household’s app. Jellyfin has the same gravity. This is about the job, not the logo.

What Plex gets wrong on purpose

Plex’s unit is a video title. Metadata scrapers want IMDB-shaped facts. Podcast RSS is a feed with enclosures, pub dates, and a resume that should be per-item and per-user without pretending it is S03E12. You can use Plex’s music or a custom library type and still fight chapter files, ID3, and mobile clients that were designed for albums or films.

Downloads and cellular are the daily driver. Plex apps can download. They also want an account story, a server that is awake, and sometimes a transcode that makes no sense for AAC. Audiobookshelf’s clients are unashamedly “get this episode on the phone.” That unashamed is the product.

Multi-user in Plex is household profiles for movies. For podcasts you want progress that does not leak between people who share a server but not a commute. Audiobookshelf users are first-class for that job. Plex users are first-class for the other job. Forcing one UI to be both is how someone overwrites your place in a 20-hour book.

What Audiobookshelf gets right

Books and podcasts as types. RSS pull. OPML. Progress that feels like a listening app. Cover art that is a square, not a poster. A web player that is fine and phone apps that are the point. It is a small server with a small job. It does not try to be your 4K pipeline.

It also does not replace Plex. I still run Plex or Jellyfin for video. Audiobookshelf sits beside them. Two containers is cheaper than one container that makes listening bad. Homelab people over-consolidate until the UX is a compromise nobody likes.

Where Audiobookshelf fails like every homelab app

The RSS pull is a cron. Feeds die. Disk fills with enclosures you will never hear. You need a retention policy: keep N episodes, or keep finished, or keep 90 days. Plex at least made you think in files you dropped. Audiobookshelf will happily hoard. Watch the podcast directory the way you watch Immich originals.

Metadata lookups can mismatch a book. You will fix a title by hand. That is still less work than making Plex scrape a podcast as a show.

Auth and exposure: do not put it on the WAN without a mesh or a reverse proxy you meant to run. It is a library of files you care about. Tailscale to the client is enough for a household. Plex remote is a habit that makes people open 32400. Do not copy that habit to a second app. The listening server can stay private. The phone only needs the mesh. If a relative will not install Tailscale, they can keep using Plex on the LAN and you can stop being a helpdesk for a second remote-access story.

Transcoding audio “to help the phone” is usually wasted CPU. Modern phones play the files you have. If they do not, fix the file once. Do not leave a transcoder running like this is 4K HDR. That is movie-server thinking leaking into a walk.

Podcasts versus audiobooks in the same box

Audiobookshelf handles both. Good. Do not mix them in one sloppy folder. Books want authors and series. Podcasts want feeds. Separate libraries. Your future self will thank you when a scraper tries to turn a news daily into a novel.

Chapter files and embedded chapters are why people leave Plex. A 12-hour nonfiction book without chapters in Plex is a scrub bar from hell. Audiobookshelf treats chapters as normal. If your files lack chapters, the server cannot invent a good book. Tag them. The folder structure is still your job, like it was in Plex.

Offline, cellular, and the lie of “the server is at home”

A commute through a tunnel does not care that your NAS is up. The file has to be on the phone. Audiobookshelf’s download UX is built around that. Plex downloads exist and still feel like a video feature that happens to work on an mp3. When a download fails, Plex users debug remote access. Audiobookshelf users debug the episode. I know which debug I want before coffee.

Streaming from home on LTE is a second tax: you are the CDN. Fine on unlimited home uplink. Mean on a travel eSIM. Download overnight on Wi-Fi. This is obvious and still how people blow a travel plan “testing Plex remote.” The listening app should make offline the default for a commute playlist. If it does not, it is a movie app.

Sleep timers and fade-out are not cute. They are how a book does not play for three hours into a pillow. Plex clients vary. Audiobookshelf treats this as table stakes. If you fall asleep to nonfiction, this one feature is the migration.

Sharing with a household that only has Plex

A partner who already has Plex on the TV will not install another app for a weekly podcast they play in the kitchen. Leave a copy in Plex for them if you must. You keep Audiobookshelf for the commute. Dual-write is messy. A shared kitchen speaker on Plex plus your phone on Audiobookshelf is acceptable. Progress will not sync. Accept that or accept their app. Do not fight a kitchen display into a listening specialist.

Kids’ sleep stories are a third case. A simple Plex playlist on a TV might beat a second login. Specialists are for the listener who cares. Shared ambient audio can stay dumb.

When Plex is still enough

You already live in Plex on the TV and you only play the occasional podcast on that TV. You do not need speed control. You do not commute with downloads. Stay. Adding Audiobookshelf for three episodes a year is a container you will not update.

When you listen every day on a phone, add the specialist. Keep video where it is. Do not migrate movies into Audiobookshelf out of spite. It is not a movie app. That is the compliment.

A split I run

Jellyfin or Plex for video. Audiobookshelf for books and podcasts. Navidrome if I still want music separately. Each app has a client I actually open. Progress stays in the right database. Backups are per-app. Two extra containers is less pain than one progress bug in a 30-hour series.

RSS into Audiobookshelf, not into a Plex watch folder I forget to prune. Prune in the app. Confirm disk. The movie library can stay huge. The podcast library should not silently become huge.

The close

Plex is a movie factory that can store audio. Audiobookshelf is a listening library that will not pretend your feed is a season. If the commute is the player, use the specialist. If the TV is the player, Plex is already there. The library that is not a movie should not live in a movie app just because the NAS already had a poster wall.

Backup the Audiobookshelf config and the media tree. Progress is in the database. If you only rsync mp3s you will restore files and lose the place you were in chapter 14. That restore feels like Plex watching you from the other container: you got the bytes and lost the human state. Include the database in the restic path. Test a restore onto a throwaway compose project. Listening libraries have state. Movie posters do not need your minute count. Books do.