Steam shader pre-caching usually reduces shader-compilation stutter more effectively than compiling shaders during play. It lets Steam send game shaders to your graphics driver before you start, so the driver can prepare hardware-specific code in its disk cache. When the game later requests a matching shader, most of that work is already finished.
The benefit is conditional, not a guarantee of perfectly smooth performance. A cache can be missing, incomplete or invalidated by a game update, driver change, GPU change, graphics API change or Proton/runtime change. In those cases, the game can still compile shaders or graphics pipelines while you play. Enabling pre-caching is generally the better choice when you value smoother first runs and can tolerate background processing or a wait before launch.
As an Amazon Associate I earn from qualifying purchases.
What Steam shader pre-caching actually does
Steam prepares driver-specific code before gameplay
A game normally contains hardware-independent shader code. Your graphics driver must translate that code into instructions suited to your particular GPU and driver version. Steam’s shader pre-caching subsystem takes shaders associated with a game, feeds them to the video driver and lets the driver store the resulting hardware-specific code in its on-disk shader cache. Valve maintainer kisak-valve described this process on October 15, 2023.
Free tools Windows power users keep installed
One-click scans. No signup required.
When the game later requests the same code, the driver can reuse the cached result instead of performing most of the compilation again. Valve summarized the practical effect as: “The practical effect is that stuttering is avoided whenever this happens.” The important qualification is “whenever this happens”: the requested shader must match a cache entry that is still valid for the current software and hardware combination.
#1 Best Overall
- MEET THE NEXT GEN: Consider this a cheat code; Our Samsung 990 PRO Gen4 SSD helps you reach near max performance with lightning-fast speeds; Whether you’re a hardcore gamer or a tech guru, you’ll get power efficiency built for the final boss
- REACH THE NEXT LEVEL: Gen4 steps up with faster transfer speeds and high-performance bandwidth; With a more than 55% improvement in random performance compared to 980 PRO, it’s here for heavy computing and faster loading
- THE FASTEST SSD FROM THE WORLD'S FLASH MEMORY BRAND: The speed you need for any occasion; With read and write speeds up to 7450/6900 MB/s you’ll reach near max performance of PCIe 4.0 powering through for any use
- PLAY WITHOUT LIMITS: Give yourself some space with storage capacities from 1TB to 4TB; Sync all your saves and reign supreme in gaming, video editing, data analysis and more
- IT’S A POWER MOVE: Save the power for your performance; Get power efficiency all while experiencing up to 50% improved performance per watt over the 980 PRO; It makes every move more effective with less consumption
Background Vulkan processing is preparation, not a second game launch
Steam exposes a setting named Allow background processing of Vulkan shaders. With it enabled, Steam can do preparation while the client is idle or before you launch a Vulkan game. The work may use CPU time, disk space and network data, depending on what cache material is available for that title. You may see Steam process shaders after an installation, update or driver change even though you have not opened the game.
An adjacent control can disable Steam’s shader pre-caching subsystem. Disabling it does not remove the game’s ability to compile shaders; it removes Steam’s opportunity to prepare compatible work ahead of time.
How in-game shader or pipeline compilation works
Compilation happens at the point of need
With in-game compilation, the game asks the driver or graphics API to create a shader or graphics pipeline when it reaches the relevant effect, material, level area or rendering state. If the requested object is not already available, compilation runs on the critical path. The visible result can be a short freeze, a hitch while turning the camera, a pause when a new effect appears or a series of uneven frame times during the first minutes of a session.
Microsoft’s Advanced Shader Delivery documentation, updated September 10, 2026, describes the general cost this way: “Compiling those shaders on the player’s device at launch, or "just-in-time" during gameplay, leads to longer load times, in-game shader compilation stutter, and higher power consumption.” The statement covers both launch-time compilation and compilation triggered during play; moving the work earlier can remove the most disruptive version of the problem.
Games can compile even when Steam pre-caching is enabled
Pre-caching and in-game compilation are not mutually exclusive. A title can reuse cached shaders and still compile objects that were not represented in the cache. A newly added effect, an uncommon graphics setting, a different resolution path or a pipeline generated from runtime data may not have a matching entry. The game also falls back to runtime compilation when cached binaries are invalid or incompatible.
Rank #2
- HUGE SPEED BOOST: Get random read/write speeds that are 40%/55% faster than 980 PRO; Experience up to 1400K/1550K IOPS, while sequential read/write speeds up to 7,450/6,900 MB/s reach near the max performance of PCIe 4.0*
- BREAKTHROUGH POWER EFFICIENCY: Use less power and get more performance; Enjoy up to 50% improved performance per watt over 980 PRO, plus optimal power efficiency with max PCIe 4.0 performance**
- SMART THERMAL CONTROL: Samsung's own nickel-coated controller delivers effective thermal control; With its slim size, 990 PRO is a perfect fit for desktops and laptops that meet the PCI-SIG D8 standard***
- THE CHAMPION MAKER: Up to 65% improvement in random performance enables faster loads for an ultimate gaming experience on PS5 and DirectStorage PC games****
- SAMSUNG MAGICIAN SOFTWARE: Get the most out of your SSD with Samsung Magician's advanced yet intuitive optimization tools; Monitor drive health, protect valuable data, and receive important updates for your 990 PRO
That is why a pre-cached game can still hitch once in a while. The existence of a cache improves coverage; it does not prove that every possible shader and pipeline combination has been prepared.
Which method reduces stutter more effectively?
For stutter caused specifically by shader or pipeline compilation, Steam pre-caching has the stronger design advantage because it moves work before the frame that needs it. A matching driver-cache entry means the game can load prepared code rather than pause while the driver builds it. In-game compilation leaves that work on the frame-time path, so the player experiences the delay at the moment a new rendering state is encountered.
The comparison is conditional on four things:
- Coverage: the cache must contain the exact shader or pipeline the game requests.
- Compatibility: the entry must match the current GPU, driver, graphics API, game build and, on Linux, the Proton/runtime environment.
- Validity: updates or configuration changes must not have invalidated the binary.
- Timing: Steam must finish processing before the game reaches the relevant effect.
No authoritative source provides one percentage that applies to all games, GPUs or drivers. Claims such as “pre-caching cuts stutter by a fixed amount” overstate what the evidence supports. The reliable conclusion is about where the work occurs: preparation before play usually produces better frame pacing than just-in-time compilation when the cache matches.
Steam pre-caching versus in-game compilation
| Comparison | Steam shader pre-caching | In-game shader or pipeline compilation |
|---|---|---|
| When work happens | Before launch or in the background while Steam prepares the game | At launch or when gameplay reaches an uncovered rendering state |
| Effect on first encounter | Can avoid most compilation time when a valid matching cache entry exists | Can pause or hitch the frame that triggers compilation |
| Coverage | Limited to shaders and pipelines represented in available cache data | Can handle newly encountered or runtime-generated objects |
| Compatibility dependency | GPU, driver, API, game build and Proton/runtime must remain compatible | Compiles for the current environment, but still pays the work cost during play |
| User cost | Background CPU and disk use, possible downloads and a wait before launch | Longer launch time or gameplay hitches, with no separate pre-processing wait |
| Typical failure mode | Steam processes shaders again after cache invalidation or an update | Repeated pauses as new effects or pipelines are encountered |
| Best fit | Players who prioritize smooth early-session frame pacing | Players who prefer to avoid background work and accept possible runtime pauses |
Should you enable Steam shader pre-caching?
Enable it when smooth first runs matter most
Leave shader pre-caching enabled if you want to reduce the chance of hitches during the first launch or first traversal of a game. This is particularly useful for large games with many effects, games that use Vulkan, and titles that are known to build pipelines while new areas load. Let Steam finish processing before judging the game’s frame pacing; launching immediately can force the title to compile whatever preparation has not completed.
Allow background Vulkan processing when you prefer preparation before launch
Turn on Allow background processing of Vulkan shaders when you would rather spend idle CPU and disk time before playing than encounter compilation work during a session. The setting is most useful when Steam is left open between play sessions and your system can process the queue without making other work unresponsive.
Rank #3
- This product has been replaced by our latest generation. Please search for the SANDISK Optimus GX 7100 NVMe SSD
- HIGH-OCTANE GAMING. Experience speeds up to 7,250MB/s read and 6,900MB/s write (1-2TB models), with up to 35% faster performance than previous generation.
- PURPOSE-BUILT. Designed for serious on-the-go gamers, with a PCIe Gen4 interface and SANDISK’s next generation TLC 3D NAND.
- MORE TIME TO CLEAR THAT CHECKPOINT. Built with laptops and handheld gaming devices in mind, with up to 100% more power efficiency over the previous generation.
- DO MORE WITH DASHBOARD. Ensure your drive is optimized for prime performance with the downloadable WD_BLACK Dashboard (Windows only).
Consider disabling it only for a deliberate trade-off
Disabling the subsystem can make sense if background processing repeatedly interferes with other work, consumes limited storage, or keeps reprocessing data you do not intend to use. It can also shorten the period before you can click Play, but the trade is a greater chance that the game performs compilation at launch or during gameplay. There is no universal setting that is best for every title, system or connection.
Do these 3 things before closing this tab:
1Repair Windows errors before they cause bigger problems2Scan for outdated or missing drivers - takes under a minute3Clear out junk files and repair common Windows errorsHow to check and change the Steam setting
- Open the Steam desktop client and select Steam → Settings.
- Open Downloads, then locate the Shader Pre-Caching section. Steam has changed settings layout over time, so use the settings search field if the section is not shown there.
- Leave shader pre-caching enabled if you want Steam to prepare compatible driver-cache data.
- Enable Allow background processing of Vulkan shaders if you want Steam to process Vulkan work before you launch the game.
- If you intentionally want to stop Steam’s subsystem, use the adjacent control that disables shader pre-caching. Read the label carefully: this is different from merely declining to wait for a current processing task.
- After changing the setting, restart Steam if the client does not immediately update the processing queue, then allow any pending work to finish before starting a demanding game.
The exact amount of processing, storage and waiting varies by game and by the cache data available for your system. Steam may show no work for a title, a short queue or repeated processing after a compatibility change. None of those displays, by itself, proves that the game will never compile a shader at runtime.
Why Steam may process Vulkan shaders again and again
Repeated processing is usually a sign that Steam or the driver is rebuilding data for a changed environment, not proof that the feature is useless. Common triggers include:
- Game updates: changed shaders or pipeline definitions no longer match the previous cache.
- Graphics-driver updates: a new driver can use a different compiler or invalidate older binaries.
- GPU changes: cache entries made for one GPU are not automatically valid for another.
- Graphics API changes: Vulkan and other rendering paths can require different shader or pipeline data.
- Proton or runtime changes: the compatibility layer and its graphics components can alter what the game requests.
- Incomplete or discarded data: interrupted processing, cleanup tools, disk-pressure policies or corrupted cache files can remove entries that Steam must recreate.
If processing starts after one of these events, let it complete once and test the game again. If the queue returns after every unchanged launch, note whether Steam, the game or the graphics driver changed between sessions. Persistent reprocessing alongside unusual crashes or corrupted graphics may point to a cache or driver fault rather than normal maintenance.
Linux and Steam Deck: the Proton qualification
On Linux and Steam Deck, Windows games commonly run through Proton, Valve’s compatibility layer built from modified Wine and graphics API implementations. Proton is part of the compatibility context for shader and pipeline caches. A cache prepared under one Proton version, driver stack or graphics runtime may not be reusable after another component changes.
The Tool Desk
Outbyte Driver Updater FREEFix the driver behind crashes, sound loss and screen glitchesFind Drivers →Outbyte PC Repair FREEClear out junk files and repair common Windows errorsFree Scan →Rank #4
- 【7450MB/s・Amazing Speed】Maximum read speed of 7450MB/s and maximum write speed of 6500MB/s (random read/ write speed of up to 1000K IOPS) realises the workflow of high-performance desktop PCs and notebook PCs. Ideal for power users who are looking for market-leading speeds.
- 【PCIe Gen4×4 for Superior Performance】Biwin NV7400 M.2 SSD utilizes the latest PCIe Gen 4x4 and 3D TLC NAND, choosing high-quality premium NAND flash chosen through our automated selection. Capacities of up to 4 TB are available, providing ample storage space and eliminating the anxiety of insufficient storage.
- 【PMIC Power Management & Graphite Heat Sink】NV7400 M.2 SSD adopts a composite power supply IC (PMIC), which improves power saving and energy saving performance by increasing the efficiency of power distribution, and effectively extends the durability of the SSD. Moreover, it is equipped with a 0.5mm graphene aluminium heat sink to prevent overheating with excellent heat dissipation performance and maintain stable top performance.
- 【Enhanced System Stability】The NV7400 delivers stable performance for demanding applications. Enhanced by Host Memory Buffer (HMB) technology, it ensures stable operation even under heavy workloads. The integration of Smart Cache optimizes data retrieval, while Zip data compression maximizes storage efficiency.
- 【Free Biwin Intelligence Software】Biwin Intelligence is multifunctional management software, designed to support Biwin consumer-brand storage products. For a more convenient and more secure storage experience, this software helps users manage their drives with features like performance test, data migration, firmware update, and more.
For that reason, compare stutter only after the game, Proton version and graphics driver are stable. A Steam Deck system can process shaders before launch and still compile a pipeline generated by a game’s current Proton configuration. Treat a Proton update as a possible cache-invalidation event, not as evidence that pre-caching has stopped working.
How to tell shader stutter from other kinds of stutter
Shader compilation is only one possible cause of uneven frame pacing. Traversal stutter from loading a new area, asset streaming from storage, CPU scheduling, VRAM pressure, synchronization problems and driver defects can look similar in a frame-time graph or to the naked eye.
Signs that compilation is a plausible cause
- The hitch occurs the first time a particular effect, material, enemy ability or location appears.
- Repeating the same route after the game has seen the effect produces a smoother result.
- The pause is accompanied by a brief spike in CPU activity or a visible “compiling shaders” stage at launch.
- Stutter changes after a driver, game, graphics API or Proton update.
Signs that you should investigate elsewhere
- The hitch repeats on every pass even after the same scene has been rendered several times.
- Frame rate falls when VRAM is full, storage activity is high or the CPU is saturated.
- The problem occurs independently of new effects or scene changes.
- Changing shader-cache settings has no measurable effect while another system limit clearly correlates with the pauses.
Keeping pre-caching enabled cannot correct a storage bottleneck, a scheduling problem or a defective driver. Diagnose those causes separately instead of attributing every hitch to shaders.
Independent reader supportYour contribution helps us test, update, and keep practical guides available for everyone.A practical way to test whether pre-caching helps your system
You can compare the two approaches without treating one play session as a universal benchmark. Use the same game build, graphics driver, GPU, graphics API, resolution and graphics settings for both observations.
Quick wins for a faster PC:
Repair Windows errors before they cause bigger problemsFix Now →Fix the driver behind crashes, sound loss and screen glitchesFind Drivers →Clear out junk files and repair common Windows errorsFree Scan →- Record the exact scene or action that causes the hitch, such as entering a named area or triggering a specific visual effect.
- With pre-caching enabled, let Steam finish all visible processing before launching the game.
- Perform the same route twice. Note whether the first encounter hitches and whether the second encounter is smoother.
- Repeat after a controlled change, such as disabling Steam’s shader pre-caching. Do not also change the driver, Proton version or graphics settings.
- Compare frame pacing and the timing of the hitch, not only the average frames per second. A higher average FPS does not prove that a compilation pause disappeared.
- Restore the setting that gives the better result for your use case, then retest after the next game or driver update because cache validity can change.
This method identifies a pattern on your hardware. It cannot produce a percentage that applies to other games or systems, and a single title may contain both well-covered and runtime-generated pipelines.
Best Value
- BREAKTHROUGH PCIe 5.0 PERFORMANCE: Supercharge your workflow and gaming with PCIe 5.0, boasting up to 14,700/13,400 MB/s¹ sequential read/write speeds. Tackle massive files and power up your gaming with Gen5—twice as fast as the 990 PRO SSD.
- EVERY TASK, TURBOCHARGED: Speed past productivity limits. With random read/write speeds up to 1,850K/2,600K IOPS¹, enjoy fast game loads, seamless AI apps, and efficient multitasking. Virtually no lag, no limits—just nonstop performance.
- THINK FAST, CREATE FASTER: With random read/write speeds of up to 1,850K/2,600K IOPS¹, the 9100 PRO SSD fuels seamless AI content creation, swift loads, and smooth gameplay. Work, play, and create at lightning speed.
- SPEED, WHENEVER YOU NEED: From laptops, desktop PCs, to PS5 with added heatsink devices², experience blazing PCIe 5.0 speeds and up to 8TB of storage. Perfect for video editing, gaming, and creative tasks, with the compatibility to match your device.
- STAY COOL, RUN FAST: Push limits, not temperatures. A 5nm controller boosts power efficiency up to 49% over the 990 PRO SSD³, while advanced thermal control keeps performance smooth and reliable.
Launch waits versus gameplay hitches
Pre-caching does not eliminate work; it changes when you pay for it. The cost may appear as a queue before launch, background CPU activity while Steam is open, additional disk usage or network transfer. In-game compilation hides that preparation from the Steam queue but exposes it as a longer launch stage or a pause at the moment a new rendering state is needed.
Choose based on which interruption is less disruptive:
- Choose pre-caching if you usually start a game and play continuously, because a one-time preparation period is less distracting than repeated hitches.
- Choose background processing if your computer is idle between sessions and you want the queue handled before play.
- Consider disabling background processing if you use the machine for CPU-sensitive work while Steam is open and can tolerate compilation pauses.
- Expect to revisit the choice after major updates, since the balance between waiting and runtime compilation can change.
What pre-caching cannot promise
Steam cannot guarantee zero stutter. It cannot prepare a shader that was never included in available cache data, and it cannot safely reuse a binary that no longer matches the current environment. A game may also compile pipelines assembled dynamically from runtime state, even when many ordinary shaders are cached.
Likewise, disabling pre-caching does not guarantee that every game will stutter. Some games compile everything at a deliberate loading screen, ship their own prepared data or encounter only a small amount of runtime work. The setting changes the odds and timing of compilation; the game’s rendering architecture determines the remaining behavior.
Bottom line for common questions
Does Steam shader pre-caching reduce stutter?
Usually, yes for stutter caused by shader compilation, provided the cache contains a valid match. It moves compilation away from the frame that needs the shader.
Is in-game compilation ever better?
It can be preferable when you want to avoid Steam’s background CPU, storage or launch overhead, or when the game’s cache coverage is poor. You accept the possibility of pauses during play in exchange.
Can you skip Steam shader pre-caching?
Yes. Disable the shader pre-caching subsystem in Steam’s settings, but expect the game and driver to perform any required compilation at launch or during gameplay.
What’s actually slowing this PC down?
Pick the symptom - the matching free tool is one click away.
Why does a game still compile shaders after Steam processed them?
The requested object may be outside the cache, or the cache may have been invalidated by a changed game build, driver, GPU, graphics API or Proton/runtime configuration.
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.
