NVMe vs SATA for a Steam Library: 970 EVO Plus vs BX500

For a modern PC game library in 2026, an NVMe SSD like the SAMSUNG 970 EVO Plus shaves only a few seconds off most level loads compared with a good SATA SSD such as the Samsung 870 EVO. The measurable gap widens once a title uses DirectStorage or streams open-world assets continuously. For everything else, cost per terabyte matters more than sequential throughput.

Who should read this

The reader this article is aimed at is holding a motherboard with exactly one M.2 slot, four to six SATA bays, and a Steam library that has quietly grown past two terabytes. The question isn't really "NVMe or SATA" — it's "which games belong on which drive" and, harder, "is the cheap 1 TB SATA disk actually a false economy once you factor patches and installs." That framing changes the answer.

There are three real constraints that push the decision. The first is bandwidth on the paper spec sheet, which is where most side-by-side comparisons stop and where SATA loses so decisively that people assume the gap must matter in games. Per Samsung's product page, the 970 EVO Plus tops out at 3,500 MB/s sequential read; the SATA III interface caps at roughly 560 MB/s no matter how good the flash is. That's a 6× advantage on paper.

The second constraint is what actually bottlenecks a game load, which per public Tom's Hardware storage coverage and Digital Foundry teardowns of specific engines is asset decompression on the CPU rather than raw sequential throughput. The third is money — the price-per-terabyte gap between the cheapest DRAM-less SATA drive and a mid-range NVMe has narrowed but is still real in 2026, and a 4 TB SATA drive that lets you keep three times as many games installed is a genuine quality-of-life win a 1 TB NVMe can't match.

The rest of this piece is the ranking of when those constraints flip, the drives that map to each tier, and the specific arrangement that gets you the fastest active-game loads without paying to store a 90 GB shooter you played twice on premium flash.

Key takeaways

• On the same title, moving from a SATA SSD like the Crucial BX500 to an NVMe drive typically shaves 1-4 seconds off a level load in games without DirectStorage, based on published Digital Foundry and AnandTech coverage of DirectStorage load-time analysis.
• The transformative jump is HDD to any SSD; that comparison routinely halves load times in the same benchmark set.
• DirectStorage-enabled titles are where NVMe pulls decisively ahead — some published measurements show 40-60% faster load times versus SATA on the same engine.
• A DRAM-less SATA drive like the SANDISK SSD PLUS 480GB is a reasonable game-library pick because game workloads are read-dominated after install; the same drive would be a poor choice as a Windows boot drive.
• The most efficient two-drive tiering in 2026 is a 500 GB - 1 TB NVMe for the OS and 3-5 actively played titles, plus a 2-4 TB SATA drive for the backlog.

Step 0 — diagnose your board before you buy anything

Before you buy any drive, open your motherboard manual and confirm three things. First, how many M.2 slots are populated versus available: mid-range boards frequently ship a single primary M.2 slot in a heatsink shroud, with the second slot behind the GPU. Second, whether the second M.2 slot shares PCIe lanes with a SATA port or a PCIe x16 slot — on many B550 and B650 boards, populating M.2_2 disables SATA ports 5 and 6, which is a surprise if you were counting on running the M.2 and a fifth SATA disk simultaneously. Third, whether the primary M.2 slot is PCIe 4.0 or 3.0; a 970 EVO Plus is a PCIe 3.0 x4 drive that will run at spec in either, but a newer 4.0 drive throttled to 3.0 spends the price premium on bandwidth you can't use.

The lane-sharing footnote catches more people than the actual drive choice. If your board disables two SATA ports the moment you install a second NVMe, and you were planning to keep the backlog on two 4 TB SATA drives, the plan collapses. Read the manual page titled something like "shared bandwidth notes" before you spend anything.

Once the slot count is known, the drive decision is straightforward: fill the fast M.2 with an NVMe, put bulk storage on SATA, and stop worrying about the paper-spec-sheet delta.

Spec-delta table

The published specs paint an intentionally lopsided picture — the sequential-read column is the one every marketing page leads with, and it's also the number that matters least in games.

Sources: Samsung's 970 EVO Plus product page and manufacturer datasheets aggregated by Tom's Hardware storage reviews. Street prices vary weekly; check the linked product pages for current pricing.

The columns that actually matter for a game library are the endurance rating and price-per-terabyte, not the sequential read. A game library is overwhelmingly read-heavy after the initial install and the occasional patch; you will not exhaust the TBW figure on any of these drives in a normal service life.

Benchmark table — published game load times

Aggregating published load-time data from independent outlets — AnandTech's DirectStorage analysis, Digital Foundry teardowns, and Tom's Hardware SSD roundups — a representative modern title behaves roughly like this at cold-cache load:

