Why This Decision Matters More on a NAS
Picking drives for a Synology box isn’t like picking a boot drive for a PC. A NAS runs 24/7, often for years without a reboot, and the drives inside it are usually doing something in the background even when nobody’s accessing files: scrubbing, indexing, running Btrfs checksums, serving Plex thumbnails. That changes the calculus. The question isn’t just “SSD or HDD,” it’s “what is this bay actually going to be asked to do.”
Most people land on one of three setups: all-HDD for bulk storage, all-SSD for speed and silence, or a hybrid where SSDs handle cache or hot data and HDDs hold everything else. All three are legitimate. Here’s how to pick.
Cost Per TB Is Still Lopsided
As of now, a 4TB NAS-rated hard drive runs somewhere around $80-110, while a 4TB SATA SSD is closer to $200-280. At 8TB and above the gap gets worse for SSDs because large-capacity flash is still a premium product. If you’re building a media server or backup target with 20TB+ of capacity, going all-SSD can easily cost three to four times as much as HDDs for the same space.
This is the single biggest reason most Synology builds still default to spinning disks. If you’re storing security camera footage, photo backups, or a movie library, you’re paying for capacity, not speed, and HDDs win on that metric by a wide margin. Browsing NAS hard drives will make the price-per-terabyte gap obvious within a few minutes.
Where SSDs Actually Change Things
Raw sequential throughput on a Synology is usually capped by the network connection, not the drive. On a 1GbE port you’re ceilinged around 110-125 MB/s, which any decent HDD can saturate on its own. Even on 2.5GbE models that’s roughly 280 MB/s, still within reach of two HDDs in RAID. So if your only use case is dumping files over the network and watching movies, SSDs won’t feel faster day to day.
Where SSDs matter is latency and random I/O: things like running Synology’s Active Backup for Business against many small files, hosting a database or Docker containers, or using the NAS as iSCSI storage for a hypervisor. HDDs have seek times in the 8-15ms range because a physical arm has to move; SSDs respond in under a millisecond. If your NAS is doing anything transactional rather than just storing files, that difference is very noticeable, especially with many simultaneous users.
The Hybrid Option: SSD Cache
Many Synology models support using one or two SSDs as a read/write cache layer in front of an HDD volume. This is the pragmatic middle ground: you keep cheap bulk HDD storage but get SSD-like response times for frequently accessed files, because the cache learns what’s “hot” and serves it from flash.
The catch is that cache SSDs need to be endurance-rated, not whatever cheap drive is on sale. Synology’s compatibility list matters here, and consumer SSDs without decent TBW (terabytes written) ratings will wear out faster under constant cache writes than they would in a normal desktop. For a two-bay cache setup, look at SSDs rated for NAS caching rather than generic budget drives.
Failure Modes Are Different, Not Better or Worse
HDDs fail mechanically: bearings wear, read heads degrade, and you often get warning signs through SMART attributes like reallocated sector counts before a full failure. SSDs fail more abruptly, usually from controller failure or NAND wearing past its write endurance, and sometimes with less warning. Neither is inherently more reliable in a NAS context; both need RAID and both need backups, because RAID protects against a single drive failing, not against the NAS being stolen, flooded, or hit by ransomware.
One real difference: HDDs are more sensitive to vibration and heat in multi-bay enclosures, which is why NAS-specific HDD lines exist with firmware tuned for that environment. Desktop HDDs dropped into a loud 8-bay chassis can see higher error rates over time. SSDs don’t have this problem since there’s nothing spinning.
Side-by-Side
| Factor | HDD | SSD |
|---|---|---|
| Cost per TB | Low ($20-30/TB) | High ($40-70/TB) |
| Sequential speed | Fine, network-limited anyway | Overkill for file serving |
| Random I/O / latency | Weak, 8-15ms seek times | Strong, sub-1ms |
| Noise and vibration | Audible, matters in multi-bay units | Silent |
| Best use case | Bulk storage, backups, media | Databases, VMs, cache, Docker |
| Failure warning | Often gradual, SMART-visible | Can be sudden |
What to Actually Buy
If your Synology is mainly a backup target, media server, or photo archive, buy HDDs and don’t overthink it. Two or three NAS-rated drives in SHR or RAID 1/5 will outlast most people’s upgrade cycle, and the money saved versus SSDs is better spent on an extra drive for redundancy or an off-site backup plan.
If you’re running VMs, databases, or heavy multi-user Docker workloads, SSDs are worth the premium, either as the whole pool on a model with enough bays, or as a cache tier in front of HDDs. For most home and small-office setups, a two-bay HDD volume plus a modest SSD cache hits the best balance of cost and responsiveness without needing to replace every drive in the chassis.
Whichever route you take, buy drives explicitly validated for your Synology model. The compatibility list isn’t just marketing; firmware mismatches on unsupported drives have caused real dropouts and degraded RAID arrays for people who assumed any SATA drive would do.
