GPU Cache
NVIDIA Shader Cache
NVIDIA’s Linux driver stores compiled GPU program binaries in GLCache so OpenGL applications can reuse previously compiled and linked shaders instead of rebuilding them every launch. The cache holds driver-specific shader objects, program binaries, and pipeline-related blobs generated from game and app workloads; Kudu removes these stale compiled shader files so the driver can regenerate clean copies without affecting saves, settings, accounts, or game data.
Why clean NVIDIA Shader Cache?
- Compiled shader blobs created under an older NVIDIA driver can become invalid after a driver update, causing hitching, long first-load pauses, or repeated recompilation until the cache is rebuilt
- Corrupted GLCache entries can make a game stall on splash screens or during shader-heavy scene changes because the driver keeps failing to load and recompiling bad binaries
- Per-game shader binaries accumulate across many titles and Proton prefixes, so the cache can grow unexpectedly large and consume disk space in home directories on smaller Linux installs
- Stale program binaries tied to previous GPU microcode or driver optimization paths can cause intermittent stutter, especially when entering menus, loading maps, or panning across effects-heavy scenes
- If the cache contains mismatched OpenGL shader artifacts after a game patch, you may see unusually long launches or a temporary drop in frame pacing while every shader variant is rebuilt
- Deleting old GLCache data is safe because the NVIDIA driver recreates it automatically; the main visible effect is one slower first run per affected game, followed by normal caching behavior
What gets cleaned
Cache paths Kudu targets
Linux
~/.cache/nvidia/GLCache |
Frequently asked
Common questions about NVIDIA 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.