Fabric API and Shaders: Using Iris and Sodium With Your Mods
How shaders fit into a Fabric setup: what Iris and Sodium do, whether Fabric API is involved, installing shader packs, and the performance settings that keep them smooth.
On This Page
Shaders are the mod category that makes screenshots famous: real shadows, waving water, light that behaves like light. They are also the category that confuses Fabric players most, because the famous names in the shader world are rendering mods with their own requirements, sitting beside the library rather than inside it.
The division of labour is clean once stated. The library supports the mods that ask for it. Sodium rebuilds the rendering engine for speed. Iris adds shader pack support on top of Sodium. Your job is simply to install the right stack for your game version and feed it a shader pack.
A working setup in this area rests on:
- Sodium, for rendering performance
- Iris, for shader pack support, usually paired with Sodium
- A shader pack file, placed in the shaderpacks folder
- The library, present when your other mods require it
For the foundation this builds on, read the the Fabric API homepage.
For the companion walkthrough, read the Fabric API Best Settings Guide.
Who Does What
Sodium replaces large parts of the game's rendering with a faster design and is the foundation almost every modern Fabric graphics setup starts from. Iris builds on it to load shader packs, the files that define a particular look.
Neither replaces the library, and the library powers neither. They coexist in the same mods folder because different mods ask for different support, which is the Fabric pattern everywhere.
Install order saves evenings: optimise first, verify plain performance, then shaders. A shader pack blamed for slowness that plain rendering already had is the classic misdiagnosis, and the two step order makes it impossible.
Installing the Stack
Install in dependency order: confirm your base setup launches, add Sodium for your game version, launch again, then add Iris, which will state its Sodium requirement plainly if the version pairing is wrong.
Shader packs are not mods and do not belong in the mods folder. They live in the shaderpacks folder the game creates once Iris runs, selected afterwards from the video settings screen.
Internal settings inside shader packs deserve the same less is more discipline as mods: disable the cinematic extras first, keep shadows and light quality, and raise luxuries one at a time across several sessions rather than in one greedy pass.
Version pairing matters most between Iris and Sodium. Their pages publish compatibility for each release, and matching them exactly prevents the commonest shader setup failure.
Choosing a Shader Pack
Packs range from gentle enhancements that keep the game's character to cinematic rebuilds that demand serious hardware. Start gentle: a light pack proves the stack works and teaches the settings menus without melting anything.
Judge a pack by its behaviour in motion, in your own world, at your settings. Screenshots are advertisements; your frame rate is the review.
Fabric API's part in shader setups is quiet but real: the loaders and performance mods around it are what give shaders their headroom, and a stable modded base is the difference between a shader showcase and a slideshow.
Performance Settings That Matter
Shadows and render distance are the two hungry settings in any shader setup. Lower shadow resolution first for the largest gain at the smallest visual cost, then trim render distance to what your machine sustains steadily.
Steady beats spectacular. A locked, calm frame rate at moderate settings feels better than a beautiful slideshow, and the general tuning approach in the performance guide applies to shader setups unchanged.
- Lower shadow resolution first
- Trim render distance to a steady level
- Close other heavy programs
- Judge settings in motion, not screenshots
Shaders and Your Other Mods
Most content mods coexist with shaders happily, because they change different layers of the game. The friction appears with mods that render custom effects, where a shader pack may draw them oddly or not at all.
When a visual oddity appears, toggle the shader pack off for one launch. If the oddity vanishes, the pairing is the cause, and the mod or pack page usually documents the setting that reconciles them.
Frequently Asked Questions
Do shaders need Fabric API?
Shaders run through Iris and Sodium rather than the library. Keep the library installed when your other mods require it; the stacks coexist in the same mods folder without conflict. That is Fabric API behaving normally.
Where do shader packs go?
In the shaderpacks folder, not the mods folder. Iris creates and reads that folder, and packs are selected from the video settings screen inside the game. Fabric API is designed to work exactly that way.
Why is my frame rate low with shaders?
Shadows and render distance are the usual costs. Lower shadow resolution first, then trim render distance until the rate is steady; a calm rate beats a spectacular slideshow. In short, Fabric API is doing its job when that happens.
Can I use shaders on a server?
Shaders are client side visuals, so they work for you in any world, including servers, without the server needing anything. Other players simply see the standard game. That is the expected behaviour with Fabric API installed.
Conclusion
Fabric API and Shaders comes down to the same discipline as the rest of a healthy Fabric setup: match versions exactly, change one thing at a time, and keep a written record of what you installed.
Follow that discipline and this part of your setup stops producing surprises, leaving the library to do its quiet work underneath the mods you actually play.
