← Back to blog Indium Mod guide

Indium Mod and Sodium Compatibility: What to Check

Understand the relationship between a performance renderer and the rendering APIs other Fabric mods may expect.

Interlocking modules representing Indium Mod and Sodium compatibility

Think in layers, not isolated mods

A performance renderer can change how Minecraft handles graphics internally, while other Fabric mods may expect a rendering API to expose specific behavior. Indium has historically been used as a bridge in setups where those expectations need to meet.

That means compatibility is not a yes-or-no property of one file. It depends on the versions and behavior of the full graphics stack.

Check whether your current stack still needs it

Mod ecosystems evolve. Features that once required a separate compatibility layer may change across major releases. Before installing by habit, review the requirements of the exact mods and versions you are using.

If nothing in your pack needs the extra rendering compatibility, fewer components can mean a simpler setup.

  • Read the requirements of rendering-dependent mods
  • Check release notes after major game updates
  • Avoid keeping legacy components without a reason

Version mismatch symptoms

A bad match can show up as an immediate loader error, a crash during startup, or rendering defects that appear only in a world. The symptom alone is not enough to identify the file at fault.

Use the log to look for explicit dependency ranges, mixin errors, missing classes, or messages that name two incompatible components.

Build a minimal compatibility test

Create a temporary profile with Fabric Loader, the performance renderer, Indium when required, and one mod that needs the rendering feature you are testing. If that works, add the rest of the pack in batches.

This method is faster than randomly deleting files from a large mod folder because every test answers a specific question.

Retest after every major update

When Minecraft, Fabric, or your graphics mods receive major updates, assume the old compatibility result is no longer guaranteed. Recreate the minimal test before migrating a large world or production modpack.

A few minutes of controlled testing can prevent hours of troubleshooting later.

Practical note: Compatibility changes between releases. Verify the exact requirements for the Minecraft, Fabric, and rendering-mod versions in your own instance before making changes.