Windows 11: Clear DirectX Shader Cache to Fix Game Stutter

Microsoft Support documents both Settings-based storage cleanup and Disk Cleanup for Windows 10 and Windows 11. More importantly, Microsoft’s Direct3D 12 documentation confirms that Disk Cleanup can enumerate and clear supported on-disk shader caches. This is not a registry hack, a driver uninstall, or a way to gain permanent FPS: it removes reusable graphics-compilation data so Windows and the game can create fresh copies where needed.

The practical catch is simple. The first launch after clearing the cache can be slower, and the first match, level, or area that introduces new effects can briefly hitch while shaders or pipeline states are rebuilt. Judge the result only after returning to the same game area that had the problem.

What the DirectX Shader Cache Stores​

Shaders are small GPU programs used for rendering effects such as lighting, shadows, reflections, post-processing, terrain, and character materials. Modern DirectX games can combine those shaders with hardware- and driver-specific pipeline settings. Preparing those combinations can take time, so Windows, the graphics driver, and games may save reusable results to disk.

Microsoft’s Direct3D 12 documentation describes cached pipeline state as data tied to the hardware, driver, and machine that created it. That design explains why a cache that was useful before a graphics-driver update may be worth rebuilding afterward: a new driver can change the code path used to translate graphics work for the GPU.

A bad or obsolete cache is only one possible cause of stutter. Clearing it will not repair a failing graphics card, add VRAM, fix a poorly optimized game patch, resolve an unstable overclock, or compensate for a CPU bottleneck. It is most useful when the trouble is confined to a DirectX game, began after a driver or major Windows change, and persists after a normal reboot.

Do not confuse this cache with downloaded shader packages from Steam, game-specific shader caches, or NVIDIA, AMD, and Intel driver caches. Disk Cleanup handles the Windows DirectX cache it recognizes; it does not guarantee removal of every cache a game, launcher, engine, or driver maintains. Microsoft’s Direct3D 12 documentation specifically notes that some application-created working-directory caches are outside Disk Cleanup’s reach.

Clear DirectX Shader Cache from Windows Settings​

The Settings route is the clearest option on a current Windows 11 installation and is also available on supported Windows 10 builds. Close the affected game and its launcher before beginning. This reduces the chance that the game recreates or keeps files open while you are cleaning up.

1. Open Settings with Windows + I.
2. Select System, then select Storage.
3. Open Temporary files. On some Windows 11 configurations, Storage may first show Cleanup recommendations; open the temporary-files category from there if it is offered.
4. Let Windows finish calculating the files available for removal. This can take a short while, especially on a full system drive.
5. Find and select DirectX Shader Cache.
6. Review every other selected category before continuing. Windows may preselect unrelated items such as the Recycle Bin, temporary files, thumbnails, Windows Update Cleanup, or Downloads. Clear those selections unless you also intend to remove them.
7. Select Remove files or Clean up, depending on the Windows version and page you reached.

The central safeguard is reviewing the complete selection, not merely ticking the DirectX item. The DirectX Shader Cache entry itself is designed to be disposable. Accidentally including Downloads, a previous Windows installation, or a needed rollback package is a different decision with different consequences.

If you do not see a DirectX Shader Cache entry, do not assume the cleanup failed. Windows may have nothing currently eligible to remove, the cache may have been cleared already, the game may rely on its own cache instead, or the available cache may not be one that Windows exposes through this page. In that situation, use Disk Cleanup once, then move on to game- or GPU-vendor-specific troubleshooting rather than deleting random folders under AppData.

Use Disk Cleanup for the Same Windows-Managed Cache​

Disk Cleanup remains useful because it exposes cleanup categories in a compact list and is explicitly recognized by Microsoft’s Direct3D 12 documentation as a way to clear supported disk shader caches.

1. Open Start and search for Disk Cleanup.
2. Select Disk Cleanup from the results.
3. When prompted for a drive, choose the drive containing Windows—normally C:—then select OK.
4. Wait for Disk Cleanup to calculate removable files.
5. Select DirectX Shader Cache.
6. Deselect every category you did not deliberately choose.
7. Select OK, then choose Delete Files to confirm.

You normally do not need to select Clean up system files merely to remove DirectX Shader Cache. That button causes Disk Cleanup to rescan for additional system-level categories, including items with consequences well beyond gaming performance. Use it only when you know you also want to assess items such as Windows Update Cleanup or a previous Windows installation.

Microsoft’s command reference also makes an important limitation clear: when Disk Cleanup is pointed at a drive other than the Windows installation drive, its available categories are much more limited. For this task, choose the system drive rather than a secondary SSD that happens to contain a game library.

What to Expect on the Next Game Launch​

After the cleanup finishes, start the affected game normally. A restart is not generally required, though it is reasonable if you had just installed a graphics driver or if the game, launcher, or driver software was still running during the cleanup.

Expect one or more of these temporary effects:

• The game may spend longer at its first launch, loading screen, or “compiling shaders” screen.
• The first visit to a map, menu, character, weather effect, or combat scene may show brief stutters as new graphics combinations are encountered.
• Disk activity and CPU use may increase while the game prepares replacement cache data.

This short-term cost is the point of the procedure. Shader and pipeline caches exist to avoid repeating expensive preparation work. Clearing them removes data that may be mismatched, stale, or corrupted, but it also discards data that may have been working correctly.

Test in a repeatable location: the same benchmark, save file, race, map, or busy city area where you noticed the stutter. Let the game finish any built-in shader compilation step, play long enough to revisit the troublesome scene, and then compare behavior. Clearing the cache immediately before a competitive session or a benchmark run can make results look worse because the cache has not yet had time to repopulate.

When Clearing the Cache Is a Good Fit—and When It Is Not​

Try this procedure after a clean graphics-driver update, a Windows feature update, a DirectX-game crash that leaves rendering artifacts behind, or a sudden regression in one game that otherwise ran properly on the same PC. It is also reasonable if Disk Cleanup shows the cache consuming an unexpectedly large amount of system-drive space.

Do not make it a routine weekly “performance optimization.” Windows and games create shader caches to reduce repeat work, and repeatedly deleting them can create the very launch-time compilation pauses players are trying to avoid. A cache clear is a reset button for a specific suspicion, not maintenance that improves every game.

If the game still has repeatable stutter after its cache has rebuilt, move to evidence-based checks: verify the game’s installed files, confirm the current GPU driver is stable for the title, remove GPU or RAM overclocks, watch CPU, GPU, VRAM, RAM, and storage utilization during the stutter, and check whether the issue began with a game update. Visual corruption that persists across multiple games is more likely to require a driver reinstall, stability testing, or hardware investigation than another cache purge.

The concrete result of this cleanup is modest but useful: Windows removes its eligible DirectX shader-cache data, and the next game sessions create fresh data for the current system state. If the original problem was tied to that stale data, the benefit should appear only after the affected game has had a chance to rebuild what it needs.