- 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 is corrupted, it can cause micro-stuttering, long loading times, and FPS drops that are frustrating; luckily, clear and rebuild the cache It usually restores fluency in NVIDIA, AMD and Intel. If you experience those jerks when throwing grenades, entering new areas or at the first Boot of the game, you are probably looking at a bad or outdated cache after a patch.
In this guide we are going to tell you in detail what the shader cache is, how it works, what real impact it has on FPS, how to adjust and clean it in Windows, NVIDIA and AMD, and what real cases have been seen in games like Overwatch, CS2, Doom or Forza. In addition, we will review the pre-caching of Steam and practical recommendations such as using DX12 or the borderless window when appropriate, along with Fine tips to reduce stuttering without black magic.
What is shader cache and how does it impact FPS?
Shaders are small programs that the GPU runs for tasks such as lighting, texturing, and shading; on first boot of a game, the graphics card should compile and save them to reuse them. This process can take from seconds to several minutes depending on the title and the hardware, and some games show it with a progress bar (like Call of Duty), while others give no clue.
That “first time” is crucial: the initial compilation can cause slow performance and stuttering, so it’s a good idea to let it finish before racing. After it’s completed, the GPU driver pulls the cache to speed up loading and smooth out frame pacing in the following sessions, also reducing There from entry to game and transition between zones.
Where is all this stored? Some of the information is stored in VRAM, but the bulk lives on the disk (SSD/HDD) as files managed by the driver. You can adjust the size assigned to this cache, and if you empty it, the system will recompile the shaders the next time you open the game, exactly the same as after uninstalling it or forma tear the PC.
The practical benefit is twofold: on the one hand, shorter loading times and, on the other hand, less stuttering during the game, especially in titles with heavy textures and complex scenes such as Death Stranding or Cyberpunk 2077. Be careful with VRAM: it doesn't make sense to reserve it entirely for the cache; there must be a balance, and the more capable GPUs take better advantage this mechanic, but it is not the main reason to change cards.
Regarding storageThe more disk cache space available, the more material the controller can reuse, resulting in fewer recompiles. On many computers, the default configuration manages the size dynamically, although if you choose to set it manually, It is not a good idea to dedicate more than 20% of the SSD to the shader cache, unless you have a lot of free headroom.
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 giving problems on NVIDIA, a method that works very well is to force a complete rebuild: first disable it, then delete it manually, and after reboot, is activated againThis sequence prevents corrupted remnants from being left behind for the controller to 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 that the game is a bit rougher at first because it's rebuilding the material; it's normal to experience some stuttering for a couple of games. Once the process is complete, the experience should be become very stable, with fewer sharp peaks.
It's a good idea to repeat this step after a major game update (e.g., seasonal patches) or after installing a new NVIDIA driver. Changing certain advanced graphics settings can also break the cache; if you notice the stuttering returning when you tinker with the settings, another cleaning usually fixes it.
In Overwatch, for example, several players have eliminated the chronic stutter of recent months with this method. Furthermore, it has been observed that going in DX12 and in borderless window mode Reduces severe FPS drops when in full screen mode on some devices.
An additional note: there are those who have noticed strange spikes with NVIDIA SLRAlternatively, 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 startup may help settle everything.
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 the Global Graphics menu; just go to the global settings, press reset and confirm the cache resetIt's a quick process that, in certain titles, eliminates micro-chopping by recompiling shaders from scratch.
A notable case has been seen in CS2 since a patch released on 9/14: on AMD machines, every time the game was restarted it seemed to recompile shaders, with hitches when detonating grenades, flash effects, or entering new areas. Looking at %localappdata%/AMD/DXCache, it was observed that CS2 was creating a new cache file almost daily, something that hadn't happened weeks before. This situation affects DX11 (not Vulkan) and could be linked to DXNavi optimizations on 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 touching software) the error stopped reproducing in one specific case, despite the memory being stable with the previous CPU. There has been speculation about the possible role of the L3 cache, although there is no definitive explanation. To debug, clear %localappdata%/AMD/DXCache and letting the game rebuild usually alleviates the problem, as does reset from Adrenalin.
Intel and Windows: Clean up directly with Space Cleanup
If you are using Intel iGPU or generally want to delete the DirectX cache managed by Windows, the Disk Cleanup offers a safe shortcut that also works for other brands. The procedure erases the “DirectX Shader Cache” which the system generates again later.
- 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.
Please note that when you restart your games, they will take a little longer and you may notice some temporary stutter while the cache is being recompiled. Then, everything should run smoothly if there are no other bottlenecks.
Adjust the cache size in NVIDIA (Classic Dashboard and NVIDIA App)
The cache capacity can be left at "Controller Default" to adapt automatically, or set manually 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, clean and optimize 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 are not worried about space; if you prefer to fix it, values of 10 GB They're usually a good balance. Avoid allocating excessive percentages of your SSD: you don't need to allocate tens and tens of gigabytes to notice improvements.
With the new NVIDIA App, the settings are located in Graphics > Global Settings. The control has the same name and even allows you to set unlimited size or a minimum of 128 GB; in practice, set a reasonable limit. It is more than enough for the majority.
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 by itself, but it reduces waiting and can help avoid microcuts on the first boot after a patch.
Real-life testing: Does 10GB, 100GB, or unlimited work?
A practical test compared various cache capacities on NVIDIA, clearing everything and rebooting before each measurement. The test was conducted on a specific route (Area18 tram line) and the fifth or sixth pass was recorded to minimize variations, with a warning that the server status would be displayed. could introduce noise in the results.
What was seen? The difference in FPS was just a few frames between the default settings (which were around 4–5 GB in that version), 10 GB, 100 GB, and even unlimited. Where something was noticeable was in the stuttering: with the cache active and at a reasonable size, there were fewer micro-cuts. Therefore, setting 10 GB is a sensible choice and robust enough for general use.
Case studies: Overwatch, Doom, and Forza
If you've been experiencing issues in Overwatch for months, clearing and rebuilding the cache is usually a surefire solution. The typical pattern: disable the cache in the NVIDIA Dashboard, restart, clear DXCache/GLCache, restart, and reactivate it; the first few games may experience some compilation issues, but after a while, things improve significantly. After major game patches or new drivers, it's a good idea to repeat the ritual, and if you tweak advanced settings, be prepared to do it again if the stutter returns.
There are also direct experiences in other titles: a player who suffered unexplained crashes recovered, after purging the cache, peaks of around 130 FPS in Doom and about 105 FPS in Forza: Apex, both at 1440p and maximum settings. It doesn't always happen, but when the cache is corrupted, the jump can be noticeable.
On the plus side, some machines experience less severe drops in DX12 and borderless windowing than in fullscreen; it's not a universal rule, but if your title allows for a choice, test itAnd if NVIDIA Reflex is giving you spikes, toggling it to “ultra low latency” from the Dashboard 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 all of the above, remember that the first boot after clearing the cache may be rougher: recompilation is inevitable and not a symptom of a persistent problem. Avoid doing serious benchmarks right after emptying it y let the game finish its process of construction.
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 choose to set it, 10 GB works fine on most computers, without needing to go to 100 GB or unlimited. Keep the Steam Pre-caching Shader and if you change APIs (DX11/DX12/Vulkan), accept that the game may compile different material and take a little longer in that first session.
When fixing stuttering on NVIDIA, the disable, clear, and re-enable DXCache/GLCache method provides a thorough cleanup. On AMD, rely on Adrenaline to reset and check the %localappdata%/AMD/DXCache folder if you notice any unusual rebuilds. If you're using Windows to clean up, be sure to check "DirectX Shader Cache" in Space Cleanup.
If you're playing competitively and every millisecond matters, it's sometimes worth prioritizing DX12 with borderless windowing, adjusting the render queue (ultra low latency), and letting the cache do its work. Once stabilized, extreme FPS drops are often mitigated and pacing is smoother. noticeably more uniform.
A well-maintained shader cache isn't a magic potion for a crazy FPS boost, but it is a key to stability: it speeds up loading, prevents unnecessary recompilation, and reduces micro-stuttering. It cleans up after major updates, uses the size wisely (10 GB is usually enough), relies on Steam's pre-caching, and resorts to NVIDIA/AMD resets when appropriate; with these habits, the game will usually recover. the lost fluency 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.