Quick answer

Leave the shader cache at Driver Default unless you swap between a large library of demanding games and have disk space to spare. A bigger cache only helps repeat launches of games you already play; it does not speed up the first run. Clear the cache when corruption causes crashes or artifacts.

Contents

At a glance

Class
Gaming

Provenance

  • Nov 16, 2026Published

TL;DR · NVIDIA Shader Cache Size

  • Default action: leave it where it is. You are trading disk space against repeated shader compilation, not buying frame rate.
  • Raise it only if you rotate through a large library of demanding games and you can afford the space. NVIDIA's own guidance is a size big enough for your normal games and small enough not to crowd your drive.
  • Do not leave it Disabled. That is a step in the cache-clearing procedure, not a permanent setting.
  • Clear the cache when games crash on launch, artifacts appear, or performance drops after a corrupted cache. NVIDIA documents that exact failure mode.
  • Where it lives: NVIDIA App → Graphics → Global Settings → Shader Cache Size, or the older NVIDIA Control Panel under Manage 3D settings.

The Shader Cache Size control is the only entry in NVIDIA’s 3D settings list that people change for a problem it does not solve. It does not make a game render faster. It decides how much disk space the driver may spend keeping compiled shaders around, so that a game you launched last week does not have to compile them all again.

That makes the decision narrower than the forum threads suggest. Leave it on the default unless you have a specific reason to move it, raise it if you own a large library of demanding titles and have the space, and touch it at all only to clear a damaged cache. The rest of this page is the reasoning and the exact paths.

What a shader cache actually holds

A shader is a small program the GPU runs, and the driver has to compile it for your specific card and driver version before the game can use it. NVIDIA’s Control Panel reference describes the problem in one line: shader compiles “are normally performed each time a game runs and are a common cause of game-play stuttering” (NVIDIA Control Panel Help).

The cache exists to skip that repeat work. The same reference says the cache “stores these compiled shaders so that subsequent runs of the same game do not need to perform the shader compilation.” That is the whole promise: the second launch is cheaper than the first.

Two things follow, and they matter more than any benchmark.

First, the cache helps the second run, not the first. Nothing in NVIDIA’s description says the cache accelerates the initial compile. If your complaint is “this game hitches every time I start it, every session,” a bigger cache is not the fix, because the cache is not what you are waiting on.

Second, the cache is a disk cost. Compiled GPU code is not small, and NVIDIA’s guidelines note that higher-end games “may require several hundred megabytes” each. Multiply that across a library and you understand why the setting has a ceiling at all.

The option list, as NVIDIA documents it

The Control Panel reference lists the values as: “Disabled, Unlimited, or one of the following values: 128 MB, 256 MB, 512 MB, 1 GB, 5 GB, 10 GB, 100 GB.” It also notes the control was introduced in Release 495. It does not state a default size anywhere on that page, so I am not going to quote one from that source.

The NVIDIA App exposes a different label. NVIDIA’s support article on deleting shader cache files tells you to set the control back to “Driver Default (currently 16GB)” when you are finished clearing it. That sentence is the only place either document names a numeric default, and it describes the NVIDIA App’s entry rather than the Control Panel list.

OptionWhat it means in practice
Disabled / OffNo persistent shader cache. Every launch recompiles. This is the clearing state, not a tuning state.
Driver DefaultNVIDIA’s chosen size; the support article names it as currently 16 GB. The sane starting point.
128 MB to 1 GBSmall ceilings. Fine for a couple of old titles, tight for anything modern.
5 GB and 10 GBRoom for a working library of demanding games without unbounded growth.
100 GBA ceiling large enough that you will hit free-space limits before you hit it.
UnlimitedNo ceiling of its own. The constraint becomes your free disk space.

The mechanical consequence of a small ceiling is the interesting part, and NVIDIA spells it out: “On approaching the size limit, the driver will remove older shaders from the cache to make space for newer shaders; setting a size limit too small may cause the driver to remove shaders you still make use of and cause game play stutters.”

Read that twice, because it inverts the usual advice. A too-small cache does not merely fail to help. It can actively churn, evicting the shaders for the game you play nightly in favour of the one you installed last weekend.

Why stutter spikes after a purge or a driver update

The single most useful sentence in NVIDIA’s documentation is the note attached to this setting: “Installing a new driver will delete the cache; you may experience game play stutters the first time you run a game after installing a driver.”

