Key takeaways
- Iris needs three things: a mod loader, Sodium, and a shader pack – in that order.
- Shader .zip files go in the shaderpacks folder and are never unzipped.
- If the frame rate is bad, lower render distance and shadow distance before changing pack.
Installing shaders used to mean installing OptiFine and accepting that half your mod list would stop working. Iris ended that, and the install is now short enough to write out in one page.
This is the whole process, in order, with the parts that people get wrong called out as they come up.
Before you start
You need Minecraft Java Edition and a mod loader – Fabric or NeoForge. If you have never installed one, the easiest route is a launcher that does it for you: the Modrinth App or Prism Launcher will create the profile, install the loader, and manage the mods folder.
You do not need OptiFine, and you should not install it alongside Iris. They do the same job and will fight.
The five steps
1. Install the loader
Run the Fabric or NeoForge installer for your Minecraft version, or create the profile in your launcher. Launch the game once so the profile finishes setting itself up.
2. Install Sodium
Iris requires it. Download the Sodium build that matches both your Minecraft version and your loader, and put the jar in the mods folder.
3. Install Iris
Same folder, same rules – match the Minecraft version and the loader. Launch the game. If it boots to the main menu, the hard part is done.
4. Add a shader pack
Download a pack from Modrinth’s shaders section. Put the .zip in the shaderpacks folder inside your game directory without extracting it. Extracting it is the single most common mistake, and the pack simply will not appear in the list.
5. Turn it on
Video Settings, then Shader Packs. Select the pack and it applies immediately – no restart. If the screen goes dark or the world turns into static, your GPU driver is out of date more often than the pack is broken.
What Iris is doing
Worth thirty seconds of context before the settings section. Iris is a shader loader, not a shader. On its own it changes nothing about how the game looks – it replaces Minecraft’s rendering path with one that can read and execute shader packs written in the OptiFine format, which is why a decade of community packs work in it without being ported.
That also explains the Sodium dependency. Iris is built on top of Sodium’s renderer rather than beside it, so the optimised pipeline is doing the work underneath the shader stages. It is the reason shaders on Iris frequently run better than the same pack did on OptiFine.
Picking a first pack
Start with something vanilla-faithful rather than cinematic. Complementary Reimagined is the usual first choice because it keeps Minecraft’s colours and runs well; BSL if you want more colour; MakeUp Ultra Fast if your machine is the constraint.
The full shader pack comparison goes through five packs and what each is good at. What matters for a first install is picking one that will not make you conclude shaders are impossible on your hardware.
Where the files go
Two folders inside your game directory matter. The mods folder holds jar files – the loader, Sodium, Iris and anything else. The shaderpacks folder holds shader .zip files. Putting a shader zip in the mods folder is the second most common mistake after extracting it, and it produces a crash rather than a missing entry.
If you cannot find the game directory, every launcher has a button for it – usually next to the profile name. On a default Windows install it is the .minecraft folder in AppData/Roaming.
The two settings that matter
Render distance is the single biggest cost, and it is a vanilla setting rather than a shader one. Dropping from sixteen chunks to ten will buy back more frames than any pack change.
Shadow distance is the shader-side equivalent, and most packs let you set it separately. Halving it costs very little visually and a great deal less GPU time. Between those two you can usually make any pack playable.
Per-pack settings
Each shader pack ships its own options, reachable from the same Shader Packs screen once a pack is selected. That menu is where bloom, water styling, shadow quality and colour grading live. Turning two or three of those down is usually less painful than dropping to a lighter pack, and it is the step most people skip.
When it does not work
The pack does not appear in the list: it is extracted, or it is in the wrong folder. The game crashes on launch: version mismatch between Minecraft, loader, Sodium and Iris – check all four. The world renders black: driver update, then try a different pack.
Everything is fine but slow: that is not a bug, that is the pack. Shaders are expensive and a mid-range GPU running a cinematic pack at high render distance is doing genuinely hard work. What Sodium is doing underneath is the only reason it runs at all.
One last note for modpack users: if your pack already ships a shader loader or a performance stack, install nothing yourself and use what is there. If you are assembling the stack yourself, the wider performance mod list covers what else belongs in the folder. Two rendering mods in the same profile is a broken profile.