Iris plus Sodium is the setup to use now — it loads OptiFine-style shader packs while staying open-source and compatible with other mods, and OptiFine itself is no longer the safer default.
Install Fabric, then add Sodium and Iris as mods, then drop a shader pack file into the shaderpacks folder and turn it on from Video Settings. That's the whole process on Java Edition today — the older route through OptiFine still exists, but Iris is the one worth setting up first.
Iris is that loader. It's built to run on top of Fabric, and it ships bundled with Sodium, a separate mod that rewrites Minecraft's rendering for speed rather than looks. You install them together, and Iris then reads shader packs the same way OptiFine used to.
For years OptiFine was the only practical way to run shaders, and a lot of older guides still point there. Two things changed that: OptiFine's license is closed and restrictive, and it tends to conflict with the wider Fabric mod ecosystem, which is where most current performance and content mods live. Iris was built specifically to solve both — it's open-source, and it was designed from the start to sit alongside Sodium instead of fighting it.
The trade-off is compatibility depth: Iris aims to run existing OptiFine-format shader packs, and mostly succeeds, but a pack built for very old OptiFine-specific features can still behave differently or not load at all. If a specific pack refuses to run under Iris, that's the one case where trying it under OptiFine instead is a reasonable fallback — just don't run both loaders installed at once, since Iris, Canvas and OptiFine-style renderers are not meant to coexist and will crash the game.
.zip, straight into the shaderpacks folder inside your Minecraft installation. Iris adds this folder automatically once it's installed; there's also a button that opens it directly from the in-game menu described below.Nothing here touches your world files or your .minecraft saves folder, so there's no risk of losing a world by getting a step wrong — worst case, a pack doesn't load or the game needs a restart.
Shaders are not free. Even with Sodium doing the heavy lifting on the vanilla side of rendering, a shader pack adds real GPU work on top — some current packs implement path tracing and full global illumination, which is a genuinely different workload from lighting a few blocks and calling it done. A light shader pack on decent hardware can run close to vanilla framerates; a heavy one on modest hardware can cut your frame rate hard, especially across open biomes with a lot of sky and foliage to light. If you've just gotten your setup fast enough to comfortably run a long session mining for diamonds, expect to give some of that margin back once shaders are on.
No — not in the way Java players mean it. Since Bedrock Edition 1.18.30, third-party shader packs bundled in resource packs stopped working across the board, a change tied to Bedrock's RenderDragon renderer. What Bedrock has instead is a built-in deferred rendering pipeline, exposed through official resource packs on supported devices, which can adjust lighting, fog and PBR materials — but that's Mojang-controlled visual tuning, not installing an independent third-party shader pack the way Iris or OptiFine do on Java.
None of this is supported by Mojang either way: shader packs and the mods that load them are third-party software, and running them is outside official support regardless of edition.