How to Clear Shader Cache to Fix Stuttering (NVIDIA, AMD, Steam)

Published

On this page

Shader cache problems have one signature: stutter that appeared after a driver update or game patch, in an otherwise healthy system. Clearing the cache forces a clean rebuild and removes corrupted entries. Here’s where the caches live for each vendor and launcher.

How to Clear Shader Cache to Fix Stuttering

Stale shaders hitch. Fresh shaders compile once, then run smooth.

When this is your fix (and when it isn’t)

Clear the cache when:

  • Stutter started right after a driver or game update
  • One specific game hitches while others are fine
  • Hitching happens the first time effects/areas appear, then repeats anyway

Look elsewhere when: every game stutters equally (lag spikes guide), or stutter correlates with loading new areas (storage) or fights (CPU bottleneck).

NVIDIA

  1. Close all games and launchers.
  2. Press Win+R → %localappdata%\NVIDIA\DXCache → delete the contents.
  3. Also check %localappdata%\NVIDIA\GLCache and %programdata%\NVIDIA Corporation\NV_Cache if present.
  4. Reboot.

NVIDIA rebuilds caches automatically. You can also raise the cache size limit: NVIDIA Control Panel → Manage 3D Settings → Shader Cache Size → 10 GB or Unlimited — a small cache evicts shaders that then recompile mid-game (full NVCP guide).

AMD

Adrenalin has it built in:

  1. Adrenalin → Gaming → Graphics → Advanced → Reset Shader Cache.
  2. Or manually: %localappdata%\AMD\DxCache (and DxcCache/VkCache folders).
  3. Reboot.

More Radeon tuning in the Adrenalin settings guide.

Steam (Vulkan/OpenGL pre-caching)

Steam ships pre-compiled shaders for some games:

  1. Steam → Settings → Downloads → Shader Pre-caching — keep it on in general (it prevents stutter).
  2. To rebuild a corrupted set: delete Steam\steamapps\shadercache\{appid} for the affected game, then verify game files.

Per-game caches

Some engines keep their own (paths vary): Unreal Engine games under %localappdata%\{GameName}, Call of Duty rebuilds via an in-game “Restart Shader Pre-Loading” option, and many DX12 titles recompile at the menu after updates. Let any in-game shader preparation finish before queueing — joining a match mid-compile is self-inflicted stutter.

After clearing: expect one rough session

The first launch recompiles everything — menus load slower and early gameplay hitches. That’s the rebuild, not a failure. Give it one session, then judge with a frame-time overlay.

If stutter survives a cache rebuild and a DDU clean driver install, the cause is system-level — work through Game Bar/DVR, VBS, and power plan next.

Frequently asked questions

What is shader compilation stutter?

Games compile GPU shaders for your exact hardware and driver. When a shader is compiled mid-gameplay instead of beforehand, the frame waits on it — that pause is the stutter you feel.

Does clearing the shader cache improve FPS?

Not average FPS — it fixes hitching. The first session after clearing is actually rougher while shaders rebuild; the payoff is removing corrupted or stale entries that caused persistent stutter.

How often should I clear the shader cache?

Only when you have a reason: stutter that appeared after a driver update or game patch. It is a troubleshooting step, not maintenance.

Why does my game stutter after every driver update?

Driver updates invalidate every compiled shader, so each game recompiles on the next launch. One warm-up session per game is normal; persistent stutter beyond that is when you clear the cache.