- The shader cache reduces loading and stuttering; if it becomes corrupted, stuttering and FPS drops occur.
- Clean it after major updates or changes drivers restores stability and smooths out the game.
- Increasing to 10 GB improves consistency; it doesn't tend to increase FPS much, but it does reduce stuttering.
When the shader cache becomes corrupted, you'll experience micro-stuttering, extremely long loading times, and frustrating FPS drops. Fortunately, cleaning and rebuilding the cache usually restores smooth gameplay on NVIDIA , AMD, and Intel systems . If you're experiencing those stutters when throwing grenades, entering new areas, or during the initial launch of the game, you're likely dealing with a corrupted or outdated cache, perhaps due to a recent patch.
In this guide, we'll explain in detail what shader caching is, how it works, its actual impact on FPS , how to adjust and clear it on Windows , NVIDIA, and AMD, and real-world examples seen in games like Overwatch, CS2, Doom , and Forza. We'll also cover Steam 's pre-caching and practical recommendations such as using DX12 or borderless windowing when appropriate, along with tips for reducing stuttering without resorting to drastic measures.
What is shader cache and how does it impact FPS?
Shaders are small programs that the GPU runs for tasks like lighting, texturing, and shading. When a game first launches, the graphics card must compile and save these shaders for later use. This process can take anywhere from seconds to several minutes, depending on the game and hardware . Some games display this progress with a bar (like Call of Duty ), while others don't provide any indication.
That "first time" is crucial: the initial compilation can cause poor performance and stuttering, so it's best to let it finish before you start competing. Once completed, the GPU driver uses the cache to speed up loading and smooth frame pacing in subsequent sessions, also reducing entry times and transition times between zones.
Where is all this stored? Some of the information is kept in VRAM, but the bulk of it resides on the hard drive (SSD/HDD) as files managed by the driver. You can adjust the size allocated to this cache, and if you empty it, the system will recompile the shaders the next time you open the game, just as it does after uninstalling it or formatting your PC.
The practical benefit is twofold: shorter loading times and less stuttering during gameplay, especially in titles with heavy textures and complex scenes like Death Stranding or Cyberpunk 2077. Be mindful of VRAM: it doesn't make sense to reserve it all for caching; there needs to be a balance, and more powerful GPUs make better use of this mechanic, but it's not the main reason to upgrade your graphics card.
Regarding storage , the more disk space available for the cache, the more material the controller can reuse, resulting in fewer recompilations. On many systems, the default configuration manages the size dynamically, but if you choose to set it manually, it's not a good idea to dedicate more than 20% of the SSD to the shader cache unless you have a lot of free space.
Cleaning, tuning, and real-life cases on NVIDIA, AMD, and Intel
NVIDIA: Disable, Wipe, and Re-enable for a Clean Rebuild
When the cache is causing problems on NVIDIA systems, a method that works very well is to force a complete rebuild: first, it's disabled, then manually deleted, and after restarting, it's re-enabled . This sequence prevents corrupted remnants from being left behind that the driver might try to reuse.
- Enter in the NVIDIA control panel and open the Global 3D Settings.
- Temporarily disables the option of shader cache and restart the PC.
- Go to Users\YOURUSER\AppData\Local\NVIDIA\ and delete the contents of DXCache y GLCache.
- Reboot again and re-enable the cache; if you have space, you can set it to 10 GB or even 100 GB.
After this cleanup, you'll notice the game runs a bit rougher at first because it's rebuilding the data; it's normal to experience some lag for a couple of matches. Once the process is complete, the experience should become very stable , with fewer frame rate spikes.
It's advisable to repeat this process when a major game update is released (for example, seasonal patches) or after installing a new NVIDIA driver. Changing certain advanced graphics settings can also corrupt the cache; if you notice stuttering returning after tweaking the settings, another cleanup usually fixes it.
In Overwatch, for example, several players have eliminated the chronic stuttering of recent months using this method. Additionally, it has been observed that running in DX12 and borderless windowed mode reduces significant FPS drops compared to fullscreen mode on some systems.
One additional note: some users have noticed unusual spikes with NVIDIA Reflex . As an alternative, try "Ultra Low Latency" from the NVIDIA Control Panel; and if your game includes a "stutter reduction" option, toggling it a couple of times at the start might help smooth things out.
AMD: Reset from Adrenalin and focus on DXCache in some games
On AMD cards, the Adrenalin software allows you to reset the shader cache from Global Graphics; simply go to Global Settings, click Reset, and confirm the cache reset . It's a quick process that, in certain games, eliminates screen tearing when recompiling shaders from scratch.
A striking issue has been observed in CS2 since a patch released on September 14th: on AMD systems, every time the game was restarted, it appeared to be recompiling shaders, resulting in stuttering when detonating grenades, flash effects, or entering new areas. Looking at %localappdata%/AMD/DXCache revealed that CS2 was creating a new cache file almost daily , something that hadn't occurred weeks prior. This situation affects DX11 (not Vulkan) and could be linked to DXNavi optimizations in the 5000/6000/7000 series, according to some observations.
Interestingly, after upgrading the CPU from a Ryzen 5 2600 to a Ryzen 7 5700X3D (without any software modifications), the error stopped occurring in one specific instance, even though the memory was stable with the previous CPU. There has been speculation about the possible role of the L3 cache , although there is no definitive explanation. To troubleshoot, clearing %localappdata%/AMD/DXCache and letting the game rebuild usually alleviates the problem, as does resetting the cache from within Adrenalin.
Intel and Windows: Clean up directly with Space Cleanup
If you use an Intel iGPU or, in general, want to clear the DirectX cache managed by Windows, Disk Cleanup offers a safe shortcut that also works for other brands. The procedure deletes the "DirectX Shader Cache," which the system then regenerates.
- Open Windows Search and run Disk Cleanup.
- Leave only the boxes that interest you checked and locate DirectX Shader Cache.
- Press on “Clean system files” and confirm; when finished, close and that's it.
Keep in mind that when you restart your games, they will take a little longer, and you might notice some temporary stuttering while the cache is being recompiled. After that, everything should run smoothly unless there are other bottlenecks.
Adjust the cache size in NVIDIA (Classic Dashboard and NVIDIA App)
The cache size can be left at "Driver Default" to adjust automatically, or you can manually set it if you want to control its disk usage. In the classic Control Panel, you'll find it under the name "Shader Cache Size ." If you need to free up space, cleaning and optimizing Windows can help.
- Right click on the empty desktop and open the NVIDIA control panel.
- Go into "Control 3D settings".
- Seeks "Shader cache size” and choose the capacity.
The practical recommendation is to leave it dynamic if you're not worried about space; if you prefer to set it, values of 10 GB are usually a good balance. Avoid allocating excessive percentages of your SSD: you don't need to reserve tens of gigabytes to notice improvements.
With the new NVIDIA App , the settings are located under Graphics > Global Settings. The control has the same name and even allows you to set an unlimited size or a minimum of 128 GB; in practice, setting a reasonable limit is more than enough for most users.
Steam and Shader Pre-caching: Small, Useful, and Best Enabled
- In the Steam client, go to Steam > Parameters.
- Open section Downloads and check that Shader pre-caching is active.
It is recommended to keep it on: it does not transform performance on its own, but it reduces waiting times and can help prevent micro-cuts on the first boot after a patch.
Real-life testing: Does 10GB, 100GB, or unlimited work?
A practical test compared various NVIDIA cache capacities, clearing everything and restarting before each measurement. The test was performed on a specific route (Area18 tram line) and the fifth or sixth pass was recorded to minimize variations, with the warning that the server's status could introduce noise into the results.
What did we see? The difference in FPS was only a few frames between the default setting (which was around 4–5 GB in that version), 10 GB, 100 GB, and even unlimited. Where we did notice a difference was in stuttering: with the cache enabled and at a reasonable size, there were fewer micro-stutters . Therefore, setting it to 10 GB is a sensible and robust enough choice for general use.
Case studies: Overwatch, Doom, and Forza
If you've been experiencing stuttering in Overwatch for months, clearing and rebuilding the cache is usually a lifesaver. The typical procedure: disable the cache in the NVIDIA Control Panel, restart, clear DXCache/GLCache , restart, and then re-enable it. The first few matches might have some compilation stuttering, but the experience improves significantly after a short time. After major game patches or new drivers, it's a good idea to repeat this process, and if you've tweaked advanced settings, be prepared to do it again if the stuttering returns.
There are also direct reports of this happening in other titles: one player who was experiencing inexplicable frame drops recovered peak frame rates of around 130 FPS in Doom and around 105 FPS in Forza: Apex , both at 1440p and with maximum settings, after purging the cache. It doesn't always happen, but when the cache is corrupted, the difference can be significant.
As a bonus, some systems experience fewer frame rate drops in DX12 and borderless windowed mode than in fullscreen; it's not a universal rule, but if your game allows this option, try it . And if NVIDIA Reflex is causing spikes, switching to "ultra-low latency" from the Control Panel can stabilize the situation.
When to clean and good practices
- After season updates or large game patches, especially if you notice rebuilds when entering maps or seeing new effects.
- After install drivers from NVIDIA/AMD: Some drivers change the way they manage the cache.
- If you have touched advanced graphics settings and suddenly the stutter returned, a quick clean usually solves it.
- When you encounter weird behavior (e.g. CS2 on DX11 creating daily caches on AMD), flush DXCache and rebooting helps diagnose.
In addition to the above, keep in mind that the first boot after clearing the cache may be rougher: recompilation is unavoidable and not a sign of a persistent problem. Avoid running serious benchmarks immediately after clearing the cache and let the game finish its rebuild process.
How to adjust without breaking the experience
Leave the cache size at "driver default" unless you have a reason to limit or increase it; if you decide to set it, 10 GB works well on most systems, without needing to go to 100 GB or unlimited. Keep Steam's Shader pre-caching enabled , and if you switch APIs (DX11/DX12/Vulkan), accept that the game may compile different material and take a little longer on that first session.
When troubleshooting stuttering on NVIDIA, disabling, clearing DXCache/GLCache, and then re-enabling it provides a thorough cleanup. On AMD, use Adrenalin to reset the cache and monitor the %localappdata%/AMD/DXCache folder for any unusual regenerations. If you're using Windows for the cleanup, be sure to select "DirectX Shader Cache" in Disk Cleanup.
If you play competitively and every millisecond matters, it sometimes pays to prioritize DX12 with borderless windowing, adjust the render queue (ultra-low latency), and let the cache do its job. Once stabilized, extreme FPS drops are often mitigated, and pacing becomes noticeably smoother.
A well-maintained shader cache isn't a magic potion for a massive FPS boost, but it is a pillar of stability: it speeds up loading times, prevents unnecessary recompilation, and reduces micro-stuttering. Clean it up after major updates, use the cache size wisely (10 GB is usually enough), take advantage of Steam's pre-caching, and use NVIDIA/AMD resets when necessary; with these habits, the game should regain its lost fluidity and get rid of that annoying stuttering.
Passionate writer about the world of bytes and technology in general. I love sharing my knowledge through writing, and that's what I'll do on this blog, show you all the most interesting things about gadgets, software, hardware, tech trends, and more. My goal is to help you navigate the digital world in a simple and entertaining way.