What You’re Really Paying For
SSD vs HDD space isn’t just a price-per-gigabyte question, though that’s where most people start. A 4TB hard drive and a 4TB SSD store the same amount of data, but they get there through completely different physics, and that affects more than speed. It affects how you should actually divide storage across drives, what happens when a drive starts dying, and whether that “4TB” number on the box means the same thing in practice.
Right now, mechanical hard drives run about $15-20 per terabyte at the 4TB-8TB range. SATA SSDs land around $35-45 per terabyte. NVMe SSDs vary more, but a decent 1TB-2TB drive is usually $50-90 per terabyte depending on controller and NAND quality. That gap has narrowed over the past few years, but it hasn’t closed, and for bulk storage it probably won’t anytime soon.
Price Per GB, in Practice
The sticker price per gigabyte matters less than what you’re storing. A 1TB game library doesn’t care whether it’s sitting on an SSD or HDD once it’s installed and sitting idle, but load times and texture streaming do. A 4TB archive of old project files, backups, and media you rarely touch doesn’t care about speed at all. That’s the actual decision point: speed-sensitive data goes on flash, cold storage goes on spinning platters, and most people benefit from having both rather than picking one.
| Use case | Better fit | Why |
|---|---|---|
| OS and active programs | SSD | Boot and load times, no mechanical latency |
| Current game library | SSD (NVMe ideally) | Faster level loads, less stutter on texture streaming |
| Photo/video archive | HDD | Cheap per GB, fine for sequential read/write |
| Backup target | HDD | Low cost justifies redundant copies |
| Video editing scratch disk | SSD (NVMe) | Sustained throughput matters for 4K+ footage |
| Long-term cold storage (unplugged) | HDD, with caveats | Cheaper, but needs power-on time periodically |
Capacity Ceilings and Where They Bite
HDDs still win outright at the high end. Consumer SSDs top out around 8TB for most people’s budgets, with 2TB and 4TB being the realistic sweet spot. Hard drives go up to 20TB+ in NAS-oriented models, and the price scaling stays close to linear, which SSDs don’t do as cleanly past 2TB. If you need 16TB of storage for a media server or large backup set, doing that in SSDs is possible but financially silly for most home setups. This is the clearest case where the cheaper option isn’t a compromise, it’s just correct. For that kind of bulk capacity, browsing internal hard drives in the 4TB-8TB range will get you further per dollar than anything flash-based.
On the other end, if your whole system only needs 500GB-2TB and you want it fast, that’s squarely SSD territory, and NVMe drives have gotten cheap enough that there’s little reason to default to SATA SSDs anymore unless you’re filling an older board without M.2 slots. Checking a current NVMe SSD listing will usually show prices close to SATA SSDs at the same capacity, which makes SATA SSDs mostly a bridge technology for older hardware at this point.
How Failure Changes With Density
Higher capacity drives, SSD or HDD, concentrate more data on fewer physical units, which means a failure costs you more. A dead 1TB drive loses 1TB. A dead 8TB drive loses 8TB. This isn’t a reason to avoid big drives, it’s a reason to not treat a single big drive as your only copy of anything you care about.
HDDs fail mechanically, often with warning signs, clicking, slow access, SMART errors creeping up. SSDs tend to fail more abruptly, sometimes going from fine to completely unreadable with no warning, because there’s no spinning part to physically audibly degrade. Both have write endurance limits, but for typical desktop use, you’ll replace an SSD for capacity reasons long before you hit its write limit. The real-world failure modes you should plan around are drive controller death and NAND degradation on SSDs, and bearing wear or head crashes on HDDs. Neither is rare enough to skip backups.
How to Actually Split Your Storage
If you’re building or upgrading a PC with a budget for mixed storage, a workable split for most people is a 1TB-2TB NVMe SSD for OS, applications, and current games, plus a 4TB+ HDD for everything else: finished projects, media libraries, backups, old game installs you’re not actively playing. This gets you fast everyday performance without paying SSD prices for bulk capacity you don’t need fast access to.
If your case or budget only allows one drive, go SSD unless your capacity need is genuinely large (8TB+) and your workload is mostly sequential, like a media server. A single large HDD as your only drive is fine for a dedicated backup or storage box, but as a primary OS drive it will be the slowest part of an otherwise modern system, and you’ll feel it every time you open an application or boot up.
Where people overspend is buying a large SSD, 4TB or more, purely to avoid having two drives. It works, but you’re paying roughly double or triple the per-GB cost for speed that your archive data will never use. Two drives in different roles isn’t more complicated to manage than one, Windows and most NAS software handle multi-drive setups without any special configuration, and the cost savings are real enough to matter.
