Gaming

Shader Cache

Stored compiled graphics programs that a game or driver can reuse instead of compiling them during play. This may reduce compilation-related pauses, but caches can be rebuilt after game, driver or hardware changes and cannot remove every cause of stutter.

How it works

Shaders are small graphics programs used to draw materials, lighting and other effects. A cache keeps compiled versions for reuse. When a game encounters a shader it has not prepared, compilation can interrupt the flow of frames. Some games instead prepare a set of shaders before normal play begins.

Important differences and limits

A cache is not a permanent cure for every pause. Game updates, driver changes and different graphics options can require new compilation. Storage loading, CPU work and network problems remain separate causes of stutter. Repeatedly deleting a working cache may force compilation again and make the next session less smooth.

A useful practical check

Let an official shader-preparation step finish before judging a new installation. Compare a first visit to a scene with subsequent visits and note whether the same pause returns. Keep supported cache settings unless a documented troubleshooting procedure calls for a reset. Do not download supposed shader-cache fixes from untrusted sources.

An example in practice

A first encounter with a new visual effect may pause while its shader is compiled, yet later encounters may be smooth. If the pause repeats on every visit, the explanation may involve something else. Compare repeated scenes before erasing caches or changing hardware.

Technical sources

← All glossary terms