Compatibility

Is There a Nvidium Fabric Version?

Illustration representing mod loader compatibility for Nvidium

Nvidium is available for Fabric and Quilt as a client-side rendering mod. It is not a standalone loader and it does not replace Sodium. The correct setup is a compatible loader, a matching Sodium build and a matching Nvidium JAR for the same Minecraft version.

Fabric support

Fabric is a primary platform for Nvidium releases. Install Fabric Loader for the exact Minecraft version listed by the chosen Nvidium file. The loader itself is separate from Fabric API: having Fabric Loader does not automatically mean Fabric API is installed, and Nvidium does not universally require Fabric API.

Quilt support

The official project also lists Quilt on its supported platform information. Use a Quilt-compatible release and check the dependency metadata for that exact file. Do not assume every Fabric ecosystem combination is automatically tested on Quilt, especially when several rendering mods are installed together.

Sodium is required

Nvidium replaces or extends Sodium's terrain rendering backend and therefore requires Sodium. Compatibility is exact enough that a Sodium update can break an older Nvidium build. Before downloading, compare the Nvidium version's dependency entry with the Sodium JAR already in your instance.

Is Fabric API required?

Not as a universal Nvidium dependency. Some modpacks or companion mods need Fabric API, so it may still be present in a working setup. The safe rule is to install only dependencies listed by the selected Nvidium file and the rest of your mod list, instead of presenting Fabric API as mandatory for every user.

Version-matching checklist

  • Exact Minecraft point release.
  • Fabric Loader or Quilt Loader version.
  • Sodium version required by the Nvidium release.
  • Nvidium JAR built for that game branch.
  • No duplicate old JARs in the instance.
  • Supported NVIDIA mesh-shader GPU and current driver.

Common loader errors

“Incompatible mod set” messages usually identify the expected game or Sodium version. Read the full message rather than repeatedly adding libraries. A crash before the title screen can also come from another rendering mod modifying the same pipeline. Test a minimal profile with only the loader, Sodium and Nvidium, then add other client mods back gradually.

Where to choose the correct build

Match the exact Minecraft version, loader and Sodium dependency listed for the chosen Nvidium build. Keep a record of the working combination before updating.

Minimal compatibility test

When a large modpack fails, duplicate the launcher instance and temporarily remove everything except the selected loader, Sodium and Nvidium. A successful minimal launch proves the core versions can work together. Add performance and rendering mods back one at a time, checking the latest log after each group.

Client-side and server use

Nvidium runs on the client and does not need to be installed on a normal multiplayer server. A server can still restrict client modifications through its own rules, so players should follow the server's policy even though Nvidium changes rendering rather than game mechanics.

Why exact versions matter

Rendering mods interact with internal game code that can change between point releases. A file built for one 1.21.x version may fail on another even when the names look similar. Always use the release filters and dependency list rather than relying on a broad “1.21 compatible” label from a third-party page.

Keep release notes with the profile

Save the selected Nvidium and Sodium version numbers in the launcher instance name or a small text note. When the game updates later, this record shows which combination worked and prevents accidental mixing of files from different branches.