If shaders aren't showing up at all, a shader pack file on its own does nothing. Minecraft Java needs a separate renderer, Iris or OptiFine, before a shader pack changes anything in-game, and that single missing piece explains most of the failures below. Bedrock works differently again, and we cover that separately further down.
You don't have a shader loader installed
This is the most common reason shaders don't work. A shader pack is just a set of files, it needs a renderer built to read them. On Java that means Iris paired with Sodium for performance, or OptiFine for older setups and specific legacy packs that still expect it. Without one of those installed, the video settings menu has no shaders option at all, and dropping a shader pack into the shaderpacks folder changes nothing by itself.
If you haven't installed a loader yet, that's the fix. Follow our shader install guide for the Java and Bedrock setup steps, then come back here if something still isn't working once the loader is in.
The shaderpacks folder doesn't exist
Minecraft only creates the shaderpacks folder inside .minecraft after you launch the game at least once with a shader loader installed. Looking for the folder before that first launch, or dropping a shader pack into a fresh install with no loader, means the folder simply isn't there yet. Launch the game once with Iris or OptiFine active, let it reach the main menu, close it, and the folder appears.
The shader pack doesn't match your loader or game version
Shader packs are frequently built for a specific version range, both of the loader and of Minecraft itself. A pack built for an older Iris release can fail to load, render broken, or crash outright on a newer one, and the same goes for packs pinned to a specific Minecraft version. Check the pack's listed compatible versions against your installed loader and game version before assuming the pack itself is broken.
The pack is in the wrong folder or still zipped
- Shader packs go in shaderpacks, not resourcepacks. The two folders look similar, but the game only reads shaders from the one built for them.
- Leave the download zipped. Most loaders read the .zip file directly, and unzipping it usually breaks the pack instead of installing it.
- Check that the file landed directly inside shaderpacks, not inside a nested folder created when an archive tool extracted it automatically.
Your GPU or drivers can't keep up
Outdated graphics drivers are a common, unglamorous cause of shaders failing to load or crashing right after launch, so update them before digging further. Integrated graphics and older dedicated GPUs also just can't run heavier packs, and that's not a bug to fix, it's a real hardware ceiling. If a pack like Complementary Unbound crashes or tanks your frame rate, the pack is doing what it's built to do on hardware it was never built for. Potato Shaders is our pick when the goal is running something on weak hardware rather than chasing the heaviest look.
Iris and OptiFine are fighting each other
Installing both Iris and OptiFine at once is a common source of crashes and broken rendering, since both try to hook the same rendering pipeline. Another mod that touches rendering, a competing shader loader, a resource pack manager, or an incompatible optimization mod, can cause the same kind of conflict. Keep exactly one shader loader installed, and check your mods folder for anything else that touches rendering before ruling this out.
Bedrock shaders work differently, and often don't work at all
Bedrock Edition has no official shader support the way Java does. Its old RenderDragon visual overhaul path is deprecated, and most packs sold or shared as "Bedrock shaders" are really resource packs or Marketplace add-ons faking lighting effects rather than a true shader pipeline, so support varies by device and Bedrock version with no single fix we can honestly give you. iOS in particular is limited: Apple's platform restrictions mean iOS Bedrock generally can't run the resource-pack style shader effects that work on Windows or Android. If a Bedrock shader pack shows no effect on your device, the likely answer is that your platform was never going to support it, not that you did something wrong.
Frequently asked questions
Why don't shaders show up in my video settings?
Vanilla Minecraft never has a shaders option in video settings. That option only appears once you've installed a shader-capable loader such as Iris or OptiFine. If you see no shaders entry anywhere in your settings, the loader isn't installed yet, follow our shader install guide to add one.
Why is there no shaderpacks folder in my .minecraft directory?
The folder is created by the shader loader the first time you launch the game with it installed, not by Minecraft itself. If you haven't launched at least once since installing Iris or OptiFine, the folder won't exist yet. Launch the game once, let it fully load to the main menu, and check again.
Why does Minecraft crash when I load a shader pack?
Crashes on loading a shader pack are usually a version mismatch between the pack, your loader, and your Minecraft version, or a GPU that can't handle the pack's demands. Outdated graphics drivers cause the same symptom. Update your drivers first, then confirm the pack's listed compatible versions match your setup before trying a lighter pack instead.
Do Minecraft PE shaders work on iOS?
Barely, and often not at all. Bedrock has no true shader pipeline on iOS the way Java does, so most "PE shaders" for iPhone and iPad are resource packs simulating lighting effects, and even those are more limited on iOS than on Android or Windows because of Apple's platform restrictions. Treat any claim of full shader support on iOS with real skepticism.
