GPU Cache
AMD Shader Cache
AMD’s driver stores compiled GPU shader artifacts on disk so games and 3D apps do not have to recompile the same DirectX pipeline state objects, OpenGL program binaries, and Vulkan pipeline cache data every launch. Those files accumulate under DxCache, GLCache, and VkCache, and can become invalid after driver updates, game patches, or shader changes. Kudu removes these AMD shader cache files so the driver can rebuild fresh per-game caches without touching saves, settings, accounts, or other personal data.
Why clean AMD Shader Cache?
- Shader blobs compiled against an older AMD driver can become invalid after a driver update, causing stutter, hitching, or unusually long shader recompilation the next time a game reaches menus or new areas
- A corrupted DirectX cache entry in DxCache can trigger repeated in-game microstutter as the driver falls back to recompiling pipeline state during gameplay
- Stale OpenGL program binaries in GLCache can cause black textures, missing effects, or a slow first load while the application recompiles shaders from source
- Outdated Vulkan pipeline cache data in VkCache after a game patch can lead to long startup shader processing screens or hitching when new effects appear for the first time
- Large per-game cache buildup across DxCache, GLCache, and VkCache wastes SSD space, which users usually notice as unexpectedly high LocalAppData storage usage
- If a game’s shader cache files become inconsistent, users may see crashes during startup, freezes on the splash screen, or repeated recompilation every launch until the cache is rebuilt
What gets cleaned
Cache paths Kudu targets
Windows
%LocalAppData%/AMD/DxCache |
%LocalAppData%/AMD/GLCache |
%LocalAppData%/AMD/VkCache |
Frequently asked
Common questions about AMD Shader Cache
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.