How to Install Minecraft Mods (Fabric, NeoForge & Forge)

Minecraft: Java Edition can’t load mods on its own. You need a mod loader, usually Fabric or NeoForge, installed for the exact game version the mod was made for. Once that’s in place, installing a mod is almost boringly simple: one .jar file goes into one folder. Nearly every problem people run into comes from mixing loaders or versions, so this guide spends as much time on picking the right files as on copying them.

The short version

1. Check which Minecraft version and which loader the mod needs. Both are listed on every CrashMods mod page.
2. Install that loader for that version: Fabric from fabricmc.net or NeoForge from neoforged.net.
3. Start the new loader profile once from the Minecraft Launcher, then close the game.
4. Drop the mod’s .jar into .minecraft\mods, together with any library it needs, such as Fabric API.
5. Start the game with the loader profile selected.

Before you download anything

Three quick checks save most of the headaches:

• You need the Java Edition. The version sold as “Minecraft for Windows”, and the console and phone versions, are Bedrock. Bedrock uses add-ons (.mcaddon and .mcpack files) instead of loader mods, and nothing in this guide applies to it.
• Match the game version. A mod built for 1.21.1 usually won’t load on 1.21.4, and a 26.2 mod won’t run on 26.1.2. Pick the mod first, then set up the game version it asks for, not the other way round.
• Match the loader. A Fabric mod won’t start on NeoForge, and a NeoForge mod won’t start on Fabric. Plenty of authors publish separate files for each loader, so grab the one that fits your setup.

One more thing catches out a lot of returning players: Mojang changed its version numbers in 2026. After 1.21.11, releases switched to a year-based scheme, so 26.1, 26.2 and 26.3 are newer than any 1.21 release, not older. The 26.x versions run on Java 25, which the official launcher downloads for you. On CrashMods you can browse by version, for example Minecraft 26.2 mods or the still very popular 1.21.1 mods.

Fabric, NeoForge or Forge?

In practice the mod chooses the loader for you. It still helps to know what each one is for, because a single modded installation can only run one of them.

If a mod page lists both Fabric and NeoForge, choose whichever matches the rest of your mods. You can’t run two loaders in one installation; if you want both, keep two separate installations (more on that below).

Step 1: install the mod loader

Fabric

1. Go to fabricmc.net, open the download page and get the installer. Windows users can take the .exe; everyone else uses the universal .jar.
2. Close the Minecraft Launcher if it’s open, then run the installer.
3. On the Client tab, pick your Minecraft version, leave the newest loader version selected and keep Create profile ticked. Click Install.
4. Open the Minecraft Launcher. A new installation whose name starts with fabric-loader- now sits in the dropdown next to the Play button.
5. Start it once and wait for the title screen. That first run creates the mods folder.

NeoForge

1. Download the installer for your Minecraft version from neoforged.net. It’s a .jar file.
2. Double-click it, choose Install client and press OK. If the file opens in WinRAR or 7-Zip instead, right-click it and use Open with → Java. No Java in that list? Install a current Java runtime (Eclipse Temurin is a good one) and try again.
3. In the launcher, select the new NeoForge installation and press Play once.

Forge works the same way as NeoForge on older versions: download the installer from files.minecraftforge.net, choose Install client, then start the new profile once.

Where Minecraft keeps its mods folder

Every loader reads from the same place. On Windows it sits inside the hidden AppData folder:

C:\Users\<YourName>\AppData\Roaming\.minecraft\mods

The fastest way there: press Win+R, type %appdata%\.minecraft and hit Enter. On a Mac the folder is ~/Library/Application Support/minecraft/mods, and on Linux it’s ~/.minecraft/mods. If there’s no mods folder yet, either start the loader profile once or create it yourself. Call it exactly mods, in lowercase.

A habit that pays off later: in the launcher, open Installations, edit your loader profile and give it its own game directory, for example .minecraft-26.2. Each version then has its own mods folder, worlds and settings, and you never end up with 1.20.1 mods sitting next to 26.2 ones.

Step 2: add the mod and its libraries

1. Download the file for your version and loader. It should end in .jar.
2. Move it into the mods folder exactly as it is. Don’t unzip it, and don’t rename it to .zip.
3. Check the mod page for requirements. Nearly every Fabric mod needs Fabric API, and others ask for libraries such as Cloth Config, Architectury API or GeckoLib. Those are mods too, and they go into the same folder.
4. In the launcher, select the Fabric or NeoForge installation (not “Latest release”) and press Play.
5. On the title screen, open Mods to confirm everything loaded. NeoForge has that button built in; Fabric shows it once you add the small Mod Menu mod.

Some mods only need to be on your own PC: minimaps, HUD tweaks and visual changes such as Enchantment Glint Outline. Others change how the game works, like Glowing Torchflower, and have to be installed on the server as well if you play multiplayer.

Resource packs, shaders and data packs don’t go in mods

