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 minuteFor most NVIDIA gaming PCs, leave Shader Cache Size on Driver Default. Choose 10 GB when you have several modern games and ample free space but want a predictable cap. Move to 100 GB only if a large library repeatedly evicts shaders, and use Unlimited only when you actively monitor storage. A larger cache can prevent repeated shader recompilation after eviction; it cannot eliminate first-time compilation or guarantee higher frame rates.
What NVIDIA Shader Cache Size actually controls
The setting is a disk-space ceiling for compiled shaders. A game and its graphics driver compile shader programs into a form the GPU can reuse, then NVIDIA stores those compiled results on your drive. On later launches, the game can reuse the stored shaders instead of compiling the same work again.
As an Amazon Associate I earn from qualifying purchases.
NVIDIA describes Shader Cache Size as the maximum amount of disk space the driver may use. As the cache approaches that limit, the driver removes older entries to make room for newer ones. If the limit is too small, a shader that a game still needs may be evicted; the next time that effect appears, the driver has to compile it again. That recompilation is one reason a game can stutter during play.
Crashes, No Sound, or Screen Glitches?
Random freezes, missing sound and display glitches usually trace back to one bad driver. Find and replace yours safely.Free scan · under a minutePC 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 & 11The cache is not a frame-rate setting, a graphics-quality preset or a memory allocation for your GPU. It is persistent storage for compiled shader data, and its main benefit is reducing avoidable compilation work on subsequent runs.
#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
Available NVIDIA options
| Setting | What it permits | Best fit | Main trade-off |
|---|---|---|---|
| Disabled | No shader cache is retained. | Short troubleshooting tests when you specifically need to rule out cached data. | Repeated shader compilation can return on every launch or during play. |
| 128 MB | Up to 128 MB of cache storage. | Very constrained systems where disk use must be minimal. | Modern games can outgrow it quickly, causing frequent eviction. |
| 256 MB | Up to 256 MB. | Legacy or very small game installations. | Little room for a current multi-game library. |
| 512 MB | Up to 512 MB. | Small libraries with older or less shader-heavy titles. | Eviction remains likely as several large games accumulate data. |
| 1 GB | Up to 1 GB. | Systems with limited free space and only a few games installed. | Can still force recompilation in modern games. |
| 5 GB | Up to 5 GB. | Moderate libraries where a finite limit is preferred. | May be reached by several large, frequently played games. |
| 10 GB | Up to 10 GB. | The practical finite choice for many gaming PCs. | Uses more reserved capacity than Driver Default on systems that would otherwise need less. |
| 100 GB | Up to 100 GB. | Very large libraries or systems where lower limits repeatedly evict useful shaders. | Reserves a substantial amount of possible disk use and is excessive for a small library. |
| Unlimited | No driver-imposed cache ceiling. | Users with abundant free space who monitor the drive and want to avoid limit-based eviction. | Cache growth is unbounded; it can consume space needed by games, updates and Windows. |
| Driver Default | NVIDIA chooses the default capacity for the installed driver. | Most users who want the lowest-maintenance setting. | The effective capacity can change with NVIDIA’s driver or app behavior. |
NVIDIA’s control-panel reference lists Disabled, Unlimited, 128 MB, 256 MB, 512 MB, 1 GB, 5 GB, 10 GB and 100 GB as selectable limits. NVIDIA support currently describes the NVIDIA App’s Driver Default as 16 GB. Treat that 16 GB figure as the current app-listed default, not as a promise that every driver version or interface will expose the same number.
Which setting should you choose?
Driver Default: the right starting point for most people
Driver Default is the lowest-maintenance option. It lets NVIDIA select a capacity rather than forcing you to predict how many games you will install or how much shader data each one will create. Choose it when you have no clear evidence that the cache is being evicted, when your game library is modest, or when you routinely install drivers and do not want to revisit a manual limit.
This is also the safest answer after building or reinstalling a PC. First establish whether stutter is actually related to shader eviction; changing the ceiling before observing a pattern makes troubleshooting harder.
Recommended Free Tools
10 GB: a sensible finite ceiling for a broad modern library
Use 10 GB when you play several current PC games, have comfortable free space on the system drive and prefer a known upper bound. It is a practical expansion over small limits without the storage uncertainty of Unlimited. The recommendation is editorial, based on NVIDIA’s documented eviction behavior and capacity choices rather than a vendor performance benchmark.
100 GB: for repeated eviction in a very large library
100 GB is justified when you regularly rotate through many shader-heavy games and can show that smaller limits are removing data you soon need again. It is not a universal quality setting. A large library alone does not prove that every game will fill 100 GB, so check free space and actual cache growth before selecting it.
Unlimited: only with deliberate storage monitoring
Unlimited removes the driver’s configured ceiling, but it does not make shader compilation faster and does not make the cache free. NVIDIA’s guidance is that the limit should be large enough for the games you use without exceeding available drive space. Unlimited therefore fits a user who has substantial headroom, understands that the cache can continue growing and is willing to inspect storage periodically.
Small limits and Disabled: specialist choices
128 MB through 5 GB can make sense on a storage-constrained machine or a system that plays only a small set of older titles. They are poor defaults for a large modern library because reaching the limit triggers eviction. Disabled is primarily a diagnostic choice; it removes persistence and can make recompilation more frequent.
Rank #2
- 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
Decide using five practical factors
1. Free space on the drive that holds the cache
Start with capacity, not a theoretical performance target. A cache limit competes with the operating system, game installs, shader updates, save files and temporary files. Leave enough free space for normal Windows and game operation. Unlimited is unsuitable if the drive is already close to full, and 100 GB is unwise when reserving that much potential space would crowd out your library.
2. Eviction risk
A small cap becomes a problem only when the working set of compiled shaders exceeds it. NVIDIA warns that, as the limit is approached, older shaders are removed; if the limit is too small, even shaders still in use may be removed and gameplay stutters can result. If you observe the same game recompiling effects after you have recently played other large titles, move up one finite tier rather than jumping immediately to Unlimited.
3. Number and size of installed games
One frequently played game has a different cache footprint from dozens of modern games installed simultaneously. A broad library, frequent switching and large DirectX 12 titles increase the chance that a smaller ceiling will churn. A small, stable library usually does not need 100 GB simply because the option exists.
4. Driver-update frequency
A new NVIDIA driver installation deletes the shader cache. The first run after an update can therefore stutter while shaders are rebuilt, even when your chosen size is ample. If you update often, expect a temporary warm-up period and do not interpret that first session as proof that 10 GB, 100 GB or Unlimited failed.
5. Whether you are troubleshooting or choosing a steady-state limit
Clearing a cache and choosing its long-term ceiling solve different problems. A reset can remove corrupted or stale files; a larger limit reduces eviction. Decide which problem you are addressing before changing both at once, or you will not know which action changed the symptoms.
How to change Shader Cache Size
- Open NVIDIA Control Panel.
- Go to Manage 3D settings.
- On the global settings page, locate Shader Cache Size.
- Select Driver Default, a finite value such as 10 GB or 100 GB, or Unlimited according to your storage and library.
- Apply the change, then launch the game normally. The driver may need to rebuild entries that are absent or have been evicted.
Change one variable at a time. If you are diagnosing stutter, record the game, driver version, when the hitch occurs and whether it appears only after an update. That record is more useful than changing the cache repeatedly between sessions.
Does a larger cache fix stuttering?
It can prevent one specific class of stutter: recompilation caused by shader entries being evicted and needed again. It cannot fix every hitch. Shader compilation is only one source of stutter, and a first run still has to compile shaders that have never been cached.
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
- Likely to improve: recurring hitches that follow heavy cache churn, especially after switching among many large games.
- Unlikely to improve: network latency, asset-streaming stalls, CPU bottlenecks, unstable overclocks, background processes or a game engine’s own traversal stutter.
- Not an FPS upgrade: a larger ceiling stores more compiled data; it does not raise the GPU’s rendering throughput.
If stutter happens only during the first minutes of the first launch after a driver update, the cache is probably rebuilding rather than overflowing. Give the game time to complete its initial work, then compare later runs under the same conditions.
Quick wins for a faster PC:
Fix the driver behind crashes, sound loss and screen glitchesFind Drivers →Repair Windows errors before they cause bigger problemsFix Now →Scan for outdated or missing drivers - takes under a minuteDriver Scan →Why stutter often returns after a driver update
NVIDIA states that installing a new driver deletes the existing shader cache. The new driver must compile and store shaders again, so the first session after an update can hitch even if the previous driver was smooth and the cache limit was never reached.
This behavior is temporary for a given title: as you play, the cache repopulates. A larger limit does not preserve entries across the driver installation because the update itself removes them. Avoid judging a setting from a single post-update launch; test after the game has had an opportunity to rebuild its commonly used shaders.
Should you clear the NVIDIA or DirectX shader cache?
Clear the cache when you are troubleshooting corrupted or stale shader data, unexplained shader-related hitching after a driver change, or a problem that persists after normal rebuilding. NVIDIA support documents deleting shader-cache files as a troubleshooting action; after deletion, the next launch recreates them.
- Close running games and graphics applications.
- Follow NVIDIA’s support procedure for deleting the shader-cache files.
- Restart the affected game and expect the first session to compile shaders again.
- Judge the result over subsequent launches, not during the immediate rebuild.
Resetting is not a guaranteed performance upgrade. It removes the existing compiled data, so an initial increase in compilation stutter is normal. If clearing the cache changes nothing after it has rebuilt, raising the size limit is unlikely to address the real cause.
NVIDIA Auto Shader Compilation
NVIDIA has announced an Auto Shader Compilation beta feature that rebuilds previously compiled DirectX 12 shaders while the PC is idle. It is off by default and can be enabled from NVIDIA App > Graphics settings.
The feature can reduce the amount of foreground rebuilding after a cache reset or driver change, but it does not remove first-time compilation for a brand-new title. It also does not turn an undersized cache into a larger one: the cache still needs a capacity that fits the games you use, and the feature remains beta software whose behavior may change.
Rank #4
- 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
A profile-based recommendation
| Your situation | Recommended setting | Reason |
|---|---|---|
| One to a few games, plenty of free space, no recurring cache symptoms | Driver Default | Lowest maintenance and no evidence that a manual cap is needed. |
| Several modern games installed and a spacious system drive | 10 GB | Finite headroom that reduces eviction risk without unbounded growth. |
| Many large games, frequent rotation, and documented repeated eviction on smaller limits | 100 GB | More room for a large working set when storage can support it. |
| Very large free-space reserve and willingness to monitor usage | Unlimited | Removes the configured ceiling, trading eviction protection for potentially unlimited disk consumption. |
| Small drive or a narrowly focused legacy library | 1 GB or 5 GB | Controls storage use when the game set is unlikely to need more. |
| Temporary diagnosis of cache corruption | Keep a normal limit and clear the cache | Resetting tests the data; changing to Disabled is not required for the reset. |
Troubleshooting by symptom
Stutter appears in the first session after every driver update
Expect a rebuild because the update cleared the cache. Play long enough for the affected areas and effects to compile, then evaluate later runs. Auto Shader Compilation may rebuild previously compiled DirectX 12 shaders while idle if you enable its beta option in NVIDIA App graphics settings.
The same game hitches again after you play other large games
This pattern is consistent with eviction. Move from Driver Default or a small limit to 10 GB if your drive has room. If a very large library still cycles through the same shaders, consider 100 GB and monitor free space.
The drive is losing space over time
Unlimited allows cache growth without a driver-imposed ceiling. Switch to Driver Default or a finite value that fits your library, then clear the cache only if you need to reclaim existing data or are diagnosing corruption. Keep enough free space for the operating system and game updates.
Stutter continues after a cache reset and rebuild
A reset did not address the underlying cause. Check whether the hitch is tied to asset streaming, CPU load, background activity, network conditions or the game’s own engine. Increasing Shader Cache Size helps only when eviction and recompilation are the trigger.
A game stutters only the first time an effect appears
That can be first-time shader compilation rather than an undersized cache. A larger limit cannot provide a shader that has never been compiled. Later runs may be smoother once the result is stored.
Storage planning: when a larger SSD helps
If your system drive cannot spare room for a 10 GB or 100 GB ceiling alongside a large game library, additional capacity is the practical fix. A 1 TB NVMe SSD can provide that headroom, but it is an optional storage upgrade, not a guaranteed stutter cure. The drive gives the cache and games more room; it does not change the driver’s compilation behavior or eliminate first-run shader work.
What’s actually slowing this PC down?
Pick the symptom - the matching free tool is one click away.
Do not buy storage solely to chase a larger number. First determine whether your current limit is actually causing eviction. If the cache is not filling and your stutter has another cause, extra capacity will not solve it.
Bottom line
Set NVIDIA Shader Cache Size to Driver Default unless you have a reason to manage the ceiling yourself. Use 10 GB as the balanced finite choice for a modern multi-game PC, 100 GB for a very large library that demonstrably churns smaller limits, and Unlimited only with substantial free space and regular monitoring. Clear the cache for troubleshooting, expect temporary rebuilding after driver updates, and treat shader-cache sizing as a way to reduce recompilation—not as a universal stutter or performance fix.
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.
