Why I switched from Plex to Jellyfin after 4 years - honest comparison
Description and use
The author switched from Plex to Jellyfin due to new paywall features and high CPU usage, keeping a free, open‑source server with low resource consumption.
Problem
Plex’s recent paywall changes and high CPU usage for transcoding on a low‑end NAS prompted a switch to a free, open‑source alternative.
Outcome
The migration took a weekend, saved $120/year, reduced CPU load, and provided a fully free, open‑source media server with native photo support.
Workflow
- Set up Jellyfin in docker‑compose alongside Plex (port 8096 for Jellyfin, Plex stays on 32400)
- Point both at the same /media directory
- Run both for a week and compare UX
- After 7 days of side‑by‑side: choose Jellyfin
- Tear down Plex and drop the port
Evidence
The breaking point was the 2025 Plex "pass" changes — when they started requiring a Plex Pass subscription for hardware-accelerated transcoding that used to be free.
Jellyfin's hwaccel (Intel QuickSync) uses ~5% CPU for the same workload.
The migration took a weekend
Jellyfin 10.9 in Docker on Synology DS220+
- Record date: 2026-10-19T21:41:10.980Z