Should you buy a Raspberry Pi 5 or a Pi 4 8GB for a 2026 homelab?
Buy the Pi 5 if you plan to run more than three or four containers, host a Postgres/Plex/Immich stack, or want NVMe-class storage. Buy the Raspberry Pi 4 Computer Model B 8GB if you want the cheapest well-supported always-on node for Pi-hole, Home Assistant, a Samba share, or a mixed-fleet worker where per-watt cost matters more than raw CPU. For most 24/7 homelabs in 2026 the Pi 5 wins on throughput; the Pi 4 8GB wins on price, power, and maturity.
The Pi 5 launch reset the value math — where the Pi 4 8GB still wins
The Pi 5 launched in late 2023 and by 2026 has settled into steady supply and mature software. Per raspberrypi.com's Pi 5 product page, the board delivers "2-3x the performance" of the Pi 4 on most workloads, with a native PCIe 2.0 lane exposed via a dedicated connector and dual 4Kp60 HDMI output. That is a bigger single-generation jump than the Pi 4 delivered over the Pi 3 back in 2019, and it means workloads that used to spill off the Pi 4 — light media transcoding, self-hosted photo libraries, moderate Postgres, multi-container Docker stacks — now fit comfortably on a single board.
The math that changed is not just "Pi 5 is faster." It is that the Pi 5 finally makes a single-board homelab viable for services that previously required either a used Optiplex micro-desktop or a cluster of Pis. Per Jeff Geerling's Pi 5 review, the Cortex-A76 cores at 2.4 GHz, LPDDR4X-4267 memory, and the dedicated southbridge (RP1) collectively unblock the I/O bottlenecks that made a Pi 4 feel sluggish under real load.
But "faster and better I/O" is not the same as "better for every homelab." The Pi 4 8GB is still in production, still gets kernel updates, still runs the same Raspberry Pi OS, HAOS, DietPi, and Ubuntu images, and now sits at a price roughly 30-40 percent below a Pi 5 8GB kit once you factor in the Pi 5's required active cooler and higher-wattage 27W USB-C PD supply. Per the Raspberry Pi 4 Model B product page, the board's four USB ports (two USB 3.0 + two USB 2.0), gigabit Ethernet, and dual micro-HDMI outputs are still more than adequate for the vast majority of homelab roles. The Pi 4 also draws less at idle, which compounds meaningfully across a 24/7 duty cycle.
Below is the framework for choosing: spec-delta, benchmarks under real homelab workloads, power/cooling reality, storage strategy, per-dollar and per-watt math, and a verdict matrix keyed to specific services.
Key takeaways
- Buy the Pi 5 for Postgres-backed apps, multi-container Docker/Podman stacks (5+ containers), Immich or Photoprism, Plex/Jellyfin transcodes, or any workload that benefits from PCIe NVMe storage.
- Buy the Pi 4 8GB for Pi-hole, Home Assistant, AdGuard, Samba/NFS file share, single-container edge workloads, or as a low-power sidecar in a mixed Pi fleet.
- Avoid the Pi 5 2GB for anything but a single dedicated service — the 2GB SKU exists to hit a lower price, not to run a stack.
- Move off SD cards for anything that writes frequently. A Crucial BX500 1TB SATA SSD over a USB 3.0 UASP-capable adapter is the cheapest reliable path on the Pi 4; a proper NVMe HAT is preferred on the Pi 5.
- Add a Pi Zero W like the Raspberry Pi Zero W Basic Starter Kit for a single sub-1W service (sensor gateway, remote button, one-purpose MQTT broker) rather than dedicating a full-size Pi to it.
- Perf-per-watt still favors the Pi 4 8GB at idle; perf-per-watt favors the Pi 5 under sustained load.
Spec delta: Pi 5 vs Pi 4 8GB
The two boards share a form factor and the 40-pin GPIO header, but almost every other spec has moved. The Pi 5 uses the BCM2712 SoC with four Cortex-A76 cores at 2.4 GHz; the Pi 4 uses the older BCM2711 with four Cortex-A72 cores at 1.8 GHz. The RP1 southbridge on the Pi 5 handles all peripheral I/O — a dedicated die that removes the USB and Ethernet bottlenecks that limited the Pi 4.
| Spec | Raspberry Pi 5 | Raspberry Pi 4 8GB |
|---|---|---|
| SoC | Broadcom BCM2712 | Broadcom BCM2711 |
| CPU | 4x Cortex-A76 @ 2.4 GHz | 4x Cortex-A72 @ 1.8 GHz |
| RAM | LPDDR4X-4267 (2 / 4 / 8 / 16 GB) | LPDDR4-3200 (8 GB) |
| GPU | VideoCore VII @ 800 MHz | VideoCore VI @ 500 MHz |
| USB 3.0 | 2 (dedicated controller each) | 2 (shared bandwidth) |
| PCIe | 1x PCIe 2.0 lane (FPC) | none |
| Ethernet | Gigabit (full-duplex, PoE+ HAT) | Gigabit (PoE HAT) |
| HDMI | 2x micro-HDMI 4Kp60 | 2x micro-HDMI 4Kp60 (single-display) |
| Power input | USB-C PD, 5V/5A (27W supply) | USB-C, 5V/3A (15W supply) |
| Idle power | ~3.0W | ~2.7W |
| Load power (sustained) | ~9-12W | ~6-7W |
| Active cooler | Required for sustained load | Optional (heatsink sufficient) |
| MSRP | $50 (2GB) / $60 (4GB) / $80 (8GB) / $120 (16GB) | $75 (8GB, street 2026) |
Per raspberrypi.com's Pi 5 datasheet, the exposed PCIe 2.0 x1 lane is the single biggest architectural change and the reason NVMe HATs are now practical. Per Phoronix's Pi 5 review, sustained CPU throughput on tasks like Blender BMW rendering, PostgreSQL pgbench, and Redis GET/SET is roughly 2-3x the Pi 4, with memory-bound workloads seeing the largest gains due to LPDDR4X-4267 versus the Pi 4's LPDDR4-3200.
Benchmarks under real homelab workloads
Synthetic benchmarks are a starting point, but homelab operators care about "how many containers can I run" and "does Plex transcode." The table below compiles publicly reported numbers.
| Workload | Pi 5 8GB | Pi 4 8GB | Source |
|---|---|---|---|
| Docker containers (idle, mixed nginx+redis+postgres) | ~40 comfortable, ~60 stress | ~15 comfortable, ~25 stress | jeffgeerling.com |
| PostgreSQL pgbench (read-only, scale 10) | ~14,000 TPS | ~5,200 TPS | phoronix.com |
| Redis GET (1M keys, single client) | ~145,000 ops/sec | ~62,000 ops/sec | phoronix.com |
| Plex transcode 1080p H.264 to 720p (SW) | 1 stream real-time | not viable | jeffgeerling.com |
| llama.cpp TinyLlama-1.1B Q4_K_M | ~11 tok/s | ~4 tok/s | github.com/ggerganov/llama.cpp |
| Samba throughput (gigabit, NVMe/SSD backed) | ~112 MB/s (line rate) | ~110 MB/s (line rate) | jeffgeerling.com |
| Pi-hole DNS queries/sec sustained | ~2,500+ | ~2,000+ | github.com/pi-hole/pi-hole |
| Home Assistant integration count (comfort) | 100+ | 60-80 | community.home-assistant.io |
| nginx static (wrk, keepalive) | ~65,000 req/s | ~28,000 req/s | phoronix.com |
Per Jeff Geerling's homelab container density post, the Pi 5's improved memory bandwidth plus the RP1 southbridge lets it host roughly 2.5-3x the container count of a Pi 4 before response times degrade. Per Phoronix's Pi 5 benchmarks, the delta is largest on memory-bound and I/O-bound workloads and smallest on pure network-bound workloads like Samba, where gigabit Ethernet is the ceiling for both boards.
The Plex line is the clearest fork in the road: per Jeff Geerling's transcoding tests, the Pi 5 can do one real-time software 1080p-to-720p H.264 transcode; the Pi 4 8GB cannot sustain that. Anyone whose homelab plan includes Plex or Jellyfin with any transcode load should assume the Pi 5.
Power and cooling: idle/load watts and why it matters
For an always-on node, small wattage differences compound into real dollars. Per raspberrypi.com's Pi 5 datasheet, the Pi 5 requires a 5V/5A USB-C PD supply (27W) to guarantee full downstream USB current, versus the Pi 4's 5V/3A (15W) requirement. Actual draw is lower — Pi 5 idles around 3.0W and hits 9-12W under sustained all-core load; Pi 4 idles around 2.7W and hits 6-7W under load.
Multiply that out. A 24/7 Pi 4 8GB at an average 3W draws roughly 26 kWh/year; the same Pi 5 at an average 4W draws about 35 kWh/year. At US average residential rates near $0.16/kWh in 2026, that is roughly $4/year versus $5.60/year — a rounding error for one board, but meaningful in a five-node homelab where the delta becomes ~$8/year plus the cost of larger PSUs and better cooling.
Cooling is the other operational cost. Per raspberrypi.com's Pi 5 active cooler page, the Pi 5's default behavior without a cooler is to throttle at ~85°C, which under sustained load happens within minutes. The active cooler is effectively required for any workload that pins CPU for more than short bursts. The Pi 4 8GB, by contrast, holds acceptable temperatures with a passive heatsink in most cases and only needs a fan if it lives in a hot enclosure or an attic. This is a real deployment-friction difference: the Pi 4 is more forgiving of "shove it in a cabinet and forget it."
Storage: SATA SSD over USB vs NVMe HAT
SD-card storage is the biggest source of Pi homelab failures. Per Jeff Geerling's SD-card endurance tracking, even "endurance" cards eventually wear out on write-heavy workloads like Home Assistant history, Prometheus scraping, or Docker container logs. The fix is to move root and data onto a real SSD.
On the Pi 4, the affordable path is a SATA SSD in a USB 3.0 UASP-capable enclosure. A Crucial BX500 1TB SATA SSD paired with a well-behaved USB 3.0-to-SATA bridge (JMicron JMS578 or ASMedia ASM1153E chipsets are the safest bets) delivers around 350-400 MB/s sequential and orders-of-magnitude better random-write endurance than any SD card. The Pi 4's two USB 3.0 ports share bandwidth with each other but are still ample for one SSD plus a keyboard or camera.
On the Pi 5, the PCIe 2.0 x1 lane enables NVMe HATs (Pimoroni NVMe Base, Pineberry Pi HatDrive, Waveshare M.2 HAT, and the official Raspberry Pi M.2 HAT+ per raspberrypi.com's M.2 HAT+ page). A 2242 or 2280 NVMe SSD on that lane delivers ~450-500 MB/s in practice — capped by PCIe 2.0 x1 bandwidth (~500 MB/s theoretical), not the drive. That is only marginally faster than USB 3.0 SATA on paper, but latency, random I/O, and reliability are substantially better because there is no USB translation layer.
If storage speed matters (Postgres, Immich thumbnails, Docker layers, container logs at scale), go Pi 5 with an NVMe HAT. If storage is mostly cold (Samba archive, sporadic Home Assistant DB), a Pi 4 with a SATA SSD over USB is entirely adequate and cheaper.
Perf-per-dollar and perf-per-watt for a 24/7 node
At 2026 street pricing (Pi 5 8GB kit around $95 board-only, ~$130 kit; Pi 4 8GB around $75 board-only, ~$105 kit), the Pi 4 comes out ahead on straight perf-per-dollar for lightweight workloads and behind on perf-per-dollar for heavy ones. The Pi 5 is roughly 27 percent more expensive at the board level and delivers roughly 2-2.5x the performance on real workloads — a favorable ratio when your services actually need it, and dead weight when they don't.
Perf-per-watt is more nuanced. At idle the Pi 4 wins. Under sustained load the Pi 5 wins — its A76 cores at 2.4 GHz finish work faster and race-to-idle, so total energy for a fixed job (transcode, backup, index build) is lower on the Pi 5. This matters if your workload is bursty: the Pi 5 finishes and drops back to ~3W. If your workload is a flat idle line 90 percent of the time, the Pi 4 8GB saves a couple of watts continuously.
Practical rule: for a lightly-loaded single-purpose always-on node (Pi-hole, Home Assistant hub, single Samba share), the Pi 4 8GB is the cheaper and lower-power choice. For anything that periodically works hard (Docker stack, Postgres, media server, backup target, Photoprism/Immich indexer), the Pi 5 pays for itself in wall-clock time and total energy.
Verdict matrix
Get the Pi 5 if...
- You run 5+ Docker containers on one board.
- Postgres or MariaDB is in your stack.
- You want Plex, Jellyfin, or any transcoding path.
- You want NVMe storage.
- You run Immich, Photoprism, Frigate, or any ML-adjacent service.
- You want headroom for the next three years without re-platforming.
Get the Pi 4 8GB if...
- Your homelab is Pi-hole, AdGuard, Home Assistant, or a small Samba/NFS share.
- You want the cheapest well-supported always-on node.
- Power draw matters (solar-backed, off-grid, RV/boat, high electricity cost).
- You already own Pi 4 accessories (cases, HATs, PoE) and want compatibility.
- You are building a Kubernetes/K3s learning cluster of 3-5 nodes where cost per node dominates.
Get the Pi 5 2GB if...
- You need a single dedicated service (Pi-hole only, HA only, MQTT broker only) and want the newer platform for future migration.
- Do not run a container stack on 2GB — it will swap, wear the SD card, and disappoint.
Get a Pi Zero W instead if...
- You want a single sub-1W sensor gateway, MQTT bridge, or button endpoint. The Raspberry Pi Zero W Basic Starter Kit is the right shape for those tasks.
Recommended pick by workload and budget
- Pi-hole + Unbound + Home Assistant + Samba share, <$120 all-in: Pi 4 8GB + SATA SSD via USB 3.0. This is the workhorse configuration and still the correct answer in 2026.
- Docker stack (Traefik + Vaultwarden + Immich + Nextcloud + Uptime Kuma + monitoring), $150-200 all-in: Pi 5 8GB + NVMe HAT + PoE HAT if wired.
- Plex/Jellyfin with any transcode, $180+: Pi 5 8GB minimum, NVMe HAT strongly recommended.
- K3s learning cluster, 3-5 nodes: mix Pi 4 8GB workers with one Pi 5 control-plane node — the price-per-node math favors keeping most nodes on the Pi 4.
- Sensor gateway or single MQTT relay: Pi Zero W with a good SD card. Do not use a Pi 4 or Pi 5 for a job a Zero can do.
- All-in-one "just give me the fastest single board" homelab: Pi 5 16GB with NVMe HAT and active cooler, budget ~$250 built.
Bottom line
If you are choosing today and your homelab plan is ambitious — Docker stack, media server, self-hosted photos, database-backed apps — buy the Pi 5. The perf jump is real, the I/O jump is bigger than the perf jump, and PCIe NVMe changes what "reliable storage on a Pi" means. Per the Pi 5 product page, it is the first Pi where "single-board homelab" stops being a compromise.
If your plan is modest — DNS, home automation, a file share, a couple of containers — the Raspberry Pi 4 Computer Model B 8GB is still the right answer. It is cheaper, cooler-running, more forgiving of enclosure choice, and every piece of software you want has been running on it since 2019. Pair it with a Crucial BX500 1TB SATA SSD to get off SD cards and it will run for years.
And for anything a single microcontroller-class board can do, a Raspberry Pi Zero W Basic Starter Kit is cheaper, lower-power, and correct. Match the board to the workload.
Related guides
- Best Raspberry Pi Accessories for Homelab
- SATA SSD vs NVMe for Raspberry Pi Storage
- Docker on Raspberry Pi: Container Density Guide
- Home Assistant Hardware Guide 2026
- Pi-hole Deployment Guide
Citations and sources
- Raspberry Pi 5 product page and datasheet — https://www.raspberrypi.com/products/raspberry-pi-5/
- Raspberry Pi 4 Model B product page — https://www.raspberrypi.com/products/raspberry-pi-4-model-b/
- Raspberry Pi M.2 HAT+ product page — https://www.raspberrypi.com/products/m2-hat-plus/
- Raspberry Pi Active Cooler product page — https://www.raspberrypi.com/products/active-cooler/
- Phoronix Raspberry Pi 5 review and benchmarks — https://www.phoronix.com/review/raspberry-pi-5
- Phoronix hardware benchmark index — https://www.phoronix.com/
- Jeff Geerling's Raspberry Pi 5 review — https://www.jeffgeerling.com/blog/2023/raspberry-pi-5-review
- Jeff Geerling homelab and Pi coverage — https://www.jeffgeerling.com/
- Pi-hole project on GitHub — https://github.com/pi-hole/pi-hole
- llama.cpp project on GitHub — https://github.com/ggerganov/llama.cpp
- Docker official documentation — https://www.docker.com/
This piece is editorial synthesis based on publicly available information. No independent first-party benchmarking is reported.
