Does DirectStorage Need a Gen5 SSD?

What Microsoft actually documents

Microsoft's Xbox-console DirectStorage overview states the design goal as CPU-overhead reduction: "allow a title to sustain 50K IOPS and only use between 5% and 10% of a single CPU core," with a console storage minimum of "2.0 GB/s over a 250 ms window." That document explicitly scopes itself to consoles. On the PC side, Microsoft's own DirectStorage GitHub repository describes the target storage only as "high-speed storage (such as NVMe SSDs) that can deliver multiple gigabytes a second" - no PCIe-generation requirement stated.

The API's other documented purpose is GPU decompression: Microsoft's own repository states it supports "decompressing built-in formats... using the GPU which frees up the CPU for other tasks." That is a separate mechanism from the storage-speed question - it changes where decompression work happens, not what storage generation a title needs to supply the compressed data in the first place.

What the one relevant benchmark found

The one DirectStorage-specific game benchmark we could cite - Forspoken, reported by Tom's Hardware - found the full gap between a Gen3 and a Gen5 drive totalled roughly three seconds across the whole benchmark, with Gen4 and Gen5 essentially tied. That result runs against the assumption a buyer might reasonably make: that a title built specifically to exercise DirectStorage would be the clearest possible showcase for a generation gap. Instead, per this citation, the pattern matches everything else in our Gen4-vs-Gen5 coverage - the real jump sits between Gen3 and Gen4, not Gen4 and Gen5. See /gaming-ssd/directstorage for the full citation and the honest state of game adoption.

Why the assumption is so easy to make anyway

DirectStorage's own marketing framing, and a fair amount of secondary coverage repeating it, ties the API tightly to "next-generation" hardware in a way that invites the inference that next-generation storage - meaning the newest PCIe generation available - is what the API actually needs. That inference does not survive contact with either the documentation or the one benchmark that has actually tested it. The API's real target, per Microsoft's own words, is the class of hardware capable of high-IOPS, low-CPU-overhead transfers - a bar that Gen4 clears as comfortably as Gen5 does, per the measured evidence above.

This matters beyond a single buying decision, because it is the same pattern this cluster documents repeatedly: a technology's branding outruns what its own documentation and the available testing actually support, and a generation label becomes a stand-in for a claim nobody actually measured. DirectStorage is a genuinely real, genuinely useful API by Microsoft's own stated design goals - the CPU-overhead reduction and IOPS figures above are real numbers from a real specification. What isn't supported by anything we could find is the specific claim that it requires the newest available storage generation to deliver those goals.

The adoption question sits alongside the hardware question

Even setting the generation question aside entirely, a second, independent limiting factor applies: DirectStorage support has to actually be implemented by the specific game you're playing, and per the one dated count we could cite, that remains true of a small slice of the overall game catalogue. A buyer optimizing a storage purchase specifically around DirectStorage benefits is optimizing for a feature that may not be present in most of what they actually play - a consideration that matters independently of, and arguably more than, which PCIe generation sits underneath it.

Put the two findings together and the practical guidance is straightforward: buy storage sized and generationed for your broader needs - see our Gen4-vs-Gen5 and capacity pages for that fuller picture - rather than around DirectStorage specifically, since neither the API's own documented requirements nor the one benchmark that has tested it support treating Gen5 as a DirectStorage prerequisite.

What we're not claiming

We are not claiming DirectStorage delivers no benefit over the traditional Windows storage API on any hardware - Microsoft's own stated design goals (the IOPS and CPU-overhead figures cited above) describe a real architectural improvement, and the API genuinely does what Microsoft says it does. What we are specifically declining to claim is that it requires the newest available PCIe generation to deliver that improvement, because neither Microsoft's own documentation nor the one benchmark we could cite supports that narrower claim - and that narrower claim is the one this page exists to check.

If you already own a Gen5 drive

None of this is an argument to downgrade. If a Gen5 drive is already in your system, DirectStorage-enabled titles will use it exactly as they would a Gen4 drive - the API doesn't penalize newer hardware, it simply doesn't require it, per the evidence cited above. This page exists for the buying decision, not for someone deciding whether to keep hardware they already have.

The same logic applies in reverse to a Gen3 system, with one caveat worth naming: the Compusemble Forspoken benchmark Tom's Hardware reported on did find a real, if modest, Gen3-to-Gen4 gap - the step this cluster's evidence consistently identifies as the one that actually matters. A Gen3-to-Gen4 upgrade sits on firmer measured ground than a Gen4-to-Gen5 one does, for DirectStorage or otherwise.

Live picks - Gen4 and Gen5

Sorted by $/GB, cheapest first. No speed column - see the doctrine note on the gaming SSD hub.