Guide

How to install a Fabric mod

Updated October 18, 2026

A Fabric mod needs two things before it runs: Fabric Loader for your exact Minecraft version, and almost always Fabric API, a separate mod that most Fabric mods depend on. Then the mod .jar goes in the mods/ folder. Here is how to do it on your own game and on a server.

An example to start from.

Generate this with Codexe

Step by step

  1. 1.Pick the Minecraft version

    Every mod is built for one Minecraft version (or a short range). Choose the version first, then download the mods for it.

  2. 2.Install Fabric Loader

    Download the Fabric installer from fabricmc.net, choose Client, pick the Minecraft version and install. It adds a "fabric-loader" profile to the Minecraft Launcher.

  3. 3.Run the profile once

    Start the game with the Fabric profile and close it. This creates the mods/ folder inside .minecraft.

  4. 4.Add Fabric API and the mod

    Download Fabric API for the same Minecraft version, then put it and the mod .jar in .minecraft/mods/. Do not unzip them.

  5. 5.Start the game and check

    Launch the Fabric profile. If a mod is missing a dependency or is for another version, Fabric shows a screen that names the mod and what it needs.

Where the mods folder is

  • Windows: %appdata%\.minecraft\mods (paste it in the Run dialog or the Explorer address bar).
  • macOS: ~/Library/Application Support/minecraft/mods.
  • Linux: ~/.minecraft/mods.
  • Other launchers (Prism, MultiMC, Modrinth App, CurseForge app) keep a separate folder per instance: use their "Open mods folder" button.

Installing on a server

For multiplayer, the server needs Fabric too. Get the Fabric server launcher (or run the installer in Server mode) for the same Minecraft and loader version, start it once, then put Fabric API and the mods in the server's mods/ folder and restart.

Which mods go where depends on the mod:

  • Content mods (new blocks, items, mobs): on the server and on every player's client.
  • Client-only mods (HUDs, minimaps, shaders, keybinds): only on the client. Some crash a dedicated server if you put them there.
  • Server-only mods (performance, admin tools, some gameplay rules): only on the server; players join with plain Fabric or even vanilla, if the mod says so.

Common problems

  • "Incompatible mods found": a mod is for another Minecraft version, or needs a newer Fabric Loader. Fabric names the mod: replace it with the right version.
  • Requires fabric-api: Fabric API is missing from mods/, or it is for a different version.
  • The mod does nothing: you started the normal profile instead of the Fabric one, or the mod is for Forge or NeoForge. Fabric does not load Forge mods.
  • Crash on a dedicated server mentioning client classes: a client-only mod was installed on the server.

Mods made with Codexe

A Fabric mod made on Codexe is compiled before it is Ready, and the .jar must contain a valid fabric.mod.json. It is built against Fabric API, so install Fabric API next to it. Compiling proves the mod builds, not that it runs without crashing, and mods cannot be tried on a Codexe test server yet: test it in your own client with the version it was made for.

Questions

Do I need Fabric API for every mod?

Not for every one, but for most. The mod page lists it as a dependency when it is needed. Installing it when a mod does not need it does no harm.

Can I use Forge mods on Fabric?

No. They are different loaders with different APIs: use the Fabric version of the mod if it exists. See Fabric vs Forge.

Do Fabric mods work on Quilt?

Quilt is a fork of Fabric and loads most Fabric mods, but not all of them. Check the mod page.

Make a Fabric mod to install

This prompt opens ready to send:

“A Fabric 1.21.1 mod that adds a Lantern Staff: right-click places a light block that disappears after 30 seconds, 64 uses, crafted from a stick, a lantern and gold ingots, with a texture and an English name.”

Generate this with Codexe
How to install a Fabric mod (client and server) | Codexe