Numbers are order-of-magnitude — the specific value depends on CPU, GPU, mods, and shader-cache state. What the shape of the table shows is what matters: the HDD-to-SSD jump is the transformative one, the SATA-to-NVMe jump is a few seconds on non-DirectStorage titles, and the NVMe-to-NVMe-with-DirectStorage jump is another 2-3x when the engine actually asks the drive to work.

Why the gap is smaller than the spec sheet implies

Games do not load like large sequential-transfer benchmarks. A typical level load is a scatter of tens of thousands of small reads, each pulling a compressed texture or shader blob that then has to be decompressed on the CPU before it can be handed to the GPU. The rate-limiting step is that CPU-side decompression, not the drive's headline throughput.

There are three reasons this matters. First, queue depth: game engines historically issued reads one or two at a time, well below the deep queues that make NVMe's parallelism shine. Even when a drive can serve 600,000 IOPS in a benchmark, if the engine only asks for four outstanding reads at a time, the drive is idle for most of the load. Second, decompression stalls: once the CPU falls behind on decompression, feeding it faster reads doesn't help. The bottleneck migrates upstream, and a 970 EVO Plus and a Crucial BX500 finish within a handful of seconds because both are waiting for the same AMD Ryzen 7 5800X core to unpack the same textures.

Third, shader compilation on modern DX12/Vulkan titles is often mistaken for load time. What looks like a slow "loading" screen is frequently the first pass compiling shaders — a workload that is entirely CPU-bound and completely insensitive to which SSD you bought. This is why cold-cache load times on a fresh install can be 40 seconds while the same level on a warm cache loads in eight, and why the fix is either a slower first launch or a bigger shader-cache directory, not a faster drive.

Where NVMe genuinely wins

There are specific scenarios where the NVMe advantage stops being a rounding error. DirectStorage titles are the headliner. By moving decompression to the GPU and letting the engine issue deep parallel read queues, DirectStorage lets a drive like the 970 EVO Plus complete an asset stream in a fraction of the time a SATA drive can, per AnandTech's published measurements. Forspoken and Ratchet & Clank on PC are the reference cases — expect the DirectStorage title list to keep growing through 2026 and 2027 as the API matures.

Shader-cache-heavy launches are the second. First launch of a major DX12/Vulkan title writes a shader cache directory that can hit several gigabytes. Subsequent launches read that cache back before hitting the main menu, and on a fast drive with low random-read latency, that "invisible" step drops from a few seconds to less than one.

Third: scratch space. If you record replays, use Steam's built-in remote play, edit Reshade LUTs, or capture with OBS to the same drive you're gaming on, NVMe's higher sustained write and lower queue-depth latency prevent the frame-time hitches that show up when a SATA drive is asked to do two things at once.

Where SATA is the smarter money

The complement of that list is where a SATA drive is not just adequate but the correct pick. Bulk library storage is the obvious case: two 4 TB SATA drives will cost less than one 4 TB NVMe and let you keep the entire library installed without triaging what's on-disk. Second-drive expansion on a board with only one M.2 slot is the second case — you can't add a second NVMe without either an M.2 add-in card or lane-sharing tradeoffs, and neither is worth it just to speed up a level load that's already under 20 seconds.

Older systems without a spare PCIe 3.0 x4 lane are the third case. A 2018-era motherboard often only has one M.2 slot and reserves it for a specific list of drives; a SATA disk is a drop-in upgrade that costs nothing to reason about. And for laptops with one M.2 slot and no meaningful expansion, a large SATA disk in a USB 3.2 Gen 2 enclosure is a legitimate backlog drive that costs less than the equivalent NVMe upgrade.

DRAM-less and QLC caveats

Both the Crucial BX500 1TB and the SanDisk SSD PLUS 480GB are DRAM-less designs that lean on the host system's memory (via Host Memory Buffer on NVMe, or without any DRAM cache on SATA) to hold the mapping table. In sustained random-write workloads — a database, a video-editing scratch disk, an OS boot drive that swaps heavily — the missing DRAM cache shows up as a throughput cliff once the SLC cache fills. On a games drive, you'll notice it during the install itself and during multi-tens-of-gigabyte patches, where the write speed drops from the advertised 500-something MB/s to more like 80-120 MB/s.

For reads — the operation that actually loads a game — the DRAM-less penalty is small enough to be invisible under a stopwatch. Both drives are appropriate as backlog storage. Neither should be your Windows boot drive if you can afford to avoid it, because OS workloads are exactly the sustained-random-write pattern the design compromises around.

