Fabric Mod Installed on Forge

A Fabric mod was installed on a Forge server, which cannot read it. Fabric and Forge use different formats, so a Fabric mod simply will not load on Forge.

What does this error mean?
A 'ModLoader mismatch: expected Forge' error means a Fabric-format mod was found on a Forge server. Forge looks for its own mod metadata and does not understand Fabric's fabric.mod.json, so the mod is rejected.
ModLoader mismatch: expected Forge
Most Common Causes
  • Downloading the Fabric build of a mod for a Forge server.
  • Confusing Fabric and Forge versions of a mod.
  • Mixing loaders in the mods folder.
  • Assuming mods are cross-loader.
  • Picking the wrong file on a multi-loader page.
How To Diagnose
  1. Confirm the server runs Forge.
  2. Check the mod jar, a Fabric mod has fabric.mod.json.
  3. Read the log for which mod was rejected.
  4. Verify you downloaded the Forge build.
Recommended Fixes
  • Install the Forge build
    Download the Forge version of the mod for your Minecraft version.
  • Check for a Forge port
    If the mod is Fabric-only, look for an official Forge port or an equivalent mod.
  • Run a Fabric server instead
    If you need that exact Fabric mod, run a Fabric server rather than Forge.
  • Pick the right file
    On the mod page, choose the Forge download explicitly.
Frequently Asked Questions

No. They are different formats, Forge cannot read Fabric mods.

A Fabric mod contains fabric.mod.json, a Forge mod uses mods.toml/Forge metadata.

Use a Fabric server, find a Forge equivalent, or check for an official port.