Shader Compilation Stutter — The Fix Most Guides Get Wrong
The hitching in modern PC releases is usually shader compilation. Here is how to identify it, and the cache settings that actually eliminate it.
The short answer
Shader compilation stutter appears as a brief freeze the first time a new effect, weapon or area is rendered, and it does not repeat in the same session once that shader is cached. The reliable fixes are setting the NVIDIA shader cache size to Unlimited (or clearing a corrupt cache on AMD), letting any in-game shader pre-compilation step finish rather than skipping it, and keeping the cache on a fast drive with free space.
Verified and last updated August 12, 2026.
- Time needed
- 20 min
- Difficulty
- Intermediate
- Read time
- 4 min
Every modern PC release gets the same complaint in the first week: it stutters, on hardware that should be comfortable. Usually the answer is shader compilation, and it behaves differently enough from other stutter that it is easy to identify once you know the pattern.
The one-time rule
Shader compilation stutter happens once per shader per session. The first grenade hitches. The second does not. If your stutter repeats every single time you do the same thing, stop reading this and go to how to fix stuttering in games — you have a different problem.
Step 1: Confirm it is actually shader stutter
Step 2: Set the shader cache size to Unlimited
The default limit is too small for current games. When the cache fills, old shaders are evicted and recompiled next time you encounter them — a one-time cost becomes permanent.
NVIDIA: Control Panel or NVIDIA App 2 min
Manage 3D Settings → Global Settings → Shader Cache Size → Unlimited. Apply, then restart the game. This is a global setting and applies everywhere.
AMD: Adrenalin 2 min
Graphics → Advanced → confirm Shader Cache is set to AMD Optimised or On, not Off. AMD does not expose a size limit in the same way, so the equivalent action is making sure it is not disabled and the cache location has free space.
Give it disk space 1 min
An unlimited cache will grow to tens of gigabytes across a large library. If the drive holding it is nearly full, Windows will start evicting and you are back where you started. This is the step people skip.
Step 3: Clear a corrupt cache
Only if the stutter is permanent and never settles down after several sessions in the same content. That pattern suggests the cache is corrupt and shaders are being recompiled endlessly.
Windows: Disk Cleanup → tick DirectX Shader Cache → OK.
Manually, delete the contents of:
%localappdata%\NVIDIA\DXCache%localappdata%\NVIDIA\GLCache%localappdata%\D3DSCache%localappdata%\AMD\DxCacheon AMD systems
Then expect one bad session while everything recompiles. That is the cost, and it is why routine clearing is a bad idea.
Do not clear the cache as maintenance
Every clear guarantees the stutter returns for a session. Clear after a driver update that changed shader behaviour, or when you have evidence of corruption. Not weekly, and not because a video told you to.
Step 4: Stop skipping the pre-compilation step
A growing number of games compile shaders during a loading screen or on first launch, and it can take several minutes. Skipping it does not save time — it moves the compilation into gameplay, where it becomes the stutter you are trying to avoid.
Let it finish. Do it once after every driver update, because a driver change invalidates the compiled shaders.
The supporting settings
These do not fix shader stutter on their own but they stop it being made worse:
- Cap your frame rate three to five below your refresh rate with an external limiter. Consistent pacing makes the remaining hitches far less noticeable.
- Disable overlays — Discord, Steam, the NVIDIA overlay. They inject into the render pipeline and amplify hitching.
- Keep the game and cache on an SSD. Compilation involves substantial disk writes and a mechanical drive turns a hitch into a freeze.
- Do not run a shader-heavy game while something else is compiling — a background game update or Windows update competes for exactly the same CPU cores.
What works
What doesn't
Key takeaways
Frequently asked questions
How do I know it is shader stutter and not something else?
The signature is that it happens once. The first grenade you throw hitches, the first time you enter a new biome hitches, and neither repeats for the rest of that session. If a stutter recurs every time you do the same thing, it is not shader compilation — that is more likely a memory, streaming or frame-pacing problem. Shader stutter also disappears almost entirely on a second playthrough of the same area.
Does setting the shader cache to unlimited actually help?
Yes, substantially, and it is the single most effective setting change for this problem. The default cache limit is far too small for current games, so older shaders get evicted and then recompiled the next time you encounter them — which turns a one-time cost into a permanent one. Unlimited lets the cache grow to the size the game actually needs. The disk cost is real but modest compared with the size of the games themselves.
Should I clear my shader cache regularly?
No. Clearing it throws away work and guarantees the stutter comes back on the next session. Clear it only when you have a specific reason: after a driver update that changed shader behaviour, or when the stutter is permanent and never settles, which suggests corruption. Routine clearing as maintenance is counterproductive.
Why do console versions not have this problem?
Because consoles are one fixed hardware configuration, so shaders can be compiled ahead of time and shipped with the game. On PC there are thousands of combinations of GPU, driver version and settings, so shaders must be compiled on your machine the first time they are needed. That is the fundamental trade-off, and it is why the problem has grown as games have become more shader-heavy.
Does a faster CPU reduce shader stutter?
It reduces the length of each hitch, because compilation is CPU work and more cores compile in parallel. It does not remove the hitches. A high-core-count CPU turns a noticeable freeze into a brief hiccup, which is a real improvement but not a solution. Cache configuration matters more than CPU for this specific problem.
About the author
PC Hardware & Performance Editor
Marcus has been building, breaking and repairing gaming PCs since 2011, first as a weekend favour for friends and then for eight years as a bench technician at an independent repair shop in Portland, where roughly a third of the job was diagnosing machines that "ran fine yesterday".
Found something wrong? Games patch and fixes go stale. If a step here no longer works, tell us at hello@spyld.com and we will retest it. Read how we test and our editorial policy.