SCSKiller: the free tool taking on shader compilation stutter
A single-developer open-source Windows app pre-compiles your games' shaders into the driver cache before you play, and Digital Foundry and Hardware Unboxed both put it through real tests within two weeks of each other.
Shader compilation stutter has outlived every driver update, every engine patch and every Microsoft initiative thrown at it, so when a free tool claims to kill it for the games already in your library, it deserves a closer look. SCSKiller, a Windows utility by a developer going by BlueHeisenberg, has sat on GitHub since late September and now holds roughly 4.3k stars as of publication. On November 3, Digital Foundry published a full video on it titled "SCSKiller - The Beginning Of The End For PC #StutterStruggle?", and Hardware Unboxed covered the same tool on October 10 with "Can A Simple App Really Fix PC Game Stutters?". Two of the most performance-focused channels on YouTube reaching the same subject within two weeks is rare, and both came away calling it legitimate, with caveats.
This guide explains what the tool does, how it relates to the official pipeline work like Advanced Shader Delivery, how to run it, and where its limits are. Everything here comes from the project's README and website, plus reporting from Digital Foundry and Hardware Unboxed. We have not benchmarked it ourselves; see the section at the end for exactly what that means.
What SCSKiller actually does
When a game hits an effect the driver has not seen yet, the driver compiles the shader for your specific GPU on the spot, and the frame waits for the compile to finish. That pause is shader compilation stutter. Games ship shader bytecode, ready-made GPU code, so the compile is unavoidable unless the pipeline gets built ahead of time.
SCSKiller reads the shaders a game ships with, works out which pipeline state objects the game will create, and compiles them into the GPU driver's own shader cache while the game is closed. The compile runs in a separate process, so nothing happens mid-game. When you launch the game, the driver finds the compiled pipelines waiting in its cache and reuses them instead of building them during play.
The app is free and open source under GPL-3.0-or-later, written in C#, and the code has been public since the project started. It targets Windows 10 (version 2004) or 11, 64-bit. DirectX 12 games are supported on both NVIDIA and AMD; DirectX 11 support covers NVIDIA only. Intel GPUs are unsupported for now, because the developer has none to test on.
What it fixes, and how it relates to ASD
SCSKiller fixes one specific category of hitch. Traversal stutter, asset streaming hitches and frame pacing problems from other causes stay exactly where they were. Digital Foundry's testing made the same point: Star Wars Jedi: Survivor kept its streaming-related stutter even after shader compilation was dealt with.
That scope is also what separates it from Advanced Shader Delivery, Microsoft's approach that Epic folded into Unreal Engine 5.8.4 in October. With ASD, the developer generates the pipeline database ahead of time and stores ship it alongside the game, so the player's PC skips the compile entirely, assuming the driver and storefront cooperate. We covered that in detail in our piece on Unreal Engine 5.8 embracing Advanced Shader Delivery.
The two approaches sit at different ends of the pipeline. ASD moves the work upstream to developers and stores, which helps new releases but does nothing for the back catalogue, and it has already shown fragility in the wild: NVIDIA's 621.12 hotfix driver dropped ASD support entirely, as we covered when S-GAME told Phantom Blade Zero players to roll back their Nvidia drivers. SCSKiller moves the work sideways to the player's own machine, on their schedule, for any DX12 game in their library. The README says its library view marks games whose engine prepares its shaders itself, so where the official path already covers you, the tool stays out of the way. Both can matter in the same library: ASD for a new UE 5.8 release, SCSKiller for everything the store never shipped shader data for.
How to use it
The steps below follow the project README.
- Download SCSKiller-Setup.exe from the Releases page on GitHub and run it. It installs for your user only, needs no admin rights, and updates itself. A portable zip exists if you prefer a folder you control.
- Open SCSKiller. It scans for games in Steam, Epic Games, EA app, GOG, Ubisoft Connect, Xbox (PC), Battle.net, PURPLE, HoYoPlay, Gaijin and the Riot Client, and you can add anything it misses by hand. It reads the shader files each game ships with.
- Queue the games and press Compile. The README suggests "Add all recommended" as a starting point, which puts games known to stutter at the top of the list. Keep the game closed while its queue entry compiles.
- Play. SCSKiller can be closed once the compile is done; the compiled pipelines live in the driver's cache, and the app touches neither game files nor driver settings. Left open, it verifies that the compile reached the cache the game actually uses.
If a game's pipelines cannot be worked out from its files alone, turn on the optional recorder, play for a few minutes, then compile. The recorder also produces a frame-time graph for the session on the game's page, with shader stutters marked separately from other hitches. Those graphs stay on your PC.
What Digital Foundry and Hardware Unboxed found
Digital Foundry tested on a Ryzen 5 5600 with an RTX 4070 Ti Super across a range of titles. Per its video, Silent Hill F showed a clear and visible improvement, and RoboCop's roughly two-second freeze disappeared once compilation moved out of gameplay. The video also spends a section on the trade-offs: pre-compilation costs time, storage and memory, and Jedi Survivor demonstrated that streaming stutter survives the treatment. The channel credited Digital Foundry's own Alex Battaglia and his #StutterStruggle series as the inspiration BlueHeisenberg cited for building the tool. Digital Foundry's summary was that some results are clearly remarkable, with significant limitations and trade-offs alongside.
Hardware Unboxed tested the tool in Jedi Survivor, Tiny Tina's Wonderlands, Silent Hill: Townfall and Grounded 2, per TweakTown's write-up of the video, which credited SCSKiller with roughly a 25% performance improvement in Jedi Survivor and called it a proven way to remove shader compilation stutter in the titles tested. Neither channel found the tool harmful; both found it narrower than the name suggests.
The developer's own README numbers are more dramatic, and worth reading with the source in mind: about five minutes of play per game measured from a cold cache, comparing before and after. Final Fantasy VII Rebirth on an RTX 5090 went from 19 stutters of 20 ms or more to zero, with the worst stall dropping from 76 ms to 5 ms. Hogwarts Legacy on the same GPU went from 1,014 stutters to 87 and its worst stall from 2,400 ms to 100 ms. Those are the project's own measurements, taken with its recorder; your hardware, settings and driver will land elsewhere.
Things to know before you run it
Releases are not code-signed yet. The first run will probably trigger a SmartScreen warning on Windows, which you clear through More info and Run anyway, and the README recommends verifying the download's SHA-256 against the value in the release notes. Windows 11's Smart App Control blocks unsigned apps outright with no override. The release cadence tells its own story: v1.4.4 landed on November 3, v1.4.5 followed days later, and a v1.4.6 tag appeared hours before publication.
Driver updates wipe the shader cache, and every wiped cache means recompiling every game. SCSKiller can redo that automatically if you allow it, and this is the maintenance cost that official, store-delivered shader data avoids. Storage is the other cost: pipeline caches for large games reach into many gigabytes, and a TechSpot community thread discussing the tool notes AMD's DX12 driver cache tops out at 16 GB with no adjustable setting, with one commenter measuring 13.6 GB for full coverage of Oblivion Remastered alone.
On anti-cheat, the tool's behavior is deliberately conservative: for games with anti-cheat it reads files only, never launching, injecting or recording. The exceptions are explicit and user-confirmed per game: an offline session without EasyAntiCheat for ELDEN RING and ARMORED CORE VI, or an opt-in recorder setting for other supported games that the README flags as your own risk. Bans from using it are excluded from the project's support.
What we did not test
We have not installed SCSKiller, run frame-time captures, or reproduced any of the numbers above. The measurements quoted here come from the developer's README, Digital Foundry's video and Hardware Unboxed's video, cited as such. Whether the tool holds up across a full library, how long compiles take on mid-range CPUs, and how much disk the caches consume on a real drive are all things we would need to measure before making claims, and this piece deliberately makes none. If we do run our own comparison, it will get its own article with the method spelled out.
