How to Install Fabric Mods in Minecraft 26.3: Step-by-Step Guide

What you need

• Minecraft: Java Edition 26.3. Fabric mods don’t work on Bedrock.
• The Fabric Installer from the official page, fabricmc.net/use.
• Java 25. Since 26.1 the game requires Java 25, and the official Minecraft Launcher ships it, so the game itself needs nothing extra.
• Fabric API. Most Fabric mods need it. On October 19, 2026 the newest build for 26.3 was 0.164.0+26.3.

Step 1: Install Fabric Loader with the official installer

Close Minecraft and the Minecraft Launcher first. Then:

• Windows: download the .exe with “Download for Windows”. It uses the Java that comes with the Minecraft Launcher, so you don’t need to install Java. Run it, select 26.3, keep Create Profile ticked and click Install.
• macOS: download the .jar with “Download installer (Universal/.JAR)”. If macOS says it can’t verify the file, go to System Settings > Privacy & Security and click “Open Anyway”. With Homebrew, brew install fabric-installer works too. You may need to install Java first to run the .jar.
• Linux: download the same .jar and run java -jar fabric-installer.jar in a terminal (Java has to be installed). Select 26.3, keep Create Profile ticked, install.

The installer also shows a loader version: the Fabric wiki says to take the latest. If a mod later asks for a newer loader, you run the installer again (see the fixes below).

Step 2: Start the Fabric profile once

Open the Minecraft Launcher, choose the Fabric profile in the version dropdown at the bottom left and click Play. On this first start, Fabric Loader creates the mods folder in your game folder if it doesn’t exist yet. Close the game again.

Step 3: Open your mods folder

Paste the path into the address bar of your file explorer. If you play through another launcher, every instance has its own game folder. In Prism Launcher on Windows, that’s %APPDATA%\PrismLauncher\instances\<instance name>\minecraft, with its own mods, logs and crash-reports folders.

Step 4: Download the right file

Download mods only from the official page: Modrinth, CurseForge or the author’s own page. Before you click download, check three things on the version you picked:

1. Game version: 26.3. A file made for 26.2 or 1.21.11 may not load, and Fabric will tell you so when you start the game.
2. Loader: Fabric. Not Forge, not NeoForge.
3. Release, not beta or alpha. Release is the safe pick. When I do test a beta, like Nvidium in my FPS test, I label it as one.

The file name often tells you, too. GeckoLib for 26.3 comes as geckolib-fabric-26.3-5.5.7.jar and geckolib-neoforge-26.3-5.5.6.jar, and only the first one works with Fabric. Some mods ship a single file for both loaders: Zoomify 2.17.0 is zoomify-2.17.0+mc26.3-universal.jar.

Move the .jar file into the mods folder as it is. Don’t unzip it.

Step 5: Add Fabric API and the other dependencies

Most mods need Fabric API, and many need more. On Modrinth, every version lists the content it requires. Download each of those for 26.3 and Fabric as well. A few examples from my 26.3 tests:

• Zoomify needs Fabric API, Fabric Language Kotlin and YACL.
• Waystones needs Balm, Shogi and Fabric API.
• Iris needs Sodium.
• AppleSkin needs only Fabric API.

Three traps I ran into while setting up my own instances:

• The list isn’t always complete. In a test with this month’s new mods, Hoverboards needed GeckoLib and Biomes O’ Plenty needed GlitchCore and TerraBlender, although Modrinth didn’t list them. Fabric then refused to start, and the log named what was missing.
• A dependency for the wrong loader. The Fabric file of Mielon’s The Sift 1.1.2 points to the NeoForge build of GeckoLib. A launcher that installs dependencies on its own picks that file, and Fabric stops. The fix: download the Fabric build of GeckoLib for 26.3 yourself.
• A dependency you can skip. Zoomify’s single file also lists KotlinLangForge. That one only exists for NeoForge, so on Fabric you leave it out. My Fabric instance ran Zoomify without it.

Step 6: Start the game and check

