How to Add Mods to Minecraft

Before touching anything, understand what you are lining up. Your Minecraft version, your mod loader, your Java runtime and each mod file all have to agree.

Get one wrong and the outcome is either a crash on launch or a game that opens looking entirely normal with none of your mods present. The second is more confusing than the first, because nothing appears to have gone wrong.

Almost every problem in this hobby traces back to this table. It is worth reading twice before you download anything.

This takes five seconds and saves people entire afternoons. Open Minecraft and look at the main menu. If there is a Marketplace button, you have Bedrock Edition and none of this applies to you — Bedrock uses addons instead.

Java Edition is the version bought from minecraft.net and it runs on Windows, macOS and Linux. Anything bought on a console, a phone, or through the Microsoft Store is Bedrock.

There is no converter, no patch and no workaround that lets Bedrock run Java mods. If you are on Bedrock, the addons guide is the one you want.

Minecraft cannot load third-party code on its own. The loader is what makes it possible, and it is the step people skip when they drop mods into a folder and wonder why nothing happened.

For a current version, Fabric is the easiest starting point: download the installer from fabricmc.net, run it, pick your Minecraft version, and click install. It takes under a minute and creates a new launcher profile without touching your existing installation.

If the mods you want are NeoForge or Forge mods, install that instead — the process is equivalent. What matters is that the loader matches what your mods were built for.

Now launch the game once using the new profile. This is important: the mods folder does not exist until a modded profile has run at least once. Let it reach the title screen, then quit.

On Windows, press Win+R, paste %appdata%\.minecraft and press Enter. On macOS, open Finder, press Cmd+Shift+G and enter ~/Library/Application Support/minecraft. On Linux it is ~/.minecraft.

Inside, you want the folder called mods. Leave the window open — you are about to drop files into it.

If you use Prism Launcher, MultiMC or the CurseForge app, ignore all of the above. Each instance keeps its own separate mods folder, and editing the default .minecraft one will do absolutely nothing. Use the launcher's own folder button instead.

Modrinth and CurseForge are where mod authors actually publish. Both let you filter by Minecraft version and loader before downloading, which prevents the most common mistake in one click.

Set those filters first. Then download, and drop the .jar files straight into the mods folder with the game closed. Do not unzip them and do not rename them.

A Minecraft mod is a .jar file. If a site gives you a .exe, an installer, or asks you to disable your antivirus, close the tab. That is the main way people acquire malware in this hobby, and it is entirely avoidable by using the two official platforms.

This is the step first-time installs miss most often. Many mods rely on shared libraries that have to be installed alongside them.

On Fabric, the big one is Fabric API — a separate download that most Fabric mods require. Others need Cloth Config for their settings screens, or Architectury if the author ships for multiple loaders.

Every mod page lists its requirements in a dependencies section. Download each required entry, matching your Minecraft version and loader exactly as you did for the mod itself, and put them in the same folder.

Dependencies occasionally have their own dependencies. Work down the chain; it terminates within a step or two.

Open the launcher, make sure the profile dropdown still shows your modded profile rather than the plain release, and hit Play. Selecting vanilla by accident is why a perfectly correct install sometimes appears to have done nothing at all.

A successful modded launch usually announces itself on the title screen with the loader name and a mod count. If the count matches roughly what you installed, you are finished.

Add mods a handful at a time on your first few attempts. When something breaks, five suspects is a two-minute problem and eighty suspects is an evening.

The temptation on a first install is to grab twenty things that sound interesting. It is a better experience to start with four or five that change how the game feels rather than what is in it.

Performance mods are the safest opening move. They alter nothing you can see in the world, cannot corrupt a save, and can be removed at any point with no consequences. On a modest machine the difference is dramatic — frame rates commonly double.

Quality-of-life mods are the next tier: an inventory sorter, a recipe viewer, a minimap. They change how you interact with the game without changing the game itself, and they are similarly safe to remove.

Content mods — new dimensions, machines, mobs — are where modded Minecraft becomes genuinely different, and they are also where commitment starts. Once a world contains a mod's blocks, removing that mod leaves holes. Add these once the basics are stable, and back the world up first.

This sounds fussy and it repays itself the first time something breaks. Keep a plain text file listing each mod, its version, and the Minecraft version it was for.

The reason is that mod folders drift. You add something in June, update two things in July, and by August you have a setup that works and no memory of how it got there. When a launcher update breaks it, that file is the difference between a five-minute fix and rebuilding from scratch.

Some launchers do this for you. Prism Launcher can export an instance's full mod list, and the CurseForge app tracks versions per instance. If you use the official launcher, you are keeping the note yourself.

It also makes helping a friend trivial — you send them the list instead of trying to remember.

Two failures cover nearly everything on a first install, and they look completely different.

The game opens and looks entirely vanilla. That means the mods were not loaded at all, which means either you launched the wrong profile or the files are in the wrong folder. Check the launcher dropdown first, then confirm the folder you used belongs to the profile you launched.

The game crashes before reaching the title screen. That means the mods were found and something about them is wrong — usually a version mismatch or a missing dependency. Open latest.log in the logs folder and read the first error, which almost always names the file responsible.

Resist reinstalling Minecraft. It is the instinct and it almost never helps, because the problem is in the mods rather than the game. It does reliably destroy your settings.