Most desktop builds end up with both: an SSD for speed-sensitive work and a hard drive for bulk storage. The question isn’t which is “better” — it’s which jobs punish a slow drive and which don’t notice. Here’s how to split it.
What goes on the SSD
Windows (or any OS). This is non-negotiable in 2025. Windows on a hard drive takes a minute or more to boot, sits pinned at 100% disk usage in Task Manager during updates, and makes every click feel sticky. On even a cheap SSD, boot is under 20 seconds and the system stays responsive while it churns in the background.
Applications. Browsers, Office, launchers, chat apps — anything you open repeatedly benefits from an SSD’s near-instant access times. The raw spec difference is huge: NVMe drives pull 3,500–7,000 MB/s sequential reads versus 150–250 MB/s on a hard drive, but the bigger deal is random access latency, where SSDs are roughly 100x faster.
Games you’re actively playing. Modern games stream assets continuously, and some titles now list an SSD as a hard requirement — Starfield won’t even install on a HDD officially. Expect level loads of 10–20 seconds on SSD versus 60+ on a hard drive in asset-heavy games, plus less texture pop-in. Older or competitive shooters see smaller gains, but map loads still improve. A 1TB NVMe drive runs roughly $60–80 and holds your OS plus a healthy game rotation.
Active project files. Video editing timelines and scratch disks, photo libraries you’re culling (thumbnail generation hammers random reads), VMs, and code compilation all scale directly with drive speed.
What goes on the HDD
Media library. This is where hard drives still make complete sense. Even a 4K Blu-ray remux peaks under 20 MB/s — a tenth of what a 7200rpm drive delivers sequentially. Movies, music, and recorded TV see zero benefit from flash.
Backups and archives. Photo dumps, old projects, disk images. Sequential writes are a hard drive’s strength, and a 4TB hard drive costs around $80 — roughly $20/TB versus $60+ per TB on NVMe.
Back-catalog games. Be honest here: games on a HDD are playable. You’ll eat longer load times and occasional stutter or pop-in in stream-heavy titles, but for turn-based games, indies, and anything pre-2018, it’s fine. Steam lets you create library folders on each drive and move installs between them — park finished games on the HDD instead of deleting.
Downloads and capture. OBS recordings and torrents are large sequential writes, which hard drives handle easily at any realistic bitrate.
One caveat: below 2TB, hard drives barely undercut SATA SSDs on price. The HDD only earns its slot at 4TB and up.
Quick reference
| Data type | Put it on | Why |
|---|---|---|
| Operating system | SSD | Boot time and constant background I/O |
| Applications | SSD | Launch speed, update churn |
| Games in rotation | SSD | Load times, asset streaming; some require it |
| Back-catalog games | HDD acceptable | Longer loads, still playable |
| Active photo/video projects | SSD | Random reads, scrubbing, thumbnails |
| Finished media library | HDD | Playback needs <20 MB/s |
| Backups | HDD | Cheap capacity, sequential writes |
| Cold archives (unpowered storage) | HDD | SSDs can lose data sitting unplugged |
How each drive fails
Failure behavior should influence placement more than people think.
Hard drives fail mechanically — worn motors, head crashes, death by being knocked off a desk while spinning. The upside: they usually warn you first. Watch SMART data for reallocated sectors, listen for clicking, and you typically get days or weeks to copy data off.
SSDs fail silently. The NAND wears gradually (a 1TB drive rated at 600 TBW would take decades to exhaust at a typical 10–30 GB written daily, so don’t worry about endurance), but a dead controller bricks the whole drive instantly with no warning. And here’s the archive catch: worn NAND in an unplugged SSD can start losing data within a year at warm temperatures. Flash is not a shelf medium.
Practical takeaway: irreplaceable stuff belongs on the HDD, copied to an external drive or cloud too. Neither drive type counts as a backup on its own.
Sensible splits by budget
Tight budget: Skip the HDD entirely. A single 1TB SSD covers OS, apps, and games; keep overflow media on an external drive.
Typical build (~$150 for storage): 1TB NVMe for OS, apps, and current games, plus a 4TB HDD for media and backups. This is the sweet spot for most people.
Game-heavy library: If your bulk storage is games rather than video, a second SSD beats the HDD. A 2TB SATA SSD makes a fine dedicated game drive — SATA is slower than NVMe on paper, but for game loads the difference is a second or two, not the gulf between SSD and HDD.
The short version: anything you wait on goes on the SSD; anything you just keep goes on the HDD. If a file’s only job is to exist, it’s wasting flash.
