Fabric mod not loading? Check these 10 things

Run this quick checklist first

• 01Minecraft versionMatches the mod release exactly
• 02Mod loaderFabric build running on Fabric Loader
• 03DependenciesEvery required library is installed
• 04Java runtimeMeets the game and mod requirement
• 05Mods folderBelongs to the active launcher instance
• 06JAR filesNot extracted, duplicated or renamed

If Minecraft shows a Fabric Loader error screen, read it before making changes. It often names the incompatible or missing dependency directly.

Match Minecraft, Fabric Loader and Java

Wrong Minecraft or mod version

A mod build supports the versions declared by its author. A file for another Minecraft release can be rejected even when its name looks similar. Download the build for the exact game version selected in your launcher.

Fabric Loader missing or too old

Confirm the instance actually launches with Fabric Loader. If a mod declares a minimum Loader version, use a compatible release instead of launching the normal unmodded profile. See how to install Fabric mods for a clean setup.

Wrong Java version

Minecraft versions can require different Java runtimes. Use the runtime recommended for the game version and required by the mod; changing mod files will not fix an incompatible Java runtime.

Check Fabric API and every dependency

Fabric Loader and Fabric API are different. Loader starts Fabric mods; Fabric API is a shared library used by many, but not all, mods. Install it only when the mod lists it as required, and match it to the same Minecraft version.

Some mods require an additional library or companion mod. Fabric Loader normally reports the missing mod ID and acceptable version range. Follow that message and the mod's official release notes. Our Fabric Loader vs Fabric API guide explains the distinction.

Use the correct mods folder and launcher instance

Putting a JAR in a random .minecraft/mods folder does not help when your launcher is using another game directory. Open the active profile or instance folder from the launcher, then use its mods folder. Create that folder only inside the confirmed instance directory.

Leave mod files as .jar files. Do not unpack them. Remove older duplicate versions, because two releases of the same mod can conflict. Find platform paths and launcher guidance in Where is the Minecraft mods folder?

Isolate conflicts and check client/server side

Temporarily test the problem mod with only its required dependencies in a separate test instance. If it loads, add the remaining mods back in small groups until the conflict returns. Keep a backup before changing a world used by a modded setup.

A client-side mod belongs on the player's instance and may not need server installation. A server-side mod belongs on the server, and a mod described as required on both sides must be present in both places. Verify the author's requirement; moving a server-only mod into the client cannot make it work. Learn the boundary in our client-side mods guide.

Read the log or crash report

When the Loader screen is not enough, inspect logs/latest.log inside the active instance. If Minecraft created a crash report, look in that instance's crash-reports folder. Search near the final error for a mod ID, dependency, version range or Java exception.

If the mod still does not load

1. 01

   Reproduce it in a clean instance

   Use only Fabric Loader, the problem mod and its declared dependencies.

2. 02

   Record exact versions

   Note Minecraft, Java, Fabric Loader and every relevant mod version.

3. 03

   Keep the complete error

   Share the relevant log or crash report with the mod's official support channel after removing private data.