Not everything people call a “mod” is a .jar. Three other kinds live in folders of their own, and putting them into mods only makes the loader ignore them or complain.

• Resource packs (.zip) change textures, models and sounds. Drop them into resourcepacks and switch them on under Options → Resource Packs.
• Shader packs (.zip) need a shader loader first: Iris on Fabric or NeoForge, or OptiFine on older setups. They go into shaderpacks, and you pick one under Video Settings → Shader Packs. RenderPearl is a good example: an Iris shader pack, not a mod.
• Data packs (.zip) belong to a single world. Add them while creating the world (More → Data Packs) or copy them into saves\<WorldName>\datapacks. Something like X-Ray World Generation works with any loader, or with none at all, precisely because it’s a data pack.

Using a launcher instead: CurseForge, Modrinth App or Prism

If you plan to run more than a handful of mods, a third-party launcher is worth the five minutes it takes to set up. The CurseForge app, the Modrinth App and Prism Launcher all work with separate instances, each with its own Minecraft version, loader, mods folder and worlds. They install the loader for you and can pull in required libraries automatically.

You can still add a .jar you downloaded from CrashMods. Every one of these launchers has an Open folder button for an instance: go into its mods folder and drop the file in. The same version and loader rules apply.

Playing on a modded server

On a modded server, the content mods have to match on both sides: same mods, same versions. If the server adds a block your game doesn’t know about, you’ll be kicked with a mismatch or registry error the moment you join. Purely visual mods (shaders, minimaps, performance mods like Sodium) only need to be on your PC, and many mod pages, ours included, say which side a mod belongs on.

Realms is the exception: it doesn’t run mods at all, so a modded world needs a regular server.

Give modpacks enough memory

The launcher gives Minecraft 2 GB of RAM by default. That’s fine for vanilla and light Fabric setups, but bigger packs stutter, freeze while loading or crash with an out-of-memory error. To change it, go to Installations, edit your profile, open More options and change -Xmx2G at the start of the JVM arguments to -Xmx6G. Four to eight gigabytes covers almost any pack. Handing over all of your RAM actually makes things worse, because Windows and Java’s garbage collector need room to breathe too.

When the game crashes after adding mods

Start with the error screen itself. Fabric spells out which mod is missing a dependency or needs a different version, and NeoForge shows an error screen naming the file it choked on. Most of the time the fix is written right there.

If the launcher only says Exit Code: 1 (or another number), open .minecraft\logs\latest.log in Notepad and search for the first line that mentions “ERROR” or “Exception”. Full crash reports land in .minecraft\crash-reports. The usual suspects:

• A mod for the wrong Minecraft version or the wrong loader.
• A missing library. Fabric API is the classic one.
• Two versions of the same mod in the folder, often left behind after an update.
• OptiFine installed together with Sodium, Iris or Embeddium. Choose one rendering setup.
• Not enough memory for the pack (see above).

Still stuck? Move half of the mods out of the folder and test. If the game starts, the problem is in the half you removed; keep halving until a single file is left. It sounds tedious, but even with 80 mods it only takes six or seven launches.

Six mistakes that break modded Minecraft

• Launching the wrong profile. “Latest release” is plain vanilla. Select the Fabric or NeoForge installation before you press Play.
• Unzipping the .jar. Leave it as a single file; an extracted folder won’t load.
• Mixing loaders. One installation, one loader.
• Forgetting the library. Read the requirements on the mod page before you blame the mod.
• Packs in the wrong folder. Shader, resource and data packs each have a folder of their own.
• Updating Minecraft too early. When a new version comes out, mods take days or weeks to catch up. Stay on the version your mods support until they’ve been updated.

Frequently asked questions

Can I install these mods on Bedrock or on a console?

No. Fabric, NeoForge and Forge mods only run on Minecraft: Java Edition for Windows, macOS and Linux. Bedrock has its own add-on system and Marketplace.

Do I still need OptiFine?

Usually not. On current versions, Sodium takes care of performance and Iris loads shader packs, and both exist for Fabric and NeoForge. OptiFine also tends to clash with other mods.

Will Forge mods work on NeoForge?

Only on 1.20.1, where NeoForge started out as a copy of Forge, and even there not every mod cooperates. From 1.20.2 onwards the two went separate ways, so download the NeoForge file whenever the author offers one.

Is it safe to download Minecraft mods?

A .jar can run code on your PC, so where you get it from matters. Every file on CrashMods is scanned with VirusTotal before it goes live. Steer clear of sites that wrap mods in .exe “installers”: a real Minecraft mod is never an .exe.

Can a mod damage my world?

Removing a mod deletes everything it added: its blocks vanish from the world and its items disappear from chests. Before you add or remove a big content mod, copy the world from the saves folder somewhere safe.

Ready to try something? Browse all Minecraft mods on CrashMods, or jump straight to adventure, technology, magic, world generation and shader mods.