That explains a whole category of support thread. You update your driver, launch your main game, and it hitches for the first minutes. Nothing is broken. The cache that was saving you that work was just deleted, and you are paying the first-run compilation cost again.

It also means the stutter is self-limiting. Play the game once and the cache rebuilds. If the hitch persists across many launches with no driver change, the cache is not your explanation and you should stop looking at this setting.

The same logic covers the manual case. NVIDIA’s article describes what a damaged cache actually does: “If the NVIDIA Shader Cache files are damaged, it may cause applications or games to crash on launch, exhibit lower performance, or display visual artifacts.” Note the word damaged. Corrupt compiled code being replayed is a different failure from a cache that is merely small, and only one of those is fixed by deleting it.

Why Unlimited is not free

Unlimited sounds like the option that removes a problem, and it is the option most likely to be recommended in a comment thread. It is not free, and the cost is not subtle.

The disk cost grows with your library and your settings, because every game you launch deposits its compiled output. NVIDIA’s own guideline for this control is a limit “large enough to cover the set of games you normally use, but not too large that it exceeds your available hard drive disk space.” Unlimited deletes the first half of that sentence and keeps the second, leaving your free space as the only thing standing between the driver and a full drive.

There is a second cost that people miss. The cache only pays back while its contents are valid, and a driver install resets that clock no matter how much room you allocated. Unlimited does not exempt you from the invalidation; it just means more stored shaders are discarded when the wipe happens.

And a third: nothing about a larger ceiling speeds up the game you are about to play for the first time. That is the first-run cost again, and it is unaffected by how much room you have allocated.

When to clear the cache

Clear it when the symptoms are cache-shaped: a game crashes on launch, artifacts appear, or performance drops in a way that started recently and follows a driver change. NVIDIA’s article lists exactly those outcomes as the damaged-cache signature.

NVIDIA’s own procedure is a five-step sequence, and the order matters:

  1. Open the NVIDIA App, select Graphics in the left column, then Global Settings at the top.
  2. Search for and select Shader Cache Size, choose Off under Cache Size, and click Apply.
  3. Reboot the PC.
  4. Delete the cache files. Open the Run dialog (Win + R) and enter %USERPROFILE%\AppData\Local, open the NVIDIA directory, and delete all contents from both the DXCache and GLCache folders. Then go back to the Local folder, open NVIDIA Corporation, and delete the contents of NV_Cache.
  5. Reopen the NVIDIA App, set Shader Cache Size back to Driver Default, click Apply, and restart once more.

Delete the contents of those folders, not the folders themselves. NVIDIA also documents an alternative route: the third-party Display Driver Uninstaller has a Clean Shader Cache (Only) button, reached by selecting GPU as the device type and NVIDIA as the device. Its article says to restore the Driver Default setting afterwards either way.

Two reboots rather than one is not ceremony. The first gets the driver out of the way of the files you are about to remove; the second settles the restored setting. If you skip straight to deleting while the cache is still enabled, you are racing the driver for the same files.

Driver cache versus per-game pipeline caches

The folders above are NVIDIA’s cache. They are not the only shader cache on your machine, and confusing the two leads to a lot of wasted effort.

Direct3D 12 gives applications their own shader cache. Microsoft’s D3D12 Shader Cache specification defines disk-backed cache sessions as being “backed by files on disk, that will persist from run to run, unless cleared,” and separately defines a driver-managed cache kind that “refers to the cache which is managed by the driver,” where “operations for this cache are hints.” Two caches, two owners.

Games can also cache compiled pipeline state objects directly. Microsoft’s pipeline state cache sample describes exactly why they do: “An app can use PSO libraries to cache compiled PSOs to disk and avoid costly shader compilation during subsequent runs.”

Practically, this means a game that still hitches after you clear the NVIDIA folders may be reloading its own pipeline cache instead. It also means a game that hitches on first launch after a driver update may be recompiling PS states that the driver’s cache never held in the first place. If you are chasing a specific title, check whether it exposes its own shader or pipeline cache option before you touch the NVIDIA setting again.

Leave it alone, change it, or clear it

Leave it alone if your games settle within a session or two of launching, or after a driver update. That is the system working. This setting is not the reason a game stutters in hour three.

Change it if you keep a large library of demanding titles installed and you see repeat compilation cost as you rotate through them. Go to 10 GB, or one step at a time from Driver Default, and watch your free space. There is no reason to jump straight to Unlimited, and no evidence that it helps a library that already fits.

Clear it if a game crashes at launch, shows artifacts, or lost performance right after something changed on the system. Follow NVIDIA’s sequence in the order written, and put the setting back when you are done.

Stop tuning it the moment the symptom survives a cleared cache. A cache that has been deleted and rebuilt cannot be the cause of a hitch that is still there afterwards, and this control has nothing to say about a problem that lives in the game, the driver’s per-game profile, or the rest of the machine. The stuttering guide sorts those by pattern, and if you are choosing between driver branches rather than cache sizes, the Game Ready versus Studio driver comparison covers that decision.

One last boundary. This setting governs shaders the driver compiles for your games. It is not a way to buy frame rate, and on a system where the FPS calculator already tells you the GPU is the limit, no cache size will change the answer.

Frequently asked questions

What is the best Shader Cache Size setting?
Leave it on Driver Default unless you have a specific reason to change it. The setting caps how much disk space the driver may use for compiled shaders, and NVIDIA’s own guidance is to pick a limit large enough for the games you normally play but not so large that it eats your free disk space. If you already sit near the default and rarely rotate through a big library, moving it up buys you very little.
Does a bigger shader cache increase FPS?
No. NVIDIA describes the cache as storing compiled shaders so that later runs of the same game do not repeat the shader compilation. That work is not frame rendering, so removing it changes how quickly a game settles after launch rather than how fast it renders. Average frame rate at a steady state is not what this setting controls.
Should I set Shader Cache Size to Disabled?
Only as a temporary step while you clear a damaged cache. NVIDIA’s own cache-deletion procedure sets the control to Off, reboots, deletes the contents of the DXCache and GLCache folders, then returns the setting to Driver Default and reboots once more. Leaving it disabled permanently means paying the compilation cost on every launch.
Does ‘Unlimited’ use a lot of disk space?
It can, because the only remaining ceiling is your free space. NVIDIA’s guidance says to set a limit that covers your normal games but does not exceed available disk space, and it notes that higher-end games may need several hundred megabytes each. A large library of demanding titles is exactly the case where an unbounded cache grows without anyone noticing.
Where do I delete the NVIDIA shader cache files?
NVIDIA’s support article names %USERPROFILE%\AppData\Local\NVIDIA\DXCache and the GLCache folder beside it, plus the NV_Cache folder inside %USERPROFILE%\AppData\Local\NVIDIA Corporation. Delete the contents of those folders rather than the folders themselves, then restore the Shader Cache Size setting and reboot.
Does installing a new driver clear the shader cache?
Yes. The NVIDIA Control Panel reference states plainly that installing a new driver deletes the cache and that you may see stutter the first time you run a game afterwards. That is expected behaviour, not a fault, and it is one reason a driver update can make a game hitch for a session or two before settling.
Is the DirectX 12 shader cache the same as the NVIDIA cache?
No. Direct3D 12 exposes its own disk-backed shader cache sessions that persist from run to run, and apps can also cache compiled pipeline state objects themselves. Microsoft documents the driver-managed cache as a separate cache kind whose operations are hints. Clearing the NVIDIA folders does not necessarily clear a game’s own pipeline cache, and the reverse is also true.

Sources and corrections

Last updated
Methodology
See our methodology for research and review standards. It draws on 5 cited sources, listed below, each checked against the original page on the date above. Every menu name, option name and option list on this page was read from NVIDIA’s own documentation on 2026-11-16: the NVIDIA Control Panel Help reference for Manage 3D Settings, and the support article on deleting NVIDIA shader cache files, which is also the source for the current NVIDIA App paths. I did not time a single shader compile for this page, so no frame-time, stutter-length or disk-size figure is quoted; every behavioural statement is attributed to the document that makes it. Microsoft’s Direct3D 12 material is used only for the distinction between the driver’s cache and an application’s own pipeline cache.
Corrections
Spotted an error? Email a correction with the affected line and what you found. The draft includes this page’s address. Verified changes are recorded here. Contact details.

About the author

Written by Lowell K. Wood IV, who builds and runs TechFuelHQ from St. Louis, Missouri.