Confirm the symptom
Repeat the same legal game, scene, build and graphics backend. Cache-related stutter often improves on a second pass.
Shader cache troubleshooting
Ryujinx Shader Cache: Purge, Rebuild and Fix Stutter Safely
A Ryujinx shader cache stores compiled graphics work so repeated scenes can become smoother. Purging it can help after corruption, a graphics-backend or driver change, or a reproducible regression, but deleting it for every slowdown usually creates more first-run stutter. This guide shows a controlled backup, purge, rebuild and comparison workflow without downloading unknown shared caches.
$ channel: canary
$ platforms: windows linux macos
$ source: ryubing releases
$ status: verify before download
Independent guide. No keys, firmware, ROMs, DLC or game files are hosted here.
Primary intent
Cache purge and rebuild
Best first check
Repeat the same scene
Main risk
Deleting a healthy cache
Expected result
Temporary recompilation stutter
Safe Ryujinx Shader Cache Purge Order
Record the baseline
Note the Canary version, GPU driver, Vulkan or OpenGL choice, game update, mods and resolution scale.
Back up before deleting
Close Ryujinx completely and copy the relevant cache or user-data folder.
Purge only the suspected cache
Remove only the game-specific cache; do not delete saves, profiles, keys, firmware or the full user directory.
Rebuild with one controlled test
Launch the same scene twice and compare the first pass, second pass and previous cache.
Treat shader cache deletion as a controlled test
Compare the same build, game, scene and graphics backend before and after a cache reset. Do not assume every FPS drop is a cache problem.
What the Ryujinx shader cache does
Ryujinx compiles graphics shaders as a game encounters effects, materials and scenes. A cache keeps reusable compiled results, so a new area or freshly cleared cache can stutter more on the first pass and improve on a repeat. CPU limits, GPU drivers, resolution scale, mods, game updates and emulator regressions can produce similar symptoms.
- Repeat the same legal game, scene, build and graphics backend. Cache-related stutter often improves on a second pass.
- Note the Canary version, GPU driver, Vulkan or OpenGL choice, game update, mods and resolution scale.
When purging the shader cache is justified
A purge is reasonable when the cache may be corrupted, the graphics backend or GPU driver changed, or a specific title shows repeatable artifacts after an update. It is a weak first response to general low FPS, heat, audio or controller problems. Build a baseline first so the result is measurable.
- Repeat the same legal game, scene, build and graphics backend. Cache-related stutter often improves on a second pass.
- Launch the same scene twice and compare the first pass, second pass and previous cache.
Back up, purge and rebuild without losing data
Close Ryujinx and verify no background process remains. Open the normal data location, identify the game-specific shader cache and copy it to a dated backup. Remove only that cache, start the same title with the same settings and repeat the same scene twice. Restore the backup if the clean cache is worse.
- Close Ryujinx completely and copy the relevant cache or user-data folder.
- Remove only the game-specific cache; do not delete saves, profiles, keys, firmware or the full user directory.
- Launch the same scene twice and compare the first pass, second pass and previous cache.
Separate cache symptoms from drivers, settings and builds
Shader compilation usually changes with repetition. Driver or backend issues often affect multiple titles. Resolution or mod problems follow the changed setting. A Canary regression often begins immediately after a build update and can be tested with a separate previous build.
- Ryujinx compiles graphics shaders as a game encounters effects, materials and scenes. A cache keeps reusable compiled results, so a new area or freshly cleared cache can stutter more on the first pass and improve on a repeat. CPU limits, GPU drivers, resolution scale, mods, game updates and emulator regressions can produce similar symptoms.
- A purge is reasonable when the cache may be corrupted, the graphics backend or GPU driver changed, or a specific title shows repeatable artifacts after an update. It is a weak first response to general low FPS, heat, audio or controller problems. Build a baseline first so the result is measurable.
| Symptom | Cache fit | Next controlled test |
|---|---|---|
| Second pass improves | Likely | Repeat unchanged |
| All games stay slow | Unlikely | Check driver and power |
| Starts after Canary update | Possible regression | Compare previous build |
Expect temporary stutter while the cache rebuilds
After a purge, the first pass through effects-heavy scenes may be less smooth because shaders are being compiled again. Judge the result after repeating the same route or encounter. If every run remains equally poor, investigate the driver, backend, scale, power profile, mods and Canary build.
- After a purge, the first pass through effects-heavy scenes may be less smooth because shaders are being compiled again. Judge the result after repeating the same route or encounter. If every run remains equally poor, investigate the driver, backend, scale, power profile, mods and Canary build.
- Launch the same scene twice and compare the first pass, second pass and previous cache.
Avoid unknown shared shader cache downloads
A precompiled cache from Telegram, a file mirror or an unrelated game build can be stale, incompatible or packaged with unsafe files. It may not match your game update, graphics backend, driver or emulator build. This guide does not host or recommend shared caches.
- A precompiled cache from Telegram, a file mirror or an unrelated game build can be stale, incompatible or packaged with unsafe files. It may not match your game update, graphics backend, driver or emulator build. This guide does not host or recommend shared caches.
- Remove only the game-specific cache; do not delete saves, profiles, keys, firmware or the full user directory.
If purging does not help, isolate the next layer
Keep the clean test result and change one layer at a time. Compare Vulkan and OpenGL only when both are supported, verify the GPU driver, disable one mod at a time, return resolution scale to a conservative baseline and compare the current Canary build with a separate known-working build.
- Keep the clean test result and change one layer at a time. Compare Vulkan and OpenGL only when both are supported, verify the GPU driver, disable one mod at a time, return resolution scale to a conservative baseline and compare the current Canary build with a separate known-working build.
- Note the Canary version, GPU driver, Vulkan or OpenGL choice, game update, mods and resolution scale.
Official references and technical context
Verify builds and setup boundaries with Ryubing first-party resources.
FAQ
Where is the Ryujinx shader cache?
Ryujinx compiles graphics shaders as a game encounters effects, materials and scenes. A cache keeps reusable compiled results, so a new area or freshly cleared cache can stutter more on the first pass and improve on a repeat. CPU limits, GPU drivers, resolution scale, mods, game updates and emulator regressions can produce similar symptoms.
How do I purge the shader cache in Ryujinx?
Close Ryujinx and verify no background process remains. Open the normal data location, identify the game-specific shader cache and copy it to a dated backup. Remove only that cache, start the same title with the same settings and repeat the same scene twice. Restore the backup if the clean cache is worse.
Will deleting the shader cache improve FPS?
A purge is reasonable when the cache may be corrupted, the graphics backend or GPU driver changed, or a specific title shows repeatable artifacts after an update. It is a weak first response to general low FPS, heat, audio or controller problems. Build a baseline first so the result is measurable.
Is first-run stutter after clearing the cache normal?
After a purge, the first pass through effects-heavy scenes may be less smooth because shaders are being compiled again. Judge the result after repeating the same route or encounter. If every run remains equally poor, investigate the driver, backend, scale, power profile, mods and Canary build.
Should I download a shared shader cache?
A precompiled cache from Telegram, a file mirror or an unrelated game build can be stale, incompatible or packaged with unsafe files. It may not match your game update, graphics backend, driver or emulator build. This guide does not host or recommend shared caches.