On a Raspberry Pi 4 8GB in 2026, Jellyfin reliably serves direct-play video to two or three simultaneous local clients, one remote client at 1080p H.264, and one 1080p H.265 to H.264 CPU transcode at a time. Push past those limits and the Pi 4's CPU pegs at 100% and the stream buffers. For a family library streamed to phones, tablets, and one TV, it's plenty. For 4K anything or three concurrent transcodes, it isn't — that's a Pi 5, N100 mini-PC, or NUC problem.
Why the Pi 4 8GB is still a real Jellyfin platform in 2026
The Pi 5 has been out for two years, and the Pi 6 is expected soon. Yet the Raspberry Pi 4 8GB remains one of the most cost-effective platforms for self-hosted media because it does three things that matter for a lightweight Jellyfin box: it draws under 10W at idle, it decodes H.264 in hardware, and its 8GB of RAM is enough to hold a modest metadata cache in memory. That combination costs $75–$95 with the board plus a case; a Pi 5 8GB with case is $90–$110. The gap is small enough that plenty of home labs run whichever they have on hand, and the Pi 4's efficiency edge holds for pure media serving.
The catch is that Jellyfin's transcoding needs are the exception the Pi 4 struggles with. When a client can't play a codec natively (mostly: an older iPhone hitting a 10-bit HEVC file), Jellyfin has to transcode on the CPU. The Pi 4's Cortex-A72 quad-core at 1.5 GHz gets one 1080p H.264 CPU transcode done in near real-time and chokes on anything harder.
Key takeaways
- Direct-play delivery on the Pi 4 8GB is limited by network bandwidth, not the Pi. Multiple 1080p direct-play streams work fine.
- CPU-side H.265 → H.264 transcoding on the Pi 4 tops out at one concurrent 1080p session; forget 4K transcoding.
- Hardware H.264 decode via V4L2 M2M works well for playback but not encoding — Pi 4's video encoder is not a Jellyfin path.
- SD card is the wrong OS storage; use a USB SSD (like Crucial BX500 + adapter) for read latency and thermal safety.
- For 4K libraries, expect direct-play only; do not attempt transcoding.
Compute + memory breakdown
The Pi 4 8GB pairs a Broadcom BCM2711 quad-core Cortex-A72 at 1.5 GHz with 8 GB of LPDDR4-3200. On the SoC there's a VideoCore VI GPU, and — importantly for Jellyfin — a V4L2 M2M path for hardware H.264 decode. Encoding hardware exists but is not integrated with Jellyfin's ffmpeg build in a supported way in 2026, so all transcodes hit the CPU.
Per public Jellyfin community benchmark threads and r/selfhosted posts, this shakes out to:
| Scenario | CPU load | Verdict |
|---|---|---|
| 1 client, 1080p H.264 direct-play | 5–8% | Trivial |
| 3 clients, all 1080p direct-play | 15–25% | Fine, network-bound |
| 1 client, 1080p H.264 CPU transcode | 65–85% | Marginal — one at a time |
| 1 client, 1080p HEVC 10-bit → H.264 transcode | 90–100% | Buffers if HEVC has heavy grain |
| 2 concurrent transcodes | 100% both cores | Both buffer |
| 4K H.264 direct-play | 20–30% | Fine if client supports it |
| 4K HEVC direct-play | 25–35% | Fine, GPU decodes |
| 4K → 1080p transcode | 100% + queue | Do not attempt |
The right architecture for a Pi 4 Jellyfin box is: pre-encode your library to H.264 (yes, this loses the space savings of HEVC), or accept that any client that can't direct-play will buffer.
Storage: SD card kills this workload
The single biggest reliability issue with a Pi 4 Jellyfin box is running the OS off the boot SD card. SD cards have terrible random-write latency, and Jellyfin's metadata database (SQLite) writes on every scan, view, and playback event. On an SD card, the Jellyfin process routinely stalls for 500 ms to 2 s during scans; on a USB 3.0 SSD, those stalls disappear.
The cheap fix is a Crucial BX500 240GB or 500GB SATA SSD in a USB 3.0 SATA-to-USB adapter (like the Unitek SATA/IDE to USB 3.0 Adapter). Total add-on cost: $45–$60 for the SSD and $10–$15 for the adapter. The Pi 4 supports USB boot natively, so no SD card needed at all.
Media storage is separate: a bigger external drive over USB 3.0 handles the library. Any 4–8 TB external drive works. Do not put the library on the same drive as the OS — separate spindles keep scan latency out of playback latency.
Networking and remote access
Gigabit Ethernet on the Pi 4 is fully wired (unlike the Pi 3B+, which shared USB and Ethernet bandwidth). Direct-play throughput saturates at real-world 900+ Mbps in local benchmarks — comfortably enough for four 1080p direct-play streams or one 4K H.264 direct-play stream.
Remote access is where the Pi 4 shows its age. Jellyfin's own remote-user experience depends on either exposing the port (bad) or running a reverse proxy plus a Tailscale / WireGuard tunnel (good). The Pi 4 handles a WireGuard endpoint fine — the SoC has AES-NI-equivalent crypto acceleration through its ARMv8 crypto extensions, and single-stream WireGuard bandwidth on the Pi 4 lands in the 400–600 Mbps range per community measurements. Adequate for one remote 1080p stream, not two.
Build spec — what actually to buy
- Board: Raspberry Pi 4 Model B 8GB — ~$75
- Boot drive: Crucial BX500 240 GB SATA SSD — ~$25 (or 500GB for a bigger metadata cache)
- USB-to-SATA adapter: Unitek SATA-to-USB 3.0 — ~$15
- Media drive: external 4TB USB 3.0 hard drive — ~$85
- Case + cooler: metal case with heat sink and PWM fan (Argon One M.2 recommended) — ~$25
- Power supply: official Pi 4 USB-C PSU (5V/3A) — ~$8
- microSD or USB thumb drive: unnecessary if booting from SSD
Total: ~$233 including 4 TB of storage. Compare to a used NUC or N100 mini-PC at $180–$250 with more headroom. The Pi 4 wins on power draw and enclosure size; the NUC wins on transcoding capability.
Real-world numbers under measured load
- Idle: 3.5–4.5 W board power, 40–45 °C core temp with a decent cooler.
- 1 stream 1080p direct-play: 4.5–5.5 W, 45–50 °C.
- 1 stream 1080p CPU transcode HEVC → H.264: 8–9 W, 68–75 °C without a fan, 55–60 °C with a fan.
- 2 concurrent transcodes: throttles into the 78–82 °C range without a fan — thermal throttling drops clock speed and stream buffers.
The takeaway: a passively cooled Pi 4 works for direct-play scenarios; a fan-cooled Pi 4 (Argon One M.2 or similar) is required for reliable single-transcode work.
When to walk away from the Pi 4
You should not use a Pi 4 8GB for Jellyfin if any of these apply:
- Your library is mostly 4K HEVC 10-bit and clients don't support direct-play — you'll transcode constantly, and the Pi 4 chokes.
- You have three or more household members simultaneously watching from outside the LAN, requiring transcoding for varying client caps.
- You want Jellyfin's hardware-accelerated transcoding (HW encode) — supported on Pi 5, Intel N-series, and NVIDIA GPUs, but not the Pi 4.
- You want to run Jellyfin alongside other heavy services (Nextcloud, Immich, Home Assistant) on the same box.
For those cases, either a Pi 5 8GB, an Intel N100 mini-PC, or a used i5-8500-class NUC lands in the $150–$280 range and eliminates the transcoding cliff.
Common pitfalls
- Running the OS from the SD card and complaining about lag. Move to USB SSD boot on day one.
- Skipping the fan. The Pi 4 thermally throttles at 80 °C, and a single transcode gets you there in five minutes without a fan.
- Enabling HEVC transcoding globally. Turn off HEVC → H.264 transcoding in Jellyfin's dashboard for specific clients that direct-play HEVC; the default settings force transcodes the Pi can't handle.
- Trying to run Jellyfin + Plex + Emby on the same box. Pick one media server; the metadata scans compete for the same SSD.
Bottom line
A Pi 4 8GB is a viable Jellyfin box in 2026 if your workload is direct-play-heavy, your library is mostly H.264, and you have a maximum of two remote streams. Put the OS on a USB SSD, add a fan, put the media on an external drive, and you have a $230-ish media server that draws less power than the LED strip behind your TV. For anything above that — 4K, HEVC, or concurrent transcoding — buy a Pi 5 or an N100 mini-PC.
Related guides
- Network-Wide Ad Blocking with Pi-hole on a Raspberry Pi 4 8GB (2026 Setup)
- Raspberry Pi OS Moves to Linux 6.18 LTS: Performance Gains for Pi 4 Owners
Citations and sources
- Raspberry Pi Foundation — Pi 4 Model B product page
- Jellyfin — official site and documentation
- Jellyfin community forum — Pi 4 benchmark threads
- Crucial BX500 SATA SSD page
- r/selfhosted — Jellyfin Pi performance discussions
- Argon40 — Argon ONE M.2 case
This piece is editorial synthesis based on publicly available information. No independent first-party benchmarking is reported.
