SSD vs HDD
For bulk NAS storage in 2026, spinning HDDs are still the right call. They cost a fraction per terabyte, ship in much larger capacities per bay, and a single 7200 RPM drive already saturates a 1GbE link. SSDs win when you need random IOPS, silence, low power, or an all-flash box for VMs and databases. Most homelabs end up doing both: HDDs for the data pool, a small SSD or two for cache and app data. Here is where each one actually belongs.
Updated 2026-06-18 · by Jonathan Caruso
Side by side
| SSD | HDD | |
|---|---|---|
| Cost per TB | ~$50-90/TB (SATA, large) | ~$15-22/TB (NAS-rated) |
| Max capacity per drive | 8TB consumer SATA, more in enterprise U.2 | Up to 24-30TB (IronWolf Pro, Exos) |
| Sequential speed | ~550 MB/s (SATA), 3-7 GB/s (NVMe) | ~150-260 MB/s |
| Random IOPS | Tens of thousands | ~80-200 |
| Endurance limit | Finite writes (TBW rating) | Mechanical wear, rated by workload/year |
| Power (active) | ~2-4W | ~5-9W |
| Noise / vibration | Silent | Audible spin and seek, vibration |
| Best role | VMs, databases, cache, all-flash | Media, backups, archive, bulk pool |
Cost per terabyte is the whole argument
This is why NAS boxes are still full of spinning disks. A NAS-rated HDD like a WD Red Plus or Seagate IronWolf runs roughly $15 to $22 per terabyte as of 2026, and the price barely moves as you go up in capacity. A large SATA SSD is in the neighborhood of $50 to $90 per terabyte, and consumer SATA tops out around 8TB per drive. Fill a four-bay NAS with 12TB HDDs and you have 48TB raw for a few hundred dollars. Do the same with SSDs and you are spending multiples of that for less capacity.
For a media server, a backup target, or a general file dump, that math is not close. You want the cheapest reliable terabytes you can get, and that is a CMR spinning disk. The SSD premium only earns its keep when capacity is small and the workload actually needs flash speed.
If you are sizing a pool and want to see how raw capacity turns into usable space after parity, run the numbers in the RAID and ZFS calculator before you buy drives.
Speed: the network usually decides it
A single 7200 RPM NAS HDD does roughly 150 to 260 MB/s sequential. A 1 gigabit network link tops out around 113 MB/s. So on plain 1GbE, a single spinning disk already saturates the wire, and an SSD gives you nothing for large file transfers. This is the detail people miss: the SSD is faster than the HDD, but the network is slower than both.
The picture changes when you move to 2.5GbE or 10GbE, or when the workload is random rather than sequential. HDDs are terrible at random I/O, somewhere around 80 to 200 IOPS because the head physically seeks. An SSD does tens of thousands. So if the NAS is serving VM disks, a database, lots of small files, or many simultaneous users hitting different files, flash is dramatically faster and HDDs feel like molasses. For one person streaming movies over gigabit, the HDD is fine.
Endurance and reliability work differently
SSDs wear out by writes. Every flash cell has a finite program/erase count, and the drive's TBW (terabytes written) rating tells you how much the warranty covers. A NAS that is mostly reads, like a media library, will never come close to exhausting a modern SSD. A write-heavy role like a busy database or a ZFS write-log can chew through cheap consumer flash, which is why endurance and power-loss protection matter for those jobs.
HDDs do not wear from writes the same way; they fail mechanically. NAS-rated drives are built for 24/7 spin and rated for a workload (commonly 180 to 300 TB/year) and around 1 to 1.2 million hours MTBF. SSDs have no moving parts and higher rated MTBF, but when flash fails it tends to fail suddenly and completely, whereas a dying HDD often gives you SMART warnings and reallocated sectors first.
Either way, RAID is not a backup and neither drive type changes that. Backblaze's published drive stats are the best public reliability data, and the headline is that good drives from any class are reliable enough that your backup strategy matters more than the SSD-versus-HDD failure rate. Pair the pool with real backups using something like Restic or Borg.
The trap: SMR HDDs and the wrong SSDs
Not every drive is NAS-safe, and the failure modes are different for each. On the HDD side, avoid SMR (shingled) drives in any RAID or ZFS pool. SMR rewrites overlapping tracks and grinds to a halt during a resilver, which can turn a routine rebuild into a multi-day ordeal or a failed one. Stick to CMR drives explicitly sold for NAS use: WD Red Plus and Red Pro (not the plain blue-label Red, some of which are SMR), Seagate IronWolf and IronWolf Pro, or Toshiba N300.
On the SSD side, the cheapest DRAM-less QLC drives have low endurance and poor sustained write performance once their cache fills, which shows up badly in a NAS. If you are using SSDs for a ZFS SLOG or a write cache, you specifically want power-loss protection (PLP), which is an enterprise feature, not a consumer one. For a straight all-flash data pool, a decent SATA SSD or a NAS-branded model like the Seagate IronWolf SSD or WD Red SA500 is the safer pick than the bargain-bin drive.
What most homelabs actually build
The common and correct answer is both, in different roles. Spinning disks form the bulk data pool: media, file shares, backups, the stuff measured in tens of terabytes. One or two SSDs handle the things that benefit from speed: the boot/OS volume, the apps or Docker volumes, VM disks, and cache. On Synology that is SSD read/write cache; on TrueNAS it is L2ARC, SLOG, or a metadata special vdev. NVMe slots on newer NAS boards make this easy without giving up drive bays.
All-flash NAS builds are real and getting more common as SSD prices drift down, but they make sense for specific reasons: a silent box in a living space, a low-power always-on unit, or a workload that is genuinely IOPS-bound like running VMs off the NAS. For most people storing media and backups, a hybrid build gives you the speed where it matters and the cheap capacity everywhere else. If you are still choosing the box and OS, see TrueNAS vs Unraid and the best NAS operating system roundup.
Where SSD wins
- Tens of thousands of IOPS; huge advantage for random, multi-user, and VM workloads.
- Silent, low power, no vibration, and higher rated MTBF.
- Fast enough to use 2.5GbE/10GbE that an HDD pool cannot keep up with.
Where HDD wins
- Roughly a quarter the cost per terabyte of large SSDs.
- Largest capacities per drive (24TB+) for dense bulk pools.
- A single drive already saturates a 1GbE link for sequential transfers.
Which to pick, by situation
| Your situation | Pick | Why |
|---|---|---|
| Media server and backups over 1GbE | HDD | A single NAS HDD saturates gigabit; cheap terabytes win. |
| Running VMs or a database off the NAS | SSD | Random IOPS is where HDDs collapse and flash shines. |
| Silent, low-power NAS in a living space | SSD | No spin noise, no vibration, lower watts. |
| Maximum capacity per bay on a budget | HDD | 24TB+ CMR drives at a fraction of SSD cost per TB. |
| 10GbE network, lots of small-file or multi-user load | SSD | HDD random performance bottlenecks before the network does. |
The verdict
For the bulk of a NAS, buy NAS-rated CMR HDDs. They are roughly four times cheaper per terabyte, come in larger capacities, and a single drive already saturates a gigabit link, so for media, file shares, and backups an SSD buys you nothing you can use. Add SSDs for the jobs that are actually IOPS-bound: VM disks, databases, app and Docker volumes, and read/write cache. Reserve all-flash for a deliberate reason like silence, low power, or a VM-heavy box on a fast network. The right homelab answer is almost always a hybrid pool, and you should size it in the RAID and ZFS calculator before buying.
Choose SSD if the workload needs random IOPS, silence, or low power: VMs, databases, cache, or a deliberate all-flash build.
Choose HDD if you are storing bulk data like media and backups and want the cheapest reliable capacity per terabyte.
Official links
FAQ
Is it worth putting an SSD in a NAS?
It depends on the job. For bulk storage like media and backups, no, the SSD premium buys you nothing a 1GbE network can use. For VM disks, databases, app data, or as a read/write cache, yes, the random-I/O speedup is large and very noticeable.
Why doesn't a NAS use SSDs?
Mostly cost and capacity. NAS HDDs run roughly $15-22 per terabyte versus $50-90 for large SATA SSDs, and HDDs come in much bigger per-drive capacities. For storing tens of terabytes of media and backups, that price gap is the whole reason spinning disks still dominate NAS bays.
Why does a NAS still use HDDs in 2026?
Because most NAS workloads are sequential and capacity-bound, not IOPS-bound. A single HDD saturates gigabit Ethernet, and you can buy four times the capacity per dollar. SSD prices keep falling, so all-flash is growing, but for bulk storage HDDs are still the economical choice.
How long will an SSD last in a NAS?
For a read-heavy NAS, well past a decade; you will replace it for capacity before you exhaust its write endurance. The wear comes from writes, tracked by the TBW rating. A write-heavy role like a busy database or ZFS write-log on a cheap consumer drive can wear flash much faster, which is why those jobs want high-endurance drives with power-loss protection.
Can any SSD be used in a NAS?
Physically almost any SATA or NVMe SSD fits, but not every one is a good idea. Avoid the cheapest DRAM-less QLC drives for sustained writes, and for a ZFS SLOG or write cache you specifically want power-loss protection. NAS-branded drives like the WD Red SA500 or Seagate IronWolf SSD are tuned for 24/7 use.
Are SSDs reliable for a NAS?
Yes. SSDs have no moving parts and high rated MTBF, and in large fleets they fail at rates comparable to or better than HDDs. The difference is the failure mode: SSDs tend to fail suddenly while HDDs often give SMART warnings first. Reliability of either is no substitute for backups.
What hard drive is best for a NAS?
A CMR (not SMR) drive sold for NAS use: WD Red Plus or Red Pro, Seagate IronWolf or IronWolf Pro, or Toshiba N300. Avoid SMR drives in any RAID or ZFS pool because they stall badly during a rebuild. Match capacity to your pool plan and buy from more than one batch if you can.
Should I build an all-flash NAS?
Build all-flash if you want a silent, low-power box, or if the workload is genuinely IOPS-bound like running VMs off the NAS. For media and backups it is hard to justify the cost per terabyte. The middle path most people pick is a hybrid: HDDs for the data pool, SSDs for cache, apps, and VM storage.