Minecraft Java mod not working or crashing
Almost every "broken" mod is one of four things: the wrong loader, the wrong Minecraft version, a missing library, or a crash the log will name for you. Work down this list in order — the first two causes catch most cases.
Check these three first: (1) the mod is for your loader (Forge, Fabric or NeoForge); (2) it's for your exact Minecraft version; (3) you installed its required dependency (e.g. Fabric API). One of these is the problem about 90% of the time.
1. Wrong mod loader (Forge vs Fabric vs NeoForge)
Java mods are built for a specific loader, and they are not interchangeable — a Fabric mod will never load on Forge, and vice-versa. The main loaders today:
- Fabric — lightweight, fast updates; needs the Fabric API mod alongside it.
- NeoForge — the fork that most large 1.20.2+ mods moved to; it's where modern Forge-style modding lives now.
- Forge — the classic loader, still used by many packs on 1.20.1 and older.
- Quilt — a Fabric-compatible loader; most Fabric mods run on it too.
On the mod's CurseForge or Modrinth page, each file is tagged with its loader. Match it: install that loader, then launch the matching profile and drop the mod in that profile's mods folder. A Forge mod in a Fabric profile simply won't appear.
2. Minecraft version mismatch
A mod built for one Minecraft version usually won't load on another — often not even between minor releases (a 1.21.1 mod may refuse to load on 1.21.4). On the download page, check the file's supported Minecraft version and pick the file that matches the profile you're launching. If you just updated Minecraft, your old mods are almost certainly the wrong version now (see step 8).
By 2026 the active mod ecosystem still centers on 1.21.x — that's where almost every mod and pack is available, so it's the safest version to mod on. Always match the version the mod actually lists.
3. A required dependency is missing
This is the single most common "fails to load" cause. Many mods need a library mod to run:
- Fabric API — required by the vast majority of Fabric mods.
- Architectury API, Cloth Config, Forge Config API Port — common shared libraries.
The mod's page lists what it needs (look for a Dependencies / Relations section). Download each required dependency for your loader and Minecraft version and put it in the same mods folder. If the game says a mod "requires Fabric API", that's exactly this.
4. The mod is in the wrong folder
Mods must go in the profile's mods folder, not just anywhere:
- Vanilla launcher (Windows):
%appdata%\.minecraft\mods— paste that into the Explorer address bar. Create themodsfolder if it isn't there. - CurseForge App / Modrinth App / Prism / MultiMC: each instance has its own mods folder — open the instance and use "Open folder" / "Mods", not the vanilla path.
Putting a mod in the vanilla folder while launching a CurseForge instance (or the reverse) is a classic "nothing happens" mistake.
5. The game crashes on launch → read the log
A crash isn't a dead end — Minecraft tells you the culprit:
- When it crashes, open the crash report it points to, or the latest log at
%appdata%\.minecraft\logs\latest.log(per-instance launchers have their ownlogsfolder). - Search for lines like "Caused by", "Failed to load", or a mod id in red — that usually names the mod and the reason (wrong version, missing dependency).
- Can't tell which mod? Bisect: remove half the mods and launch. If it works, the problem is in the half you removed; if it still crashes, it's in the half left. Repeat until one mod is left.
6. Java version
Modern Minecraft needs a modern Java (Java 17 for 1.18–1.20.4, Java 21 for 1.20.5 and 1.21+). The official launcher and CurseForge/Modrinth/Prism bundle and pick the right one automatically — so leave Java on default. Problems usually come from an old, manually-set JDK in a launcher's Java settings; remove the override and let the launcher manage it.
7. RAM allocation
Most modpacks run well on 4–6 GB. Too little causes "out of memory" crashes; allocating too much (e.g. all your RAM) can actually make it stutter. Set it in the launcher's instance/Java settings, not by editing files.
8. Outdated mods after a Minecraft update
When you update Minecraft, every mod has to be updated to the new version too — and all of them must be the same Minecraft version and loader. Update the whole set together, or keep a separate profile on the older version for your existing mods.
9. Two mods conflicting
Occasionally two mods change the same thing and crash together even though each works alone. The bisect method in step 5 finds the pair; then check each mod's page for a known incompatibility, or keep only one.
Get MC Java Mods
Browse and download Java mods, modpacks and resource packs — with the loader and version shown up front so you grab the right file. Free on Android.
Frequently asked questions
Forge or Fabric — which one do I need?
Whichever the mod is built for — the mod's download page tells you. Each mod's file is tagged Fabric, Forge or NeoForge, and they aren't interchangeable. Install that loader, launch its profile, and put the mod (plus any required library like Fabric API) in that profile's mods folder.
Where is the mods folder?
For the vanilla launcher on Windows it's %appdata%\.minecraft\mods (paste that into the Explorer address bar; create the folder if it's missing). The CurseForge App, Modrinth App, Prism and MultiMC each give every instance its own mods folder — open the instance and use its "Mods" / "Open folder" button instead.
It says a mod "requires Fabric API" — what now?
Fabric API is a required library for most Fabric mods. Download Fabric API for your exact Minecraft version and put it in the same mods folder as the mod. Many mods also need other libraries (Architectury, Cloth Config) — the mod's page lists them under Dependencies.
How do I read a crash report?
Open the crash report the game points to, or logs\latest.log in your Minecraft folder. Look for "Caused by" or "Failed to load" lines — they usually name the mod and the reason. If it's unclear, remove half your mods and launch; whichever half stops the crash contains the culprit. Repeat to narrow it to one mod.
The mod still won't load and there's no crash
Double-check all three basics: the mod matches your loader, it matches your exact Minecraft version, and its required dependencies are installed in the same folder. A mod that's silently absent is almost always the wrong loader or version for the profile you launched.
Can I use a Bedrock addon in Java?
No. Bedrock and Java use completely different formats — Bedrock addons are .mcpack/.mcaddon, Java mods are .jar. They don't cross over. If you're on Bedrock instead, see the Bedrock addon guide.