Learn how to delete the X-Plane 12 shader cache safely, rebuild it automatically, and avoid common folder and post-rebuild stutter mistakes.
To delete the X-Plane 12 shader cache, quit the simulator completely, open its installation folder, then delete or rename Output/shadercache. Start X-Plane again and it will create a fresh cache automatically. The first flight afterwards may stutter while shaders are compiled again; aircraft, scenery and preferences are unaffected.
How do I clear the X-Plane 12 shader cache safely?
- Close X-Plane completely. If it crashed, check that no X-Plane process remains open before changing the folder.
- Find the active X-Plane 12 installation. Open the folder containing the X-Plane application and its
Outputfolder. This matters if you keep more than one copy of X-Plane. - Open
Output. Locate the folder namedshadercache. - Rename or delete it. Renaming it to
shadercache-oldis our preferred troubleshooting method because it preserves the old files temporarily. Deleting the folder has the same effect. - Restart X-Plane 12. The simulator will generate a new
shadercachefolder as required. - Remove the renamed copy later. Once X-Plane starts and renders correctly,
shadercache-oldis no longer needed.
Delete only Output/shadercache, not the entire Output folder. The latter contains other data, including preferences and saved simulator information.
When should I delete the shader cache?
Clear it when shader corruption is a credible cause, not as routine maintenance or a general performance tweak.
| Situation | Clear the cache? | Reason |
|---|---|---|
| Broken graphics or shader-related errors after an update or driver change | Yes | A clean rebuild can replace incompatible or corrupt cached data. |
| Repeated Vulkan device-loss errors | Try it once | It is a useful isolation step, but cache deletion alone may not fix the underlying driver, plug-in or hardware problem. |
| Regular stuttering with no other symptoms | Usually not first | Rebuilding shaders can temporarily increase stutter. |
| A new graphics driver with no problems | No | X-Plane and the driver normally manage their generated data without manual intervention. |
For graphics-backend context, see our explanation of how Vulkan is configured in X-Plane 12. If the simulator reports device-loss errors, use the cache reset alongside our Vulkan device-loss troubleshooting steps, rather than treating it as a complete fix.
What happens after the shader cache is rebuilt?
The new cache starts largely empty, so X-Plane may compile shaders as different aircraft, weather conditions and scenery appear. Brief pauses or extra stutter during the first flights are therefore expected and should lessen as the cache is populated.
Repeatedly deleting the cache prevents that benefit. If stuttering continues after several comparable flights, investigate scenery, plug-ins, frame-time limits and graphics settings instead; our guide to diagnosing persistent X-Plane 12 stutter covers those causes.
What if the shadercache folder is missing or cannot be deleted?
A missing folder usually means it has already been removed, has not yet been generated, or you opened the wrong X-Plane installation. Launch the copy you actually use, close it, and check that installation's Output folder again.
If the operating system says the folder is in use, an X-Plane process is still running. Close it or restart the computer, then rename the folder before launching the simulator again. The folder returning afterwards is normal and confirms that X-Plane rebuilt it.
If a fresh cache does not change the fault, stop clearing it and test the next likely cause. For problems that began with legacy OpenGL plug-ins, use our Zink plug-in bridge troubleshooting to separate a plug-in compatibility problem from a damaged shader cache.