Capacity shopping for storage used to be simple: more gigabytes per dollar, buy the biggest drive you could afford. SSDs changed that math. Flash memory costs more per terabyte than spinning platters, and that gap doesn’t disappear just because SSDs are faster and more reliable. If you’re trying to figure out how much capacity you actually need and whether to spend the premium on flash, here’s what the numbers actually look like.
Price per terabyte, realistically
As of this writing, a 2TB SATA or NVMe SSD typically runs somewhere in the $90-130 range, which works out to roughly $45-65 per terabyte. A 2TB 7200RPM hard drive costs $45-55, or about $22-28 per terabyte. That’s a real gap, not a rounding error. At 4TB the spread widens in absolute dollars even though the per-terabyte ratio narrows slightly, since 4TB SSDs still carry a premium for the larger NAND packages and controllers that handle them.
Once you get past 8TB, the comparison stops being close. HDDs scale up to 16TB, 20TB, even 24TB in consumer and NAS-oriented drives, with cost per terabyte often dropping below $20. SSDs technically exist in those capacities but they’re enterprise-priced and not something you’ll find on a typical upgrade budget. If you need to store 12TB of video footage or a surveillance archive, you’re buying hard drives, full stop.
Where capacity actually matters
The right capacity depends entirely on what you’re storing, not some universal rule of thumb.
For a Windows boot drive running an OS plus a handful of applications, 500GB is tight but workable, 1TB is comfortable. Game installs are the wildcard here — modern AAA titles routinely eat 60-100GB each, so if you’re building a gaming PC, a 2TB NVMe SSD is the sweet spot for most people rather than something you’ll regret in six months.
For bulk storage — media libraries, backups, archived projects — the calculation flips. You’re not paying for speed you’ll notice, since watching a movie or copying a backup file doesn’t benefit from NVMe-class throughput. This is where a 8TB hard drive makes far more financial sense than filling the same budget with flash.
Side by side at common capacities
| Capacity | SSD (typical street price) | HDD (typical street price) | Price gap |
|---|---|---|---|
| 1TB | $55-75 | $40-50 | ~$20-25 |
| 2TB | $90-130 | $50-60 | ~$50-70 |
| 4TB | $220-300 | $80-100 | ~$150-200 |
| 8TB | $450-600 (uncommon in consumer SATA/NVMe) | $130-160 | ~$350-450 |
| 16TB+ | Rare, enterprise pricing | $220-280 | Not comparable |
Note how the gap isn’t linear. At 1TB it’s almost an impulse-buy difference. At 4TB and above, it’s the difference between an upgrade you do this weekend and one you have to budget for.
Capacity on the label isn’t capacity on disk
Both drive types report less usable space than the number on the box, for the same reason: manufacturers use decimal gigabytes (1,000,000,000 bytes) while your OS counts in binary gibibytes (1,073,741,824 bytes). A “2TB” drive shows up as roughly 1.82TB in Windows. This affects HDDs and SSDs equally, so it’s not a factor in choosing between them, but it does mean you should budget about 7% less usable space than the sticker claims when deciding if a given size will actually fit your library.
SSDs lose a bit more to overprovisioning, where the controller reserves a slice of NAND for wear leveling and bad block management, invisible to you but worth knowing exists if a 1TB SSD feels like it’s showing less free space than a 1TB HDD would.
What happens when a large drive fails
Capacity decisions aren’t just about price, they’re about blast radius when something goes wrong. A failed 20TB HDD full of unreplaceable family photos is a much worse day than a failed 500GB SSD that only held a game library you can redownload. The practical rule: the more irreplaceable data you’re storing, the more that capacity needs a backup plan, not just a bigger drive. RAID is not backup. A second physical drive, ideally offsite or cloud-synced, is.
HDDs tend to fail with some warning — unusual noises, SMART errors creeping up, slow degradation. SSDs more often fail suddenly and completely, going from fine to undetected-by-BIOS with little warning. Neither failure mode cares how much capacity you crammed onto the drive, but a bigger drive means more data at risk per failure event, which is an argument for spreading large libraries across two mid-sized drives rather than one giant one if the data genuinely matters.
The actual decision
If you’re specing a new PC build or upgrade, buy SSD capacity for anything the OS or applications touch, sized to what you’ll actually install, not what you might theoretically need. Buy HDD capacity for anything measured in hundreds of gigabytes of static files — media, archives, backups. Mixing both in one system, a smaller fast SSD plus a larger slow HDD, almost always beats trying to find a single drive and capacity that does both jobs well. The HDD premium at small capacities is small enough that buying “a bit more than you need” costs little. The SSD premium at large capacities is steep enough that doing the same there is just paying for gigabytes you’ll never notice using.