Start the Fabric profile again. To see what loaded, open latest.log in the logs folder: Fabric writes “Loading” with the number of mods, then every mod with its version. In the game, the quickest check is the mod itself. With Sodium, for example, the Video Settings screen turns into Sodium’s own. Mod Menu adds a list of all installed mods and, for many mods, a settings button.

Prism Launcher and the Modrinth App

I record all my Minecraft videos with Prism Launcher. My setup is one clean instance for 26.3 with Fabric that I copy for every recording. Each mod and its required dependencies come straight from Modrinth (or from CurseForge for the few mods that are only there), and every Modrinth file is checked against its SHA-512 hash before the game starts. Separate instances also mean separate folders, so a test never mixes with another one.

• Prism Launcher: click Add Instance, pick 26.3, click Fabric in the Mod Loader list and take the recommended loader version (marked with a star). Then select the instance, click Edit, open Mods and use Download Mods (Modrinth or CurseForge) or Add Mod for a file you already have. Mods you downloaded there can be checked for updates.
• Modrinth App: create a new profile, choose Fabric as the loader and 26.3 as the game version, then search for mods inside the app and add them to that profile.

Both install the loader for you, so you skip Steps 1 to 3.

Common errors and how to fix them

When Fabric can’t load your mods, you don’t get the game. You get Fabric’s own window with the heading “Failed to launch!” and two buttons, Copy error and Exit. Read the text in the middle: often there’s a line “A potential solution has been determined, this may resolve your problem:” with the exact fix.

“Incompatible mods found!”

This is the general headline for every dependency problem. The lines under it tell you which one:

• ”… requires … which is missing!” A dependency isn’t installed. Download exactly what the line names, for 26.3 and Fabric. The Sift trap above showed up like this: “requires version 5.5.6 or later of geckolib, which is missing”.
• ”… but only the wrong version is present” The mod was made for a different Minecraft version, or a dependency in your folder is too old. Get the 26.3 file of the mod, or update the dependency.
• ”… is incompatible with …” The mod’s developer has marked two mods as not working together. Remove one of them or check for updates.

Fabric Loader is too old

Newer mods can need a newer loader. I hit this with a snapshot build of Fabric API, which stopped with “requires version 0.20.0 or later of mod Fabric Loader”. The fix: run the installer again, uncheck Create Profile, install the new loader version, then edit your Fabric profile in the launcher’s Installations tab and choose the new version.

A mod does nothing

If the game starts but a mod doesn’t show up, check whether you downloaded the Forge or NeoForge file. Fabric Loader doesn’t load files that aren’t Fabric mods. It only writes a warning to latest.log: “Found 1 non-fabric mod”, followed by the file name.

The game crashes on start

Two files tell you why:

In a crash report, start at the top section, “---- Minecraft Crash Report ----“, with the error and the stack trace. The first mod named there is often the cause, but if many mods show up, it can also be a conflict between them. “– System Details –” further down lists your Java version and every Fabric mod. For a crash inside a mixin, look for a mod-id$handlerName pattern in the stack trace: the mod ID names the mod. If you ask for help, upload the file to a paste site like mclo.gs and send the link to the mod author’s issue tracker.

Update and remove mods

• Update a mod: download the new 26.3 Fabric file, delete the old .jar and start the game. Keep only one version of each mod in the folder.
• Update Fabric Loader: run the installer again with Create Profile unchecked, then switch your Fabric profile to the new loader version in the Installations tab.
• Remove a mod: close the game and take its .jar out of the mods folder. Check the log on the next start: if another mod needed it, Fabric names it.

Stay safe: official pages only

Most mod authors publish on Modrinth and CurseForge, and the Fabric documentation explains why that matters: both sites check that mods are what they say they are and don’t contain malicious code, and they act on reports. Some authors also publish on their own GitHub. What to avoid are sites that advertise Minecraft mods but are really there to spread malware. Antivirus tools can help, but Fabric’s own guide warns that they can be wrong.

That’s why every download button on this site goes to Modrinth, CurseForge or the author’s own page, and I never re-host files. Once your setup runs, my 26.3 tier list and the FPS mod test are good places to pick your first mods.