The old loading path, and why it was slow
Under the classic Win32 storage path, a game streaming a level asks the operating system for thousands of small file reads. Each request crosses kernel boundaries, gets queued, and copies data through several buffers before the game engine ever sees it. The engine then decompresses those assets on the CPU, which competes with the game itself for the same cores. The result is a pipeline where fast NVMe hardware spends much of its time waiting on software overhead.
DirectStorage, introduced with Windows 11 in 2021 and refined in later SDK versions, attacks both bottlenecks. It batches many small reads into a few large requests and submits them with far less kernel friction, so the drive actually gets used. And since DirectStorage 1.1 in late 2022, decompression can run on the GPU through DirectCompute instead of burning CPU cores — which is why vendors ship their own variants, like RTX IO on NVIDIA cards. Games that adopt it properly stream worlds continuously instead of hiding behind loading screens.
What it means for load times — honestly
The number to keep in mind is this: Microsoft's famous “up to 40 times faster” claim came from an I/O-stack throughput demo, not from a stopwatch on a loading screen. Shipped games show a real but far more modest picture, and the biggest win is usually what you don't see — the absence of mid-game stutter while a world streams around you.
- The 40x figure measures batched I/O throughput in a synthetic path, not end-to-end load time — expect seconds, not miracles
- Forspoken (2023) was the first PC title to ship it; Ratchet & Clank: Rift Apart used it to keep dimensional rifts seamless on PC
- The clearest benefit is streaming: fewer hitches and pop-in in open worlds, because assets arrive faster than the engine needs them
- Requirements are modest: an NVMe SSD and a DirectX 12 GPU with Shader Model 6.0 support — most gaming PCs of the last decade qualify
- It is per-game engineering work in the engine, not a Windows feature you can switch on for older titles
- Install sizes do not shrink; if anything, some titles ship assets less compressed, since the GPU can now decompress fast enough to keep up
What you actually control
You cannot enable DirectStorage yourself — a game either supports it or doesn't, and the list of titles that do is still short but growing. What you can do is keep the path ready: install games on an NVMe drive rather than a SATA SSD or HDD, where the API's benefits mostly evaporate. Keep GPU drivers current, because DirectStorage and RTX IO fixes ship inside ordinary driver packages, and keep Windows itself updated.
Don't buy hardware for DirectStorage alone. Current titles don't come close to saturating a good PCIe 3.0 drive, so Gen4 or Gen5 buys future headroom, not faster loading today — check real game benchmarks before paying for bandwidth no engine requests. And ignore any “DirectStorage optimizer” utility: there is nothing on your side to optimize, and nothing to clean. The API changed how games read disks; the boring habits — fast drive, current drivers, sensible capacity — are still your entire job.
Questions and Answers
Does DirectStorage make games load faster?
Yes, in titles built for it — typically by some seconds, not by an order of magnitude. The bigger, less advertised win is smoother in-game streaming without stutter.
Can I turn on DirectStorage for my existing games?
No — it is engine-level support each game must be built with, not a Windows switch. If a title supports it, the game uses it automatically on qualifying hardware.
Know what is included before you buy.
The one-time 30-minute trial covers core tools. PRO-labelled features stay locked until a paid license is activated.
Read next
Write to us: [email protected]