Why Is My DirectX Cache So Large on Windows

Before You Clean

Shader and game caches reduce work on later launches. Resetting them can cause compilation delays and stutter while they rebuild; their existence is not a reason to clear them regularly.

Review and Clean Manually

1. Determine whether the issue is disk space, a rendering fault, or game stutter. Check game and driver updates first.

2. Close the game and launcher. Save local games and preserve mods, screenshots, and configuration.

3. For a DirectX cache reset, use Windows Temporary files > DirectX Shader Cache when available. For a game-specific cache, follow that game or launcher’s documented procedure.

4. Do not delete game installations or save folders. Avoid repeatedly resetting a healthy shader cache.

5. Launch the game and allow compilation to finish before comparing performance. Measure actual free space if that was the goal.

Where Kudu Helps

Kudu groups supported launcher caches under Gaming and treats supported performance-cache targets as optional resets. Performance caches are shown as optional resets and are unselected by default. Select a reset only for a specific, approved troubleshooting task. Expect recompilation or a slower next launch; resetting a healthy cache is not a routine speed boost.

Open Clean up > System Cleaner and run Scan. Review the relevant category and expand its results to inspect the paths. Set exclusions for anything you need to keep, then check the full selected total before Clean. Results search filters the view; it does not erase selections elsewhere.

After cleaning, check the summary and Activity > Cleanup receipts for removed, skipped, or failed items. A receipt is an outcome record, not a backup. Recovery Centre restores supported settings, not deleted files. Compare actual disk free space and test the original symptom; cache removal alone is not a promise of better performance.

Download Kudu Free → · Cleaning reference

References

• Official maintenance documentation
• Kudu cleaner rules