System
DirectX Shader Cache
Windows stores compiled Direct3D shader binaries in the DirectX Shader Cache under D3DSCache so games and graphics apps do not have to recompile HLSL and pipeline state data every launch. Those cached blobs speed up startup and reduce in-game shader compilation, but they can become stale after GPU driver updates, game patches, or graphics API changes. Kudu removes the cached DirectX shader binaries so Windows and your apps can rebuild fresh copies without affecting saved games, settings, accounts, or personal files.
Why clean DirectX Shader Cache?
- Shader binaries compiled against an older GPU driver can be invalid after a driver update, causing stutter, hitching, or a long shader recompilation phase when a game first loads
- Stale cached shaders from a game patch can produce missing textures, black surfaces, flickering effects, or broken lighting until the cache is rebuilt
- Corrupted entries in D3DSCache can lead to repeated micro-stutter during gameplay because Direct3D keeps falling back to recompiling shaders on demand
- An oversized shader cache wastes SSD space and can grow quietly across multiple games, which users usually notice as unexplained storage loss in LocalAppData
- Outdated pipeline cache data can increase startup times after major graphics setting changes because the app must discard bad cache hits and regenerate compatible shader variants
- Driver-level shader cache mismatches can show up as crashes or freezes when entering menus, loading a level, or switching to a scene with new post-processing effects
What gets cleaned
Cache paths Kudu targets
Windows
%LocalAppData%/D3DSCache |
Frequently asked
Common questions about DirectX Shader Cache
Related cleaners
Free & open source
Download Kudu and reclaim your disk space.
Available on Windows, macOS, and Linux. No account required, no feature gates, no telemetry without consent. All cleaning targets are open source and community-auditable.