How to Install Minecraft Mods

Minecraft ships as two separate games that share a name. Java Edition runs on Windows, macOS and Linux, is bought from minecraft.net, and is the version with a twenty-year modding ecosystem behind it. Bedrock Edition runs on consoles, phones, and Windows via the Microsoft Store, and it does not accept Java mods at all.

If you are not sure which you own, open the game and look at the bottom-left of the title screen. Java Edition prints a version like 1.21.4 on its own. Bedrock prints something longer with extra numbers, and its main menu has a Marketplace button. Java has no Marketplace.

This matters because most of the frustration people hit with modding is not a technical failure — it is downloading a Java mod, dropping it somewhere on a Bedrock install, and concluding that modding is broken. Bedrock has add-ons instead, distributed as .mcaddon and .mcpack files that you install by simply opening them. They are genuinely more limited: they work through the game’s scripting and resource systems rather than modifying the game code, so they cannot add the kind of deep machinery a Java tech mod does.

Vanilla Minecraft has no way to load third-party code. A mod loader is the layer that makes it possible, and every Java mod is built against one specific loader. Installing a Fabric mod into a NeoForge setup fails exactly as hard as installing nothing at all.

There are four loaders in circulation, but in practice you are choosing between two. Fabric is lightweight, updates within days of a new Minecraft release, and dominates performance and utility mods. NeoForge is the continuation of Forge for modern versions and carries the large content mods — tech, magic, and exploration packs. Forge itself still matters because an enormous back catalogue of 1.12.2 through 1.20.1 content runs on it. Quilt is a Fabric fork with a small following.

Our live pull from Modrinth shows how the ecosystem has actually settled, and the result surprises people who have not modded in a few years:

Fabric now carries more mods than Forge. That reverses the advice on a lot of guides still floating around, which were written when Forge was the assumed default. If you are starting fresh on a current version and you mainly want performance, quality-of-life and visual mods, Fabric is the sensible default. If you want the big content packs, follow whichever loader those specific mods target.

This is the step that breaks the most installs, and it is worth being blunt about: you should pick your Minecraft version to suit the mods you want, rather than running the newest version and hoping mods exist for it. The modding ecosystem lags the game by a long way.

Read that table carefully. The three-year-old 1.20.1 branch has 33,986 mods available, while the current 1.21.4 has 17,192 — roughly half. That is not a rounding difference, it is the reason nearly every large modpack you will encounter is still built on 1.20.1. Those counts come from the Modrinth API and were last refreshed on September 4, 2026.

The practical rule: open the mod page first, read which Minecraft versions and which loader it supports, and then create a launcher profile to match. Doing it in that order eliminates most crashes before they can happen.

Minecraft runs on Java, and different Minecraft versions require different Java runtimes. Modern versions from 1.20.5 onward need Java 21. Versions from 1.18 through 1.20.4 need Java 17. Older 1.16 and 1.12.2 setups want Java 8. The official launcher bundles the correct runtime and handles this for you automatically, which is the main argument for using it while you are learning.

Where people run into trouble is with third-party launchers, or with a system-wide Java installation overriding the bundled one. If a game that worked yesterday now fails instantly with a message about an unsupported class file version, that number is telling you a Java mismatch has occurred.

The mods folder does not exist until a loader has been installed and the game launched once with that profile. Installing Fabric and immediately hunting for the folder is a common dead end — launch the game first, let it reach the title screen, quit, and the folder will be there.

On Windows, press Win+R and paste %appdata%\.minecraft. On macOS, open Finder, press Cmd+Shift+G, and enter ~/Library/Application Support/minecraft. On Linux it is ~/.minecraft. Inside that directory you want the folder named mods.

If you use a third-party launcher such as Prism or MultiMC, each instance keeps its own separate mods folder, and editing the default .minecraft one will appear to do nothing. Use the launcher’s own “open folder” button rather than navigating there by hand.

Download mods only from Modrinth or CurseForge. Both are the platforms authors publish on directly, both let you filter by Minecraft version and loader before you download, and neither wraps files in a third-party installer. A Minecraft mod is a .jar file. If a site hands you an .exe, close the tab.

Drag the .jar files into the mods folder with the game closed. Do not unzip them and do not rename them — the loader reads metadata from inside the archive, and a renamed file still works but makes troubleshooting harder later.

Then handle dependencies, which is the step most first-time installs miss. Many Fabric mods require Fabric API, a separate download that provides shared functionality. Others need libraries like Cloth Config or Architectury. The mod page lists these under a dependencies or required section, and skipping them produces a crash that names the missing library directly.

These are the most-downloaded mods on Modrinth right now, which is a decent proxy for what a sensible first mod list looks like — several of them are the dependencies everything else needs:

Open the launcher, click the profile dropdown next to the Play button, and select the Fabric or NeoForge entry rather than the plain release. Loading vanilla by accident is the reason a perfectly correct install can open with no mods visible and no error at all.

A successful modded launch looks slightly different from vanilla: the title screen usually shows the loader name and a mod count in the corner. If the count is there and matches, you are done.

Add mods a few at a time on the first run rather than dropping in fifty at once. When something breaks, a small batch tells you immediately which mod caused it; a large batch means starting a bisect.

Crashes feel opaque but they are unusually predictable in modded Minecraft. Version mismatch, missing dependency, and insufficient memory account for the overwhelming majority of them.

A version mismatch typically produces a message about an incompatible mod set or a loader refusing to start, and the log names the offending file. A missing dependency names the library it wanted. Memory problems announce themselves as java.lang.OutOfMemoryError and usually appear when loading a world rather than at startup — the fix is raising the allocation in the launcher’s JVM arguments, not adding more mods.

The single most useful habit is opening latest.log in the logs folder and reading the first error rather than the last. Modded crashes cascade, so the bottom of the file is usually noise from whatever failed after the real problem.

Client-side mods — shaders, minimaps, performance patches — only need to exist on your own machine. Anything that adds blocks, items, mobs or recipes has to be installed on the server as well, and every player needs an identical mod list at identical versions.

Realms does not support mods. It is a common and expensive surprise, since people often buy a Realms subscription expecting to play a modpack on it. For modded multiplayer you either host on your own machine or rent a server.