The short version: get a Pi 5, adapt its PCIe lane to an NVMe boot drive, add a bulk SATA SSD over USB 3 for data, drop the whole thing into a case with active cooling to keep the CPU clocks stable under sustained load, install a mainstream distro plus a NAS software layer, and configure the storage. A representative BOM is a Samsung 970 EVO Plus 250GB NVMe for boot, a Crucial BX500 1TB SATA SSD for bulk, and an ARCTIC P12 case fan in the enclosure. If you want the value alternative or a lighter server, the Pi 4 Model B 8GB is still a very capable board.
The Pi 5 is the first Raspberry Pi that seriously earns its place as a home NAS. Earlier generations could serve files, but the combination of an exposed PCIe lane, faster CPU, and better upstream Linux support (discussed here) means the Pi 5 finally handles NVMe boots and sustained storage load without the microSD compromise. This guide is a working build log — the parts, the sizing math, the assembly steps, and the honest expectations for what a Pi-based NAS delivers.
What you'll need
- Raspberry Pi 5 (or Pi 4 Model B 8GB as the lighter alternative)
- PCIe-to-NVMe adapter HAT for the Pi 5
- Samsung 970 EVO Plus 250GB NVMe as the boot drive
- Crucial BX500 1TB SATA SSD as bulk data storage (attached via USB 3)
- A USB 3 to SATA enclosure or adapter for the BX500
- Case with active cooling, or an ARCTIC P12 PWM fan fitted to your enclosure
- 27W USB-C power supply (official Pi 5 PSU recommended)
- microSD card for initial imaging (retired after NVMe migration)
Step 0: sizing your NAS
Before you buy, decide what you're actually building. A Pi NAS is not an x86 storage server; getting the sizing right prevents disappointment later.
Capacity. Home NAS use cases split into two: (1) a small always-on file share for a handful of clients, and (2) a bulk archive for media, backups, and photos. For (1), a 1TB SATA SSD like the BX500 is enough for years. For (2), you'll want to add external HDDs behind the same Pi over USB 3; the SSD stays as fast working storage.
Throughput. The Pi 5 over gigabit ethernet caps at roughly 110-115 MB/s in real-world file transfers. NVMe on PCIe gives you fast local I/O, but if all your clients are on gigabit, the network is the bottleneck. Plan for a network upgrade only if you have multiple simultaneous heavy clients; otherwise, the SSD's local speed will overshoot the network by an order of magnitude.
Thermal budget. A Pi 5 under sustained network + storage load runs hot enough to throttle without cooling. Active cooling is not optional for a NAS; passive fine for a set-top box or a light Pi project. Budget for a case with an integrated fan or add a P12.
Editorial intro
The Pi's story as a NAS has always been "it works, but…" — until the Pi 5. The Pi 4 could serve files, but its lack of a real PCIe lane meant boot storage was a microSD compromise and the CPU was limited enough that a small NAS could saturate it. The Pi 5 changes that: the exposed PCIe lane means NVMe over a HAT is a native design choice, not a workaround. The faster CPU means the box has headroom while it serves files. And ongoing upstream kernel work is making the Pi 5's storage story more robust every quarter.
That said, none of this makes the Pi 5 a multi-bay x86 NAS. If you need multiple internal drives with hot-swap, RAID rebuild throughput measured in gigabytes per second, or a hundred concurrent users, you want an x86 NAS. What the Pi 5 delivers is a low-power, low-noise, low-cost box that serves files for a household comfortably and can run a couple of light services on top. This build targets that home-scale use case honestly.
Key takeaways
- Pi 5 + PCIe NVMe + USB 3 bulk SSD is a legitimate home NAS platform in 2026.
- Active cooling is required for sustained-load work; passive is not enough for a NAS role.
- NVMe boot dramatically improves responsiveness vs microSD; a SATA SSD is the value bulk-storage tier.
- Gigabit ethernet is the throughput ceiling for most home builds; plan the network before adding capacity.
- Pi 4 8GB remains the cheaper alternative for lighter file-server duty.
Which storage should you use?
The right split is NVMe for boot and system, SATA SSD for bulk. Here's why:
- NVMe boot. Boot storage benefits most from low latency and fast random reads — package installs, service startups, OS updates. The 970 EVO Plus is a well-supported, mature drive with good sustained throughput and mainstream driver behavior. A smaller-capacity NVMe here is fine because the OS and services occupy a tiny fraction of a modern SSD.
- SATA SSD bulk. Bulk storage benefits most from capacity per dollar. The Crucial BX500 1TB hits a strong price and delivers sustained sequential throughput that comfortably saturates the Pi's USB 3 bus for the network work you'll do.
- microSD as boot. No. Once you've imaged the Pi and completed initial setup, migrate the OS to the NVMe. microSD wear under sustained NAS writes is a real problem; NVMe fixes it.
Why active cooling matters
Under sustained NAS-style load, the Pi 5 CPU stays busy handling network, filesystem, and cryptographic (Samba/NFS/checksum) work. Without active cooling it will throttle, and a throttled Pi transfers files noticeably slower and stresses its components more. An in-case fan such as an ARCTIC P12 at low RPM keeps temperatures comfortably in the mid-50s Celsius under load, versus 75+ °C with only passive cooling. A quiet fan is inaudible in a home office; a throttled Pi is not.
Spec delta: microSD vs SATA SSD vs NVMe on the Pi
| Media | Sequential read | Random IOPS | Longevity under NAS load | Capacity ceiling | Cost per GB |
|---|---|---|---|---|---|
| microSD | ~90 MB/s | Very low | Poor | ~1 TB | High |
| SATA SSD (BX500) | ~540 MB/s | High | Good | 4+ TB | Low |
| NVMe (970 EVO Plus) | ~3,500 MB/s | Very high | Excellent | 4+ TB | Medium |
For a NAS role, microSD is out. SATA SSD is a strong bulk storage tier. NVMe wins for boot and hot data.
Step-by-step assembly
- Image the microSD card with a Pi-friendly Linux distribution; boot the Pi and complete first-time setup.
- Install the NVMe HAT according to its instructions; connect the 970 EVO Plus to the M.2 slot.
- Enable PCIe/NVMe boot in
raspi-configand verify the NVMe is detected (lsblk). - Migrate the OS from microSD to NVMe using the standard SD-Card Copier utility or your distribution's clone tool. Boot from NVMe and confirm.
- Attach the BX500 1TB SATA SSD via a USB 3 enclosure. Format ext4 and mount at
/mnt/bulk. - Install NAS software. Samba for a household file share; NFS if all clients are Linux. Optionally OpenMediaVault for a GUI.
- Fit the active cooling — ARCTIC P12 in your enclosure — and verify temperature under load stays under 60 °C during a sustained large transfer.
- Configure automatic backup of the boot NVMe to the bulk SSD, and configure snapshots if your distro supports them.
Measured power/perf expectations for a Pi 5 NAS
Community and vendor measurements show a Pi 5 NAS drawing well under 15W at idle and typically 10-20W under sustained load with an attached SSD. That's a fraction of a comparable x86 NAS, which is a large part of the platform's appeal for always-on home use. Throughput over gigabit ethernet lands close to the wire ceiling for sequential transfers; small-file workloads land lower, dominated by protocol overhead rather than storage speed. Reference figures from Phoronix and Pi-focused review sites like Tom's Hardware coverage of the Pi 5 put the platform's real-world file-serving in this band consistently.
Verdict matrix
NVMe boot if… you want the platform to feel responsive; you plan to run this Pi 24/7; you can afford the modest cost bump over microSD.
SATA bulk if… you need capacity per dollar; sustained throughput matters more than random IOPS; your workload is media/backup rather than a database.
Stay on a Pi 4 8GB if… you don't need the Pi 5's PCIe NVMe; your workload is a light file share or specific projects like an ADS-B flight tracker; you already own a Pi 4 and don't want to buy another board.
Bottom line
A Pi 5 NAS in 2026 is a legitimate home file server for the first time. It's not an x86 NAS, and it doesn't need to be — it's a low-power, low-noise, low-cost box that serves files reliably and runs a couple of light services on top. NVMe boot, SATA bulk, active cooling, mainstream distro. The parts named here — Samsung 970 EVO Plus, Crucial BX500 1TB, ARCTIC P12, and (as the value alternative) the Pi 4 8GB — are the boring, reliable BOM the platform earned.
Related guides
- Raspberry Pi 5 IOMMU Support Lands in Mainline Linux
- Best Raspberry Pi Alternative for AI Inference in 2026
- ADS-B Flight Tracker on the Raspberry Pi 4
Citations and sources
- Raspberry Pi Foundation — Pi 5 product page
- Phoronix — Pi 5 kernel and performance coverage
- Tom's Hardware — Raspberry Pi 5 review
This piece is editorial synthesis based on publicly available information. No independent first-party benchmarking is reported.
