Microsoft DirectStorage Explained: NVMe, GPU Decompression, Windows 11 Requirements, and Game Support

Microsoft DirectStorage gives game developers a storage and decompression path designed for modern asset streaming. The important boundary is software support: a game has to implement DirectStorage and prepare its asset pipeline to use it. Installing an NVMe SSD does not automatically convert every Windows game to DirectStorage, and Windows does not expose a universal DirectStorage toggle that forces unsupported games onto the API.

That distinction separates platform capability from observed performance. Storage media, I/O submission, compressed asset layout, decompression, GPU upload, engine scheduling and the game’s own loading logic can all affect what the player sees. DirectStorage can change parts of that pipeline, but the API name alone does not establish a particular load-time or frame-rate gain.

Microsoft’s current Windows 11 requirements page says DirectStorage requires an NVMe SSD to store and run games that use the Standard NVM Express Controller driver, plus a DirectX 12 GPU with Shader Model 6.0 support. Those are Microsoft’s current Windows 11 feature requirements; they are not a recommendation for one PCIe generation, one SSD model or one sequential-throughput number.

PCIe generation and advertised MB/s therefore should not be treated as a binary DirectStorage test. An NVMe drive can differ in controller, NAND, firmware, queue behavior, thermals and sustained performance, while the game still has to use the API correctly. Conversely, a very fast drive does not make an application a DirectStorage title by itself.

Modern game assets can be divided into many reads rather than one continuous file transfer. Microsoft designed DirectStorage around high-performance storage and batched I/O submission so software can issue large numbers of requests with less per-request CPU overhead than a traditional one-request-at-a-time model. That matters most when the application is actually structured to feed the pipeline efficiently.

This is different from saying that random-read performance, sequential bandwidth or queue depth alone predicts a game’s loading time. The storage request pattern is created by the title, and later stages can become the limiting work. Core Tech Tips therefore treats storage throughput and I/O submission efficiency as related but separate parts of the DirectStorage path.

DirectStorage 1.1 added GPU decompression and Microsoft’s GDeflate compression format. For eligible requests whose destination is a Direct3D 12 GPU resource, DirectStorage can move compressed data through the GPU path and decompress it on a compute queue. This can move decompression work away from the CPU in software designed around that path.

GPU decompression is not the same thing as the SSD sending data directly into final rendered pixels. Storage I/O, transfers, decompression and placement into the destination resource remain distinct stages. A title also has to package and request compatible compressed assets; merely owning a supported GPU does not make unrelated game data use GDeflate.

Microsoft documents GPU decompression support on DirectX 12 Shader Model 6.0 GPUs. Hardware vendors can additionally provide optimized metacommands for their GPUs. If that optimized path is unavailable, DirectStorage 1.1 can use its DirectCompute fallback implementation; if the GPU or driver cannot use that fallback, DirectStorage can decompress on the CPU.

Microsoft also documents CPU decompression for requests whose destination is system memory, avoiding the extra cost of sending data to the GPU only to read it back. These fallbacks are important because they show why “supports DirectStorage” is not one single hardware execution path and why vendor-driver optimization should not be turned into an unsupported universal performance claim.

Microsoft’s current Windows 11 feature-requirements documentation defines DirectStorage in Windows 11 around NVMe storage using the Standard NVM Express Controller driver and a DirectX 12 Shader Model 6.0 GPU. Older Microsoft developer material around the PC launch also described DirectStorage support on Windows 10 while recommending Windows 11 for the newest storage-stack optimizations.

Those statements answer different questions and were published in different product contexts. This guide uses the current Windows 11 requirements for a present-day Windows 11 compatibility check rather than turning older launch guidance into a timeless requirement for every DirectStorage runtime or game. For Windows 10 specifically, check the title and current Microsoft/runtime documentation instead of assuming the Windows 11 feature table applies unchanged.

DirectStorage is developer-facing infrastructure. A game must integrate the API, submit its storage work through it and, where GPU decompression is used, build an appropriate compressed-asset workflow. The operating system cannot safely infer and rewrite an arbitrary game’s asset pipeline after installation.

For that reason, a hardware checklist and a game-support checklist are separate. Meeting Microsoft’s Windows 11 DirectStorage feature requirements means the PC provides the relevant platform capabilities; it does not prove that a particular game uses DirectStorage, uses GPU decompression, or benefits by a specific amount. Game-specific support should come from the developer or another reliable first-party source.

If you are diagnosing a game that loads slowly or streams assets poorly, first establish whether the title actually uses DirectStorage and whether your PC meets the title’s own storage and GPU requirements. Then consider the whole path: drive behavior, free space and thermals, CPU/GPU workload, drivers, asset decompression and the game engine. Changing one component cannot guarantee a fixed result when another stage is limiting.

For the broader SATA-versus-NVMe buying decision, the Core Tech Tips NVMe vs SATA gaming comparison owns the interface, latency, thermals and upgrade-value question. This page has the narrower job of explaining the DirectStorage API and its current Windows requirements without converting Microsoft’s capability claims or SDK examples into a universal gaming benchmark.