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. Installing Sodium on its own doesn't add shaders either, it's a performance mod, not a shader loader. Bedrock works differently again, and we cover that separately further down.
- No shaders option anywhere in Video Settings: install Iris or OptiFine, a shader pack file alone won't add the menu.
- Sodium is installed but the shaders menu still isn't there: Sodium only boosts performance, add Iris alongside it.
- The shaderpacks folder is missing: launch the game once with the loader active so Minecraft creates it.
- A pack won't load, renders broken, or crashes on load: match the pack's listed Iris and Minecraft version to your install.
- A pack loads but crashes later or tanks your frame rate: that's a GPU limit, not a bug, try a lighter pack instead.
- Bedrock shows no shader-style effect: turn on Vibrant Visuals in Video Settings, some devices don't meet the hardware requirement.
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: current Iris builds for Fabric, NeoForge, and Quilt list Sodium as a required dependency, so the two install together. OptiFine still covers older setups and specific legacy packs that expect it. Without one of those loaders 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.
You installed Sodium but not Iris
Sodium is a rendering-performance mod. It doesn't touch shaders and never adds a shaders option to Video Settings on its own, so if a setup guide only mentioned Sodium, that's the gap. Add Iris as well: current Iris builds for Fabric, NeoForge, and Quilt require Sodium as a dependency, so the two are meant to run together, not as substitutes for each other. Put both jars in your mods folder for the same Minecraft version and loader, and the shaders option appears in Video Settings.
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. Iris itself spans Minecraft 1.16.5 up through current 26.x releases across Fabric, NeoForge, and Quilt, but a pack built for an older Iris release can still 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. Complementary Reimagined trades some of that ceiling for a lighter load, and Potato Shaders is our pick when the goal is running something on genuinely weak hardware. See our Minecraft lag and FPS guide if the slowdown isn't only about shaders.
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 means Vibrant Visuals, and it needs the right hardware
Bedrock Edition's official shader-style upgrade is called Vibrant Visuals, a new rendering pipeline with real-time lighting, reflections, and shadows that Mojang ships as a cosmetic graphics mode, it doesn't change gameplay. It's available on Xbox Series X|S, Xbox One, PlayStation 4 and 5, Android, iOS, and PC, and on a supported device it's the default already. Turn it on, or check it's on, from Video Settings under the Graphics Mode dropdown. If that toggle is greyed out, your device's hardware doesn't meet the requirement, that's a per-device limit, not an iOS-wide block. There's no separate file to download for it: most packs sold or shared online as "Bedrock shaders" are really resource packs or Marketplace add-ons simulating similar lighting rather than a true rendering pipeline like Vibrant Visuals or Java's Iris. See our Minecraft Bedrock shaders guide for a full device-by-device rundown.
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, and Sodium alone doesn't add it since Sodium is a performance mod, not a shader loader. If you see no shaders entry anywhere in your settings, 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.
Why does Iris say it needs Sodium, or my shaders menu is still missing?
Current Iris builds for Fabric, NeoForge, and Quilt list Sodium as a required dependency, so installing Iris alone on a current Minecraft version can leave the shaders menu missing until Sodium is added too. Put both mod jars in your mods folder for the same Minecraft version and loader, then relaunch.
Do Minecraft PE shaders work on iOS?
Yes, if the device meets the requirement. Vibrant Visuals, Bedrock's official graphics upgrade, is supported on iOS as well as Android, Xbox, PlayStation, and PC. It's a graphics mode you turn on in Video Settings under Graphics Mode, not a shader pack file. If the toggle is greyed out, that device's hardware doesn't meet Vibrant Visuals' requirement, it isn't an iOS-wide block.
