Yes, you can safely clear NVIDIA’s shader cache. On Windows, NVIDIA’s supported method is to turn Shader Cache Size off in NVIDIA App, reboot, delete the contents of the three NVIDIA cache folders, restore Shader Cache to Driver Default, and restart again. The next game or application launch recreates the files automatically. On Linux, the documented procedure applies to the NVIDIA OpenGL cache and uses different, environment-dependent paths.
What the NVIDIA shader cache does
Games and graphics applications compile shader programs into a form the GPU driver can use. NVIDIA stores those compiled results so a later run of the same game does not have to compile every shader again. Keeping the compiled data normally reduces repeated compilation work and can make subsequent launches or gameplay smoother.
As an Amazon Associate I earn from qualifying purchases.
A cache can become stale or damaged after a driver update, an interrupted installation, a game update, or an unusual crash. NVIDIA Support says damaged shader-cache files may contribute to launch crashes, lower performance, or visual artifacts. Clearing the cache removes the reusable compiled data; it does not uninstall the driver, remove a game, or erase save files.
PC Slower Than It Used to Be?
A free scan shows the junk files, broken settings and background clutter dragging Windows down - then fixes them in one click.Free scan · Windows 10 & 11Outdated Drivers Are Slowing You Down
One free scan finds every outdated or missing driver and matches the right update for your exact hardware.Free scan · exact hardware matchBecause the cache is disposable, the safe objective is not to preserve the existing files. It is to stop the driver using the cache, remove the contents, then let the driver create clean files under its normal setting.
#1 Best Overall
- AI Performance: 767 AI TOPS
- OC mode: 2632 MHz (OC mode)/ 2602 MHz (Default mode)
- Powered by the NVIDIA Blackwell architecture and DLSS 4
- Axial-tech fan design features a smaller fan hub that facilitates longer blades and a barrier ring that increases downward air pressure
- A 2.5-slot design maximizes compatibility and cooling efficiency for superior performance in small chassis
Windows: NVIDIA’s complete supported procedure
Use this sequence on a Windows PC managed through NVIDIA App. The reboot between disabling the setting and deleting files is part of NVIDIA’s instructions, not an optional cleanup step.
1. Turn Shader Cache Size off
- Open NVIDIA App.
- Select Graphics.
- Open Global Settings.
- Find Shader Cache Size, set it to Off, and select Apply.
Disabling the setting first helps ensure that the driver is not actively maintaining the cache while you remove its files. If the control is unavailable or named differently, use the current NVIDIA App interface rather than guessing at a registry value; NVIDIA’s documented sequence depends on this setting being applied through the app.
2. Reboot before deleting anything
Restart Windows after applying the Off setting. Do not skip directly to File Explorer. A restart closes applications and driver processes that may still have cache files open. It also gives Windows a clean opportunity to load the changed cache policy before you remove the old data.
What’s actually slowing this PC down?
Pick the symptom - the matching free tool is one click away.
3. Delete the contents of NVIDIA’s Windows cache folders
In File Explorer, enter each path in the address bar. Delete the files and subfolders inside the named directories; do not delete unrelated folders under AppData.
- Open
%USERPROFILE%AppDataLocalNVIDIAand clear the contents ofDXCache. - From the same NVIDIA directory, clear the contents of
GLCache. - Open
%USERPROFILE%AppDataLocalNVIDIA CorporationNV_Cacheand clear its contents.
Windows may report that a file is in use or ask for administrator confirmation. If a file cannot be removed, close games, launchers, overlays, monitoring tools, and other graphics applications, then try again. The supported locations are the three folders above; do not widen the cleanup to every directory containing the word “cache.”
If a folder contains several levels of files, select the contents rather than the parent directory itself. Leaving the empty parent folder in place is normal; the driver can reuse it. The goal is to remove generated cache data, not to alter permissions or rename NVIDIA directories.
4. Restore the normal cache setting
- Open NVIDIA App again and return to Graphics > Global Settings.
- Set Shader Cache Size to Driver Default.
- Select Apply.
NVIDIA’s Support page updated May 25, 2026 reports that Driver Default is currently 16 GB. That value is a date-specific configuration value and can change with a later driver or application release, so use the live Driver Default option rather than entering a fixed number yourself.
5. Restart a second time
Restart Windows once more after restoring Driver Default. This completes NVIDIA’s sequence and ensures the normal cache policy is active before you test the affected game. Running with the setting left Off would prevent the normal persistent cache from providing its intended benefit.
6. Launch the game or application and allow the rebuild
Start the application that was crashing or showing artifacts. NVIDIA says cache files are recreated automatically the next time an application or game launches. You do not need to create folders manually or download replacement shader files. The application may create data gradually as new menus, levels, effects, or locations are rendered, so an initially sparse folder is not evidence that the process failed.
Rank #2
- Powered by the NVIDIA Blackwell architecture and DLSS 4
- Powered by GeForce RTX 5070 Ti
- Integrated with 16GB GDDR7 256bit memory interface
- PCIe 5.0
- WINDFORCE cooling system
What to expect on the first launch after clearing
The first run can take longer and may stutter. Clearing the cache removed compiled shaders that would otherwise have been reused, so the driver and game must compile them again. NVIDIA also warns that the first gameplay run after a driver installation may stutter for the same reason. Temporary compilation stutter is therefore different from a persistent performance fault.
Allow the game to reach its menus and, if appropriate, play through the areas that previously triggered the problem. Subsequent launches should be able to reuse the newly generated files. If the same crash or artifact returns after the cache has been rebuilt, the cache was not the only cause and you should continue with application, driver, or system troubleshooting rather than repeatedly deleting the cache.
Free tools Windows power users keep installed
One-click scans. No signup required.
Do not judge the result from the first few seconds alone. A game that compiles shaders while you move through a new area can hitch even though the cleanup worked correctly. Compare later sessions, using the same graphics settings and a similar scene, before deciding whether performance improved.
Choosing a cache size after the rebuild
NVIDIA’s Control Panel guidance says games vary greatly in how much shader cache they need. Higher-end games can require several hundred megabytes, and a limit that is too small can evict shaders that are still being used. Those evictions can contribute to gameplay stutter because the shaders have to be compiled again.
- Driver Default: the setting NVIDIA currently recommends as the automatic choice. The cited Support page listed 16 GB on May 25, 2026, but that number is not permanent.
- A deliberately small limit: saves disk space but increases the chance that active shaders are evicted and rebuilt.
- A larger limit: gives games more room to retain compiled shaders, subject to the storage available on the drive.
For most users, restore Driver Default after cleanup and leave it there. Consider a manual limit only when you have a specific storage constraint or a documented reason to manage cache growth. Do not confuse a cache limit with a guaranteed amount of disk usage: it is a ceiling for the shader cache, not an instruction to allocate that entire amount immediately.
Changing the limit is not the same as clearing the cache. A larger ceiling does not repair damaged files already on disk, while clearing files does not require choosing a permanent custom ceiling. Treat cleanup and long-term capacity management as separate decisions.
Recommended Free Tools
Is deleting DXCache and GLCache safe?
Yes, deleting the contents of the NVIDIA DXCache, GLCache, and NV_Cache directories is the cleanup NVIDIA specifies for Windows shader-cache problems. These files are generated data. The driver and applications can recreate them after the next launch.
Safety depends on deleting only the intended contents. Do not remove the entire NVIDIA driver installation, random folders in AppData, game save directories, or application configuration files. If you are unsure whether a directory belongs to this procedure, leave it alone; the three paths in NVIDIA’s sequence are sufficient for the supported Windows cleanup.
Clearing these folders does not roll back a driver, reset NVIDIA App preferences, or repair a damaged executable. It is a targeted reset of compiled graphics data. That limited scope is why it is useful as an early troubleshooting step, but also why a different fault can remain after the rebuild.
Rank #3
- Powered by the NVIDIA Blackwell architecture and DLSS 4. System Requirements: Minimum 850W PSU with 16-pin 12V-2x6 (12VHPWR) connector required. Verify before purchasing.
- Military-grade components deliver rock-solid power and longer lifespan for ultimate durability. Compatibility: 348mm (13.7") length, 3.6 slots, 4.3 lbs. Confirm case clearance and slot spacing. GPU bracket included.
- Protective PCB coating helps protect against short circuits caused by moisture, dust, or debris
- 3.6-slot design with massive fin array optimized for airflow from three Axial-tech fans
- Phase-change GPU thermal pad helps ensure optimal thermal performance and longevity, outlasting traditional thermal paste for graphics cards under heavy loads
Windows troubleshooting if the folders or files behave differently
The folder is not visible
Use the environment-variable paths exactly as written in File Explorer: %USERPROFILE%AppDataLocalNVIDIA and %USERPROFILE%AppDataLocalNVIDIA CorporationNV_Cache. The AppData directory is commonly hidden in normal folder browsing, but entering the path directly does not require you to hunt for it manually. If one of the named cache directories does not exist, do not create an empty replacement just to continue; clear the locations that are present and proceed with the rest of the sequence.
Windows says a file is being used
Confirm that the game, launcher, browser windows using hardware acceleration, recording software, overlays, and GPU-monitoring utilities are closed. Rebooting after setting Shader Cache Size to Off is specifically intended to release such handles. If a file remains locked after the restart, reboot once more and retry before considering more invasive steps.
Do not force deletion by taking ownership of unrelated directories or changing broad security permissions. The supported workflow should not require those changes. A locked file usually means a graphics process is still running or Windows has not completed the restart sequence.
The game still crashes immediately
Verify that you completed both restarts and restored Driver Default. Then test the game again so it has an opportunity to create a fresh cache. A repeat crash after a clean rebuild indicates that another component may be involved, such as the game installation, a driver issue, or an application-specific cache. The NVIDIA shader-cache procedure does not repair corrupted game files or alter game settings.
Stutter continues for several sessions
Some first-run compilation stutter is expected, but persistent stutter is not proof that the cache was cleared incorrectly. Check whether the cache-size limit is unusually small; NVIDIA notes that frequent eviction can force repeated compilation. If the setting is already Driver Default and the problem persists, investigate the game’s own shader-compilation behavior and other graphics settings rather than repeatedly deleting the NVIDIA cache.
The cache seems to return immediately
That is normally expected. The driver and application are designed to regenerate files after launch, and the folder can begin repopulating as soon as graphics work occurs. Successful cleanup means old generated data was removed and a new cache was created, not that the directories remain permanently empty.
Linux: the documented OpenGL cache procedure
Linux uses a different cache layout from Windows. NVIDIA’s Linux driver README, version 550.144.03, documents a persistent shader disk cache for the OpenGL driver. Its current default location depends on the XDG_CACHE_HOME environment variable:
| Condition | Documented OpenGL cache path |
|---|---|
XDG_CACHE_HOME is set |
$XDG_CACHE_HOME/nvidia/GLCache/ |
XDG_CACHE_HOME is not set |
$HOME/.cache/nvidia/GLCache/ |
| Legacy driver location | .nv/GLCache/ under the user’s home directory |
The README states that it is safe to remove a legacy .nv/GLCache/ directory. After removal, the driver populates a fresh cache in the newer location described above. Cached binaries are specific to a driver version, which is why an old cache may no longer be useful after a driver change.
Linux cleanup steps
- Close OpenGL applications and games.
- Check whether
XDG_CACHE_HOMEis set in the environment used to launch the application. - Identify the corresponding
nvidia/GLCache/directory, or the legacy.nv/GLCache/directory if you are following the README’s legacy-location guidance. - Remove the cache contents, or remove the legacy
.nv/GLCache/directory as described by NVIDIA. - Launch the OpenGL application again and allow the driver to regenerate the cache.
Do not assume that the Windows paths apply to Linux. The cited Linux documentation is specifically about NVIDIA’s OpenGL driver cache; it does not establish one universal deletion command for every Vulkan application, game, compatibility layer, or desktop environment.
Quick wins for a faster PC:
Clear out junk files and repair common Windows errorsFree Scan →Scan for outdated or missing drivers - takes under a minuteDriver Scan →Rank #4
- Powered by the NVIDIA Blackwell architecture and DLSS 4
- Powered by GeForce RTX 5060
- Integrated with 8GB GDDR7 128bit memory interface
- PCIe 5.0
- WINDFORCE cooling system
Environment variables can differ between a desktop launcher, a terminal, and a compatibility tool. Check the environment in the context that actually starts the affected application. Removing a legacy directory is safe according to NVIDIA’s README, but it does not imply that every similarly named directory belongs to the NVIDIA OpenGL cache.
Do not mix shader caches with CUDA or application caches
Graphics shader caches are not the only caches NVIDIA software can create. CUDA’s separate ComputeCache is listed at %APPDATA%NVIDIAComputeCache on Windows and ~/.nv/ComputeCache on Linux. That cache serves compute workloads, not the Windows graphics folders in NVIDIA Support’s shader-cache procedure.
Games, launchers, Vulkan implementations, and compatibility layers may also maintain their own shader or pipeline caches. The Windows procedure does not authorize deleting those locations, and the Linux OpenGL README does not claim that every such cache belongs to GLCache. Leave unrelated caches in place unless the application’s own documentation gives you a separate reason to clear them.
In particular, clearing the NVIDIA graphics folders is not a substitute for following a game’s instructions for its DirectX, Vulkan, or translation-layer cache. Those caches can have different rebuild behavior and may be shared by more than one installation.
Do these 3 things before closing this tab:
1Fix the driver behind crashes, sound loss and screen glitches2Repair Windows errors before they cause bigger problems3Scan for outdated or missing drivers - takes under a minuteWindows and Linux guidance compared
| Question | Windows | Linux |
|---|---|---|
| Primary documentation | NVIDIA Support’s NVIDIA App workflow | NVIDIA Linux driver README 550.144.03 |
| Scope | NVIDIA shader-cache folders used by the Windows driver workflow | NVIDIA OpenGL persistent shader disk cache |
| How cleanup is initiated | Turn Shader Cache Size Off, apply, reboot, delete contents, restore Driver Default, restart | Remove the documented cache or legacy directory after closing applications |
| Location behavior | Three documented folders under the user profile | Depends on XDG_CACHE_HOME; older drivers used .nv/GLCache/ |
| Rebuild | Automatic at the next application or game launch | Driver repopulates a fresh cache when an OpenGL application runs |
There is no single deletion procedure that covers every operating system, graphics API, and application. Match the cleanup to the platform and cache type you are actually troubleshooting.
When clearing the cache is the right fix
- A game began crashing on launch after a driver or game update.
- Visual artifacts appeared while other applications work normally.
- Performance became unusually poor after a driver change and the symptoms fit damaged cached shader data.
- You need to discard driver-version-specific compiled binaries before testing a clean rebuild.
Clearing is less likely to help when the problem is caused by overheating, unstable overclocking, missing game files, a defective GPU, insufficient system memory, or a bug in the application itself. The procedure is a low-risk diagnostic and repair step, not a universal graphics-performance reset.
Independent reader supportYour contribution helps us test, update, and keep practical guides available for everyone.Questions readers commonly ask
Will clearing the cache delete my game saves?
No. The documented folders contain generated NVIDIA cache data, not game saves. The procedure does not uninstall games or remove their configuration, although you should still delete only the contents of the three named directories.
Do I have to clear all three Windows folders?
NVIDIA’s supported sequence names DXCache, GLCache, and NV_Cache. Clear the contents of each location that exists, rather than substituting a different folder because its name also contains “cache.”
The Tool Desk
Outbyte PC Repair FREERepair Windows errors before they cause bigger problemsFix Now →Outbyte Driver Updater FREEScan for outdated or missing drivers - takes under a minuteDriver Scan →Can I skip the reboot after selecting Off?
You should not. NVIDIA includes that reboot before deletion so driver and application processes release cache files. Skipping it can leave files in use and means you have not followed the complete supported sequence.
Best Value
- Powered by the NVIDIA Blackwell architecture and DLSS 4 OC mode: 2640MHz/Default mode: 2610MHz (Boost Clock)
- Military-grade components deliver rock-solid power and longer lifespan for ultimate durability
- Protective PCB coating helps protect against short circuits caused by moisture, dust, or debris
- 3.125-slot design with massive fin array optimized for airflow from three Axial-tech fans
- Phase-change GPU thermal pad helps ensure optimal thermal performance and longevity, outlasting traditional thermal paste for graphics cards under heavy loads
How do I force NVIDIA shaders to rebuild?
On Windows, follow the full sequence: set Shader Cache Size to Off, apply it, reboot, clear the three documented folders, restore Driver Default, apply it, and restart again. Launching the affected game then causes files to be recreated automatically. On Linux, remove the documented OpenGL cache location and launch the OpenGL application again.
Is a first-run hitch proof that the cleanup failed?
No. Compilation after a cache reset can cause a slower launch or temporary gameplay stutter. Judge the result after the application has had time to compile the areas and effects it uses, and compare later sessions rather than only the first run.
Should I set the cache to 16 GB manually?
No. NVIDIA’s May 25, 2026 Support page reported 16 GB as the then-current Driver Default. Select Driver Default in the current NVIDIA App instead of hard-coding a date-specific value, because the default can change.
Why does Linux not show the Windows folders?
They are Windows locations. NVIDIA’s Linux OpenGL cache uses $XDG_CACHE_HOME/nvidia/GLCache/ when that variable is set, or $HOME/.cache/nvidia/GLCache/ otherwise. Older drivers may have used .nv/GLCache/.
Can I delete CUDA ComputeCache while doing this?
It is a separate compute cache, not part of NVIDIA’s graphics shader-cache procedure. Leave %APPDATA%NVIDIAComputeCache on Windows and ~/.nv/ComputeCache on Linux alone unless you are troubleshooting a separate CUDA issue.
Safe checklist
- Use the NVIDIA App path Graphics > Global Settings > Shader Cache Size on Windows.
- Apply Off and reboot before deleting files.
- Clear only
DXCache,GLCache, andNV_Cachecontents in the documented locations. - Restore Driver Default, apply it, and restart again.
- Expect a slower or stuttery first run while shaders compile again.
- On Linux, confirm the OpenGL cache path from
XDG_CACHE_HOMEand the driver documentation. - Keep CUDA
ComputeCacheand application-specific caches separate from this procedure.
Frequently Asked Questions
Is it safe to delete NVIDIA DXCache and GLCache?
Yes. NVIDIA identifies the contents of DXCache, GLCache, and NV_Cache as removable generated data for this Windows cleanup. Delete only the contents of the documented folders, not unrelated AppData directories.
How do I force NVIDIA shaders to rebuild on Windows?
In NVIDIA App, set Graphics > Global Settings > Shader Cache Size to Off, apply and reboot, clear the three NVIDIA cache locations, restore Driver Default, apply and restart again. Launching the game then recreates the cache automatically.
What’s actually slowing this PC down?
Pick the symptom - the matching free tool is one click away.
Why does my game stutter after the cache reset?
The first run must compile shaders that were deleted. NVIDIA warns that this can cause temporary stutter, just as it can after a driver installation. Later runs can reuse the rebuilt files.
What is NVIDIA’s current Driver Default cache size?
NVIDIA’s Support page updated May 25, 2026 listed Driver Default as 16 GB at that time. The value can change, so select the live Driver Default option instead of entering a fixed number.
Where is the NVIDIA shader cache on Linux?
For the documented OpenGL driver cache, use $XDG_CACHE_HOME/nvidia/GLCache/ when XDG_CACHE_HOME is set, or $HOME/.cache/nvidia/GLCache/ otherwise. NVIDIA also documents safe removal of the legacy .nv/GLCache/ directory.
Should I delete NVIDIA ComputeCache too?
No. CUDA ComputeCache is separate from the graphics shader cache: %APPDATA%NVIDIAComputeCache on Windows and ~/.nv/ComputeCache on Linux. Do not remove it for a graphics shader-cache reset.
Do these 3 things before closing this tab:
1Fix the driver behind crashes, sound loss and screen glitches2Clear out junk files and repair common Windows errors3Scan for outdated or missing drivers - takes under a minuteThe Bottom Line
On Windows, use NVIDIA’s exact sequence: turn Shader Cache Size Off, apply it, reboot, clear DXCache, GLCache, and NV_Cache, restore Driver Default, apply it, and restart. The next launch rebuilds the files automatically, with possible temporary compilation stutter. On Linux, follow the NVIDIA OpenGL cache paths controlled by XDG_CACHE_HOME and keep CUDA and application-specific caches separate.
Quick Recap
Product prices and availability are accurate as of the date/time indicated and are subject to change. Any price and availability information displayed on Amazon at the time of purchase will apply.
