Repository navigation
Shader Cache Management
GameAtlas includes shader cache management tools to help users inspect and troubleshoot cached shader data that can affect game performance, stuttering, and graphical behavior.
Shader caches are used by games, graphics drivers, and compatibility layers to avoid recompiling shaders every time a game runs. In normal use, they improve performance. In some situations, however, stale or corrupted cache data can contribute to problems.
Depending on the operating system, GPU vendor, launcher, and game, GameAtlas can help surface relevant shader cache locations and provide tools for managing them.
This can include:
- Identifying shader cache locations
- Showing which cache type is associated with the selected game or system
- Opening cache folders
- Clearing supported cache data
- Helping distinguish game-specific caches from driver-level caches
- Providing troubleshooting context before deleting anything
Shader cache support varies by platform and graphics stack.
Modern games use shaders for tasks such as:
- Lighting
- Shadows
- Materials
- Reflections
- Post-processing
- Ray tracing
- Upscaling
- Image reconstruction
Shaders often need to be compiled into a form the GPU can use.
To reduce repeated compilation, the game or graphics driver may store compiled data in a cache.
On later launches, the cached version can be reused.
A healthy shader cache can reduce:
- Shader compilation time
- Stuttering
- Repeated work during gameplay
- Loading delays
This is especially important in games that compile many shaders dynamically.
Clearing shader caches is not something that should be done routinely.
It is mainly useful when troubleshooting a specific problem.
Possible reasons include:
- Persistent graphical corruption
- Problems after a GPU driver update
- Unexpected stuttering that began after a configuration change
- A cache that may be corrupted
- Rendering behavior that remains after game settings are reset
- A game update that changed shaders significantly
- Troubleshooting a mod or graphics injector
After clearing a cache, the game may need to rebuild it.
After shader cache data is deleted, the next game launch may be slower or stutter more than usual.
This can happen because shaders must be compiled again.
Depending on the game, rebuilding may happen:
- During startup
- During a dedicated shader compilation screen
- The first time an effect appears
- Gradually while playing
Temporary stutter immediately after clearing a shader cache does not necessarily indicate a problem.
On Windows, several different shader caches may exist at the same time.
These can include:
- GPU driver caches
- DirectX shader caches
- Game-specific caches
- Launcher-managed caches
GameAtlas can surface supported Windows cache locations so users do not need to locate them manually.
See Windows.
NVIDIA drivers maintain shader cache data for applications and games.
Depending on driver version and configuration, cache data may be stored in NVIDIA-specific directories.
GameAtlas can use detected GPU information to determine when NVIDIA-related shader cache management is relevant.
Clearing the NVIDIA cache may cause multiple games to rebuild shader data afterward.
AMD graphics drivers also maintain shader cache data.
GameAtlas can surface relevant AMD cache information when an AMD GPU is detected.
As with other vendor-level caches, clearing these files can affect more than one game.
Intel graphics hardware and drivers may also use cached shader or pipeline data.
GameAtlas can use detected Intel graphics information where supported to surface the relevant cache context.
Windows can maintain a DirectX shader cache independently of individual games.
This cache may contain compiled shader data used by DirectX applications.
Clearing the DirectX shader cache can sometimes help with rendering issues after:
- Driver updates
- Major game updates
- Graphics configuration changes
Because it is a system-level cache, clearing it can affect multiple games.
Linux shader caching can involve several different systems depending on the GPU driver and runtime.
Potential cache types include:
- Mesa shader caches
- NVIDIA caches
- Steam shader data
- DXVK state or cache data
- VKD3D-related caches
- Game-specific caches
See Linux.
Steam can manage shader-related data for installed games.
On Linux, this may be especially relevant for games running through Proton.
Steam can download or generate shader-related data to help reduce compilation work during gameplay.
Deleting Steam-managed shader data may cause it to be rebuilt or downloaded again.
Systems using Mesa-based graphics drivers may maintain shader caches in user-level cache directories.
This is commonly relevant to:
- AMD GPUs
- Intel GPUs
GameAtlas can surface supported Mesa-related cache information where appropriate.
NVIDIA's Linux drivers can also maintain shader cache data.
Cache location and behavior can vary depending on:
- Driver version
- Environment
- Vulkan usage
- Application
GameAtlas can use detected NVIDIA hardware to determine whether these caches are relevant.
DXVK translates Direct3D 9, 10, and 11 calls to Vulkan and is commonly used by Wine and Proton.
Some games or configurations may maintain DXVK-related cache or state data.
This can affect startup behavior and stuttering in Windows games running on Linux.
VKD3D-Proton provides Direct3D 12 support through Vulkan for Proton and Wine.
Shader and pipeline compilation behavior can therefore differ from native Windows DirectX 12.
GameAtlas may surface relevant context when troubleshooting a Direct3D 12 game running through Proton.
Some games maintain their own shader cache independently of the operating system or graphics driver.
These caches may be stored in:
- The game installation folder
- Documents
- AppData
- LocalAppData
- Saved game directories
- User cache directories
- Proton or Wine prefixes
If GameAtlas can identify a reliable game-specific cache location, it can surface it separately from system-level caches.
These are not the same thing.
A driver-level cache may be shared across many games.
A game-specific cache typically belongs only to one title.
This distinction matters because clearing a driver-level cache may cause shader rebuilding across multiple games.
GameAtlas aims to make the cache scope clear before any destructive action.
Before clearing shader cache data:
- Close the game.
- Close the launcher if it is actively writing cache data.
- Make sure no shader compilation process is still running.
- Confirm which cache is being cleared.
- Avoid deleting unrelated files manually.
GameAtlas should be preferred over manually deleting broad cache directories when a supported cache-management action is available.
Do not clear shader cache data while the game is running.
A running game may:
- Have files open
- Recreate data immediately
- Write incomplete cache data
- Behave unpredictably
Always exit the game first.
Not all stutter indicates a broken cache.
Shader compilation stutter often occurs when the game encounters a shader for the first time.
Symptoms can include:
- A brief hitch when entering a new area
- Stutter when a new effect appears
- Stutter during the first playthrough that improves later
- Increased hitching after a driver update
If the stutter improves over time, normal shader compilation may be the cause.
If a game is already compiling shaders successfully, clearing the cache may remove useful compiled data.
The result can be more stuttering until the cache is rebuilt.
For that reason, shader cache clearing should be treated as a troubleshooting step rather than a general performance optimization.
Graphics driver updates can affect cached shader data.
Depending on the driver and cache type, an update may:
- Preserve the existing cache
- Invalidate the cache automatically
- Create a new cache
- Leave old cache files behind
If graphical problems begin immediately after a driver update, clearing the relevant shader cache can be a reasonable troubleshooting step.
Large game updates can also change shaders.
After an update, the game may:
- Rebuild shaders automatically
- Run a shader compilation step
- Continue using compatible cached data
- Leave obsolete cache entries behind
Do not assume the cache is broken just because a game recompiles shaders after an update.
Graphics mods can sometimes interact with shader compilation or cache behavior.
Examples include:
- ReShade
- RenoDX
- Ray-tracing modifications
- Texture or rendering mods
- Frame-generation modifications
- Engine-level graphics tweaks
If a rendering issue starts after installing a graphics mod, consider troubleshooting the mod before clearing all system shader caches.
See RenoDX.
Shader cache management works closely with GameAtlas performance diagnostics.
When investigating stuttering, GameAtlas may need to distinguish between:
- Shader compilation
- CPU bottlenecks
- GPU bottlenecks
- VRAM pressure
- Storage streaming
- Background applications
- Display configuration problems
Shader cache clearing is only appropriate for some of these conditions.
Background overlays and monitoring applications can sometimes create symptoms similar to shader stutter.
Before deleting caches, it may be useful to simplify the gaming environment using Clean Launch.
See Clean Launch.
Large shader caches are not automatically a problem.
A large cache can simply indicate that:
- Many games have been played
- The system has accumulated compiled shader data
- A game uses a large number of shaders
Cache size alone is usually not a reason to clear it.
Shader caches can consume storage space, but GameAtlas shader cache management is primarily designed for troubleshooting rather than general disk cleanup.
Deleting caches to recover storage may result in:
- Additional shader compilation
- Longer startup times
- Temporary stuttering
Users should weigh those trade-offs before clearing large caches.
Systems with more than one GPU may have cache data associated with different graphics drivers.
Examples include:
- Integrated Intel graphics plus NVIDIA
- AMD integrated graphics plus AMD dedicated graphics
- Multiple dedicated GPUs
GameAtlas uses detected hardware information to determine which shader cache categories are relevant.
See Hardware Detection.
If a game is running on the wrong graphics adapter, clearing shader caches is unlikely to solve the underlying problem.
Check GPU selection first.
Shader cache availability depends on:
- Operating system
- GPU vendor
- Driver version
- Game
- Launcher
- Graphics API
- Compatibility layer
- File permissions
Not every cache type can be safely identified or managed automatically.
GameAtlas should avoid exposing destructive actions when the target cannot be determined confidently.
GameAtlas may not show a shader cache if:
- The game has never been launched
- The cache has not yet been created
- The driver uses a different cache layout
- The cache location changed in a driver update
- The game uses an unsupported cache type
- File permissions prevent access
This does not necessarily indicate a problem.
If you suspect a shader-related problem:
- Confirm the game and GPU drivers are up to date.
- Restart the game and reproduce the problem.
- Determine whether the issue improves after playing for a while.
- Check Clean Launch for conflicting overlays or background tools.
- Review Performance Diagnostics for other likely bottlenecks.
- If the problem still appears shader-related, close the game.
- Clear only the relevant shader cache.
- Launch the game and allow shader compilation to complete.
- Test the same area or scenario again.
When managing shader caches:
- Do not clear caches routinely.
- Close games before deleting shader data.
- Clear the smallest relevant cache first.
- Expect temporary shader compilation after clearing.
- Avoid deleting entire system cache directories manually.
- Test the same game area before and after a cache reset.
- Consider recent game and driver updates when diagnosing issues.
- Use GameAtlas performance diagnostics to rule out other causes first.