I used to pay for three different streaming subscriptions simultaneously — and still couldn’t find anything I actually wanted to watch. Then I built a Raspberry Pi 5 media server running Jellyfin, loaded it up with my ripped movie collection and favorite shows, and haven’t looked back. The interface looks like Netflix, it streams to every TV and device in the house, and the whole setup cost less than one year of those subscriptions combined.
The Raspberry Pi 5 media server is genuinely one of the best value self-hosting projects you can build. The Pi 5 brought real processing improvements over the Pi 4, NVMe storage is now possible via the M.2 HAT, and Jellyfin has matured into a polished, no-subscription alternative to Plex. If you’ve been thinking about doing this, 2026 is the best time it’s ever been to pull the trigger.
Why the Raspberry Pi 5 Media Server Hits Different in 2026
The Pi 4 was capable but showed its limits when multiple streams were running or transcoding was required. The Pi 5 changed things. With a 2.4GHz quad-core Cortex-A76, it’s roughly 2–3x faster than the Pi 4 at CPU-intensive tasks. For a Raspberry Pi 5 media server running Jellyfin, that means you can comfortably handle 2–3 direct-play streams simultaneously without the Pi breaking a sweat.
The other big upgrade: PCIe via the M.2 HAT+. You can now attach an NVMe SSD directly to the Pi 5 and get significantly faster read speeds than any USB drive setup. For a media server with a large library, this matters — library scans complete faster, large file seeks are instant, and the storage doesn’t become a bottleneck. A 2TB NVMe drive holds a solid media library and costs around $80–$100.
One thing to know upfront: transcoding is limited. The Pi 5 removed the hardware video encoder from the Pi 4. Software transcoding works on the faster CPU, but if all your clients support direct play (Jellyfin app on Roku, Fire TV, Apple TV, or a browser), transcoding becomes a non-issue. Most modern devices do. Plan for direct play and you’re golden.
The Hardware You’ll Need
Here’s what a solid Raspberry Pi 5 media server build looks like:
The board: The Raspberry Pi 5 (8GB) is the one to get for a media server. The extra RAM gives you headroom to run Jellyfin alongside other Docker containers — Pi-hole, WireGuard, whatever else you’re self-hosting. At the price point, it’s not worth skimping on RAM for this use case.
The Raspberry Pi M.2 HAT+ is what unlocks NVMe storage. It attaches to the Pi’s PCIe connector and gives you an M.2 2230 or 2242 slot. Pair it with a 1–2TB NVMe SSD and you’ve got a real media server, not a glorified USB stick situation.
- Convenient Connectivity: It features a single-lane PCIe 2.0 interface (500 MB/s peak transfer rate), and supports devices that use the M.2 M key edge connector and the 2230 or 2242 form factor.
- Compatibility with Raspberry Pi 5: Specifically designed for the Raspberry Pi 5 and fitted to a Raspberry Pi 5 with the Raspberry Pi Active Cooler in place.
- Various Peripheral Accessories:Supplied with ribbon cable, 16mm stacking header, threaded spacers and screws, and knurled double-flanged screw to secure and support the M.2 peripheral.
You’ll also want a proper case with cooling — the Pi 5 runs hotter under sustained load than the Pi 4. The Argon NEO 5 or the official Pi 5 case with active cooler both work well. And don’t cheap out on the power supply: the Pi 5 needs a 27W USB-C PSU, especially with the HAT+ and NVMe drawing additional power.
Installing Jellyfin on Your Raspberry Pi 5 Media Server
Jellyfin runs great in Docker on the Pi 5. Here’s the minimal docker-compose.yml to get it running:
services:
jellyfin:
image: jellyfin/jellyfin:latest
container_name: jellyfin
network_mode: host
volumes:
- ./config:/config
- ./cache:/cache
- /mnt/media:/media:ro
restart: unless-stoppedPoint /mnt/media to wherever your NVMe or external drive is mounted. Run docker compose up -d, then browse to http://PI-IP:8096 for the setup wizard. It walks you through adding your media libraries, and Jellyfin handles the rest — scanning, pulling metadata, building your library. First scan takes a few minutes depending on library size, then it’s instant going forward.
Want it on a clean domain with HTTPS instead of :8096? Set up Nginx Proxy Manager in front of it — it takes about 5 minutes once NPM is running.
What About Plex?
Plex is the other big name in self-hosted media servers, and it runs on the Pi 5 fine. The key differences: Plex requires a Plex Pass subscription ($5–$120/year) for hardware transcoding and some app features. Jellyfin is fully free and open-source, no subscription, no account required. For a Pi 5 where transcoding is limited anyway, Jellyfin is the better fit. You’re not paying for features you can’t fully use.
If you have a Plex Pass already and love the ecosystem, Plex works on the Pi 5. But for anyone starting fresh, Jellyfin is what I’d reach for in 2026. The app support has caught up — it’s on Roku, Fire TV, Apple TV, Android TV, iOS, Android, and every major browser.
The Takeaway
A Raspberry Pi 5 media server running Jellyfin is one of the most satisfying self-hosting projects you can build. The hardware is affordable, the software is free and polished, and the end result is a private streaming service that’s entirely yours — no algorithm, no price hikes, no content disappearing overnight. If you’re building out a homelab, this is a great first or second project to add after you’ve got your basic server and networking sorted.
The key is setting up direct play properly so transcoding doesn’t become an issue. Get the Pi 5 with 8GB of RAM, add the M.2 HAT with an NVMe drive, and you’ll have a media server that runs circles around whatever streaming subscription you’re currently paying for.
What’s in Your Jellyfin Library?
Are you running Jellyfin, Plex, or something else for your home media server? Drop your setup in the comments — I’m always curious what people are running and what storage solution they landed on. If this helped you get your Raspberry Pi 5 media server off the ground, pass it along to someone who’s still squinting at subscription prices.