Where Is the Minecraft Mods Folder?

If you use the official Minecraft launcher, the mods folder lives inside your Minecraft data directory. That directory is in a different place on each operating system, and on Windows it is hidden by default, which is why browsing for it manually rarely works.

The fastest route on Windows is the Run dialog rather than File Explorer: press Win+R, paste the path, press Enter. This works whether or not hidden folders are shown.

On macOS the Library folder is hidden too, so use Finder's Go to Folder shortcut rather than clicking through.

This is the single most common reason people cannot find it, and nothing is broken.

The mods folder is created by a mod loader the first time a modded profile runs. Installing Fabric or Forge does not create it — launching the game on that profile does.

So the sequence is: install the loader, open the launcher, select the new profile, launch, wait for the title screen, quit. The folder will be there.

You can also simply create it yourself. A folder named exactly 'mods', lowercase, inside the Minecraft directory works fine — the loader will use it. But if you have not installed a loader, an empty mods folder achieves nothing, because there is nothing to read it.

This trips up people who have modded before. Prism Launcher, MultiMC, the CurseForge app, ATLauncher and GDLauncher all use per-instance directories. The .minecraft folder is irrelevant to them.

Each instance is a self-contained setup with its own mods folder, its own configs, its own memory allocation and often its own Java version. That isolation is the entire point — it is what lets you run six different modpacks without them interfering.

The consequence is that dropping mods into %appdata%\.minecraft\mods while playing a Prism instance does absolutely nothing, and produces no error to tell you so. The game launches, the mods are not there, and everything looks normal.

Every one of these launchers has a button to open the correct folder. Right-click the instance and choose Open Folder, or use the Mods tab which offers a drag-and-drop target. Use that rather than navigating by hand.

The official launcher supports per-profile game directories, and if you or a guide set one up, that profile reads from a different location.

Check by opening the launcher, going to Installations, and editing the profile. The Game Directory field shows where that profile actually stores everything. If it is not the default, the mods folder you want is inside whatever path is listed there.

This is worth doing deliberately once you run more than one modded setup on the official launcher. Giving each profile its own directory keeps 1.20.1 Forge mods from mixing with 1.21.4 Fabric mods, which otherwise all end up in one folder and produce a great deal of confusion.

Mods are .jar files and they go in loose. Do not unzip them, do not put them in subfolders, and do not rename them.

Subfolders are ignored by most loaders, so a mods folder containing a folder containing your mods will load nothing. This happens when people extract a downloaded archive rather than moving the .jar itself.

Resource packs do not go here — they belong in the resourcepacks folder. Shader packs go in shaderpacks. Putting either in mods does nothing at best and produces errors at worst.

Config files generate themselves in the config folder after the first run with a mod installed. You do not create these by hand, and editing them before that first run has no effect because they will be overwritten.

Once you have more than one version or loader in play, a single shared mods folder becomes actively harmful. A 1.20.1 Forge mod sitting alongside 1.21.4 Fabric mods will be loaded by neither and will generate errors in both.

The clean solution is instance-based launchers, where separation is enforced rather than something you maintain by discipline. Prism Launcher is the usual recommendation, is free and open-source, and imports packs from both CurseForge and Modrinth.

If you would rather stay on the official launcher, use custom game directories per profile as described above. It achieves the same isolation with a little more manual setup.

Whichever route you take, the principle is one folder per version-and-loader combination. Mixing them is the source of a surprising proportion of unexplained mod problems.

A specific case that catches people: Minecraft installed through the Microsoft Store on Windows is Bedrock Edition, which has no mods folder because it does not use mods at all.

If you searched for the mods folder, could not find it, and your game came from the Store, this is almost certainly why. Bedrock uses addons instead, imported by opening the file rather than by placing it in a directory.

There is also a Java Edition available through the Microsoft Store, which does have a mods folder in the usual place. The distinguishing feature remains the Marketplace button on the title screen — Bedrock has one, Java does not.

Owning the Bedrock version does not prevent you from owning Java. They are sold together in the Minecraft Java and Bedrock Edition bundle, so many people have both installed and are looking in the wrong one.

Both Windows and macOS hide the parent directories by default, which is why browsing to the mods folder manually so often fails.

On Windows, AppData is hidden. You can either paste the path into the Run dialog as described above, or enable hidden items in File Explorer's View tab, after which you can navigate normally.

On macOS, the Library folder inside your home directory is hidden. Finder's Go menu reveals it if you hold the Option key, and Cmd+Shift+G bypasses the problem entirely.

Once you have the folder open, drag it to the sidebar or make an alias on the desktop. You will be opening it repeatedly and it is worth the ten seconds.

If you are unsure whether the folder you found is the one the game actually reads, there is a simple test that takes one launch.

Put a single mod in it and start the game. If the title screen mod count goes up, that is the right folder. If it does not, it is not, regardless of how correct the path looked.

A second confirmation: look for a config folder and a logs folder beside it. A genuine Minecraft directory has both, and a folder containing only mods is often one someone created by hand in the wrong place.

Checking this once at the start saves repeating the same failed install three times.