Minecraft Shaders Not Working: Fixes

Iris runs on the Fabric loader and bundles Sodium for rendering. Because everything is version-locked, a single mismatched file is enough to stop shaders loading. Run down this list in order — most "shaders not working" reports on Iris are one of these:

• Versions all match. Fabric, Iris, Sodium, and the Minecraft version must all be built for the same release (for example all on 1.21.x). A mod built for a different version silently fails to load.
• You launched the Fabric profile. In the launcher, pick the fabric-loader profile, not the default Minecraft entry. Launching vanilla means no Iris, so no Shader Packs button appears.
• The mods are in .minecraft/mods. Both the Iris and Sodium .jar files belong directly in the mods folder — not in a sub-folder, and not still inside a downloaded archive.
• No duplicate or conflicting mods. Two copies of Sodium, an old Iris build, or OptiFine sitting in the same mods folder will conflict. Keep one current copy of each.
• You are not also running OptiFine. Iris and OptiFine do not coexist in one profile. Remove OptiFine from the Fabric mods folder.

If Iris loaded correctly you will see a Shader Packs button under Options → Video Settings. If that button is missing, Iris itself did not load — recheck the version match and the mods folder before touching the shaderpack. A clean walkthrough of the whole setup lives in how to install Minecraft shaders, and the install guide covers the launcher side.

OptiFine is the all-in-one option, but it fails in its own familiar ways. If shaders are not working on OptiFine, check these:

• OptiFine matches your Minecraft version. Download the OptiFine build for your exact version. An HD U release for the wrong version will not produce a working profile.
• Java is installed. The OptiFine installer is a .jar and needs Java on your system to run. If double-clicking it does nothing, install Java (or open the .jar with it), then run the installer again.
• You selected the OptiFine profile. After installing, an OptiFine entry appears in the launcher. Shaders only work when you launch that profile, not the vanilla one.
• Use the Shaders menu, not just Video Settings. On OptiFine the option is Options → Video Settings → Shaders. The Shaders… button there is where packs are listed and selected.
• Forge users: versions must line up. If you run OptiFine as a mod on Forge, OptiFine and Forge must both target the same Minecraft version, or the game will crash or drop OptiFine on launch.

Still deciding which loader to commit to? Our Iris vs OptiFine comparison weighs performance, features, and how quickly each updates after a new Minecraft release.

The loader is working, the shader menu opens — but your pack is not in the list. This is the most common single complaint, and it is almost always one of three things:

1. The file is unzipped. A shaderpack is loaded as a .zip. If you extracted it, the loader may not see it (and a double-zipped pack.zip inside another folder is just as bad). Keep the original .zip as downloaded.
2. It is in the wrong folder. The .zip must sit directly inside shaderpacks — not in resourcepacks, not in mods, and not in a sub-folder you created. On Windows the path is %appdata%\.minecraft\shaderpacks.
3. The menu was not refreshed. If you added the file while the menu was open, press the refresh button or close and reopen the shader menu so it rescans the folder.

The reliable way to land the file in the right place is to open the menu first and click Open Shader Pack Folder — that button opens the exact folder the game reads, so you cannot miss it. Drop the .zip in, refresh, and it should appear. If the menu itself is missing, the problem is the loader, not the pack — go back to the checklist above.

The pack is selected but the screen goes black, the world will not render, or the game crashes outright. These point at the shader actually trying to run and failing, so the fixes are different from a missing pack. Try them roughly in this order:

• Update your GPU drivers. This is the single most common fix for black screens and shader crashes. Install the latest driver for your card (NVIDIA, AMD, or Intel) and restart, then try again.
• Try a different or lighter shaderpack. A pack built for a much newer or older shader loader can fail to compile and render black. Test with a well-known pack on a Low or Medium preset to rule out a single bad pack.
• Lower the load. Reduce render distance and drop the shader's shadow resolution and quality preset. A black screen or hard crash can be the GPU running out of memory under a heavy pack plus a high-resolution texture pack.
• Check your hardware supports it. Shaders need a GPU with modern OpenGL support. Very old or basic integrated graphics may not be able to run a given pack at all.
• Read the crash log. If the game crashes, the launcher or the crash-reports folder names the mod or shader involved. That line usually tells you exactly which file to update or remove.

If shaders run but everything looks wrong rather than broken — surfaces flat, oddly shiny, or missing depth — that is typically a texture issue, not a shader one. See why textures look flat or shiny, which comes down to whether your pack ships PBR maps for the shader to read.

If you have worked through both checklists and shaders still will not run, do a clean reset rather than guessing — it clears the tangled-mods case that causes most stubborn failures:

1. Start from a clean profile. Remove every mod from .minecraft/mods, then add back only Iris (with its bundled Sodium) for your exact Minecraft version. Confirm vanilla shaders work before stacking anything else on top.
2. Reinstall the loader. Run the Fabric (or OptiFine) installer again for the correct version, and make sure the launcher is pointed at that fresh profile.
3. Test one shaderpack at a time. Add a single known-good .zip, on a low preset, with a modest render distance. Once that works, reintroduce other mods and packs one by one to find the conflict.

Worth remembering: shaders and texture packs do separate jobs. A shader handles lighting while the texture pack supplies the surfaces. If your goal is a realistic look, Optimum Realism is a photorealistic PBR pack built to pair with shaders on Java — its normal and specular maps give shaders real depth and reflections to work with — and it also supports Bedrock RTX. The 64x base resolution is free; higher resolutions are available through Patreon. Install it like any resource pack (see the install guide), then enable a shader on top — the shaders page lists recommended pairings, and the FAQ answers common setup questions. You can browse every how-to and explainer on the info hub.