QLC flash carries a related caveat. A QLC drive advertises high sequential numbers behind a fast SLC cache; once the cache fills, sustained write speed can drop below what a decent hard drive delivers. The cache refills during idle time, so most gamers never see the cliff. Someone re-downloading a 300 GB library from Steam in one sitting will. Read the review for the specific capacity you're buying — cache sizes vary dramatically between the 500 GB and 2 TB versions of the same product name.

The tiering recipe

The arrangement that gets the most benefit for the least money in 2026 looks like this:

• Boot drive plus the 3-5 games you're actively playing right now: 500 GB - 1 TB NVMe. The SAMSUNG 970 EVO Plus is the obvious pick here — mature firmware, real DRAM cache, endurance that will outlive the platform.
• Backlog and idle library: 2-4 TB SATA. The Samsung 870 EVO if you want the most conservative flash and long endurance; the Crucial BX500 1TB if you're paying by the terabyte and don't care about occasional slow patches.
• Cold storage / offline archives: 8 TB+ 7,200 rpm HDD in an external enclosure. Not for gameplay — for the "I might reinstall this in 2028" pile.

When you want to play something from the backlog, either move it to the NVMe first (Steam's built-in library-move takes a few minutes and the game then loads at NVMe speed for as long as it sits there) or accept a few extra seconds of load and play it in place. Either is fine. The important part is that you're paying NVMe prices only for the games you're actually playing.

Thermals and the rest of the build

An NVMe drive tucked directly under a hot graphics card can push into thermal throttling during long sequential transfers — the symptom is a sudden throughput cliff mid-transfer rather than a gradual slowdown. Most current motherboards ship an integrated M.2 heatshield for the primary slot that handles this for free; if your board doesn't, a thin adhesive M.2 heatsink costs a few dollars and closes the issue permanently.

Airflow pattern matters too. A CPU cooler that pulls air across the M.2 area helps more than the same TDP-class cooler that vents directly at the drive. This mostly matters for sustained-write workloads that a games drive rarely hits, but if you record long OBS captures to the same NVMe you're gaming on, add the heatsink.

For SATA drives, thermals are almost never the constraint — the 3.5" and 2.5" form factors dissipate heat easily and the maximum sustained throughput is a fraction of what an NVMe can push. Mount them wherever the cable routing is cleanest.

Perf-per-dollar math

Take a mid-range 1 TB configuration in 2026 (street prices, ballpark):

Read that table honestly: the NVMe premium is small enough in 2026 that if your budget is anywhere near $95, the 970 EVO Plus is the smarter buy for the boot drive because the extra bandwidth also helps every non-game workload that touches the disk. For pure bulk library storage, spending twice as much per terabyte on NVMe is a poor trade — a $150 4 TB SATA drive stores four times as many games as a $150 1 TB NVMe, and that quality-of-life win dwarfs 3 seconds per load.

Verdict matrix

Buy NVMe if:

• You're building a new system and the NVMe cost premium is under 20% per terabyte
• You want a boot drive plus actively-played games on the same fast disk
• You play DirectStorage titles or plan to (the list is growing)
• Your workflow includes recording OBS captures, editing, or heavy scratch-disk work

Buy SATA if:

• Your motherboard has one M.2 slot and it's already used
• You need bulk backlog storage and want maximum GB per dollar
• You're expanding an older system that doesn't have PCIe 4.0 headroom to justify a modern NVMe
• You want long endurance and don't need the peak throughput

Buy both and tier if:

• You have both slots and a growing library (the most common case)
• You want the fastest possible active-game load times without paying to store the entire backlog on premium flash
• You're okay moving occasional titles between drives when you rotate playlists

Bottom line

For a mainstream PC gamer in 2026, the right arrangement is a mid-range NVMe like the SAMSUNG 970 EVO Plus as boot + active-game drive, paired with a large SATA drive like the Samsung 870 EVO or the Crucial BX500 1TB for the backlog. The NVMe pays for itself in DirectStorage titles, shader-cache load times, and the everyday responsiveness of a boot drive with real DRAM cache; the SATA drive pays for itself the first time you don't have to uninstall a 90 GB game to make room for a new one. Skip the temptation to put everything on NVMe — the paper-spec advantage doesn't translate proportionally to game load times, and the money is better spent on more capacity.

Related guides

• Best M.2 slot configurations for 2026 gaming builds
• DirectStorage on PC — the current title list and what it means for your next drive
• Ryzen 7 5800X vs 5800X3D for game loads
• Best budget SATA SSDs 2026

Citations and sources

• Samsung — 970 EVO Plus product page — accessed August 2026
• Tom's Hardware — Best SSDs — accessed August 2026
• AnandTech — SSD + DirectStorage game load analysis — accessed August 2026

This piece is editorial synthesis based on publicly available information. No independent first-party benchmarking is reported.