The Minecraft mods folder is called mods, and it sits inside a bigger game folder named .minecraft that most players never see until something goes wrong. Java Edition and Bedrock Edition keep separate folders and separate file types entirely, so putting a .jar mod in the wrong one is the single most common reason a fresh install does nothing. This guide gives the exact path for Windows, Mac, and Linux, including where AppData actually is when it looks hidden or missing, plus where every other file type, resource packs, shader packs, data packs, saves, and Bedrock add-ons, belongs.
Where is the Minecraft mods folder?
Java Edition keeps every mod, resource pack, and world inside one game directory called .minecraft. The path is different on each system.
Where is the Minecraft mods folder on Windows?
On Windows, the mods folder is %APPDATA%\.minecraft\mods, inside the game directory at %APPDATA%\.minecraft. Written out in full, that is C:\Users\<name>\AppData\Roaming\.minecraft\mods. Press the Windows key plus R, type %appdata%\.minecraft\mods, and press Enter to open it directly, no need to hunt through folders by hand.
Where is the Minecraft mods folder on Mac?
On macOS, the mods folder is ~/Library/Application Support/minecraft/mods. In Finder, press Shift+Command+G, type ~/Library/Application Support/minecraft/mods, and press Return to jump straight there.
Where is the Minecraft mods folder on Linux?
On Linux, the mods folder is ~/.minecraft/mods, inside the hidden .minecraft folder in the home directory.
Every other Java file type in this guide, resource packs, shader packs, data packs, and saves, lives inside that same .minecraft folder, just in a different subfolder. A third-party install tool such as a modpack app or a profile manager usually gives each profile its own separate game directory with its own mods folder, so open the exact profile being played before adding files. A file placed in the default .minecraft folder will not appear in a different profile's game.
Fix a missing or hidden AppData folder
Why can't I see the AppData folder?
AppData is hidden by default on Windows, so a normal search for the mods folder often turns up nothing even though the folder is there. Windows hides it because most everyday apps do not need it opened directly, not because anything is missing or broken.
- Fastest: press the Windows key plus R, type %appdata%, and press Enter. This opens the Roaming folder directly, whether or not hidden items are visible in File Explorer.
- To see AppData in File Explorer from now on: open File Explorer, select View, choose Show, then turn on Hidden items. AppData will now appear inside C:\Users\<your name> alongside the other user folders.
What if the .minecraft folder isn't there at all?
If neither AppData nor .minecraft exists on that account at all, Java Edition may never have finished its first run there. Open the Minecraft app once, let it load through to the world selection screen, then check again.
Does Minecraft on Windows or Mac have mods?
Minecraft Java Edition is the version you download from minecraft.net and run through the Minecraft app on Windows, Mac, or Linux. It supports .jar mods through a loader such as Fabric, Forge, NeoForge, or Quilt. Minecraft on Mac runs Java Edition too, downloaded the same way as on Windows and Linux, so the same mods work there once a loader is installed.
Minecraft for Windows, the version installed from the Microsoft Store on Windows 10 and 11, is actually Bedrock Edition, not Java Edition. Bedrock does not read .jar files and does not run a mod loader at all. It uses its own package formats, .mcpack and .mcaddon, for behavior and resource changes, plus .mcworld for shared worlds. If Minecraft came from the Microsoft Store, check which edition is running before downloading anything: a Java mod will not appear, install, or do anything inside Bedrock.
Every file type and where it goes
Once the game directory is open, every download follows the same pattern: match the file type to its subfolder.
- Java mods (.jar), such as Sodium or Iris: mods.
- Java resource packs (.zip), such as Bare Bones: resourcepacks.
- Java shader packs (.zip), such as Complementary Unbound: shaderpacks, after installing Iris or OptiFine. The shader install guide covers Bedrock shaders too.
- Java data packs (.zip or folder), such as Terralith: inside saves, then the specific world's own folder, then datapacks. Data packs never sit at the top level of the game directory. If one does not show up, see fixing data packs that do not appear.
- Java maps and worlds, such as DreamDuo: saves. The map install guide covers Bedrock world imports too.
- Skins: applied from the in-game skin picker on Java. Bedrock skin packs (.mcpack) import the same way as other Bedrock packs.
- Server plugins (.jar), for Paper, Spigot, or similar server software: the plugins folder inside the server's own directory, not the player's game directory.
- Bedrock add-ons (.mcpack, .mcaddon), such as Better on Bedrock: imported by opening the file with Minecraft, then turned on per world.
Most of these stay zipped. Java resource packs and shader packs load straight from the .zip file, and unzipping one usually breaks it. A Java map is the exception: the world folder itself belongs directly inside saves, not a zip that contains another folder inside it. Data packs can be zipped or a plain folder, as long as pack.mcmeta sits at the top level of the pack.
Install Java mods with the right loader
A .jar mod needs three things to line up: the Minecraft version, the loader, and any required dependency mods. Fabric, Forge, NeoForge, and Quilt all read files from the same mods folder inside a profile, but they do not run each other's mods. A Fabric .jar dropped into a Forge or NeoForge profile is either ignored or it crashes the game when it starts.
Searching for mods without Forge usually means one of two things. For an alternative to Forge, Fabric, NeoForge, and Quilt are separate loaders that install the same way and read the same mods folder, so pick whichever loader the mod was built for. To skip installing a loader entirely, only data packs, resource packs, and shader packs (through Iris) work without one. A .jar mod always needs a loader of some kind.
Where is the Fabric mods folder?
Fabric does not use a separate folder. It reads from the same mods folder as Forge, NeoForge, and Quilt, inside that profile's .minecraft directory. ModMenu and Sodium, for example, both drop into that one mods folder. The loader only changes which jars it can run, not where they go.
- 1.Create or choose a profile set to the correct Minecraft version and loader, then run it once so its mods folder exists.
- 2.Download the .jar file built for that same Minecraft version and loader.
- 3.Open the profile's mods folder and drop the .jar file in directly. Do not unzip it.
- 4.Add any required dependency mods listed on the same download page, such as Fabric API for many Fabric mods.
- 5.Start the profile again and check the mod list or title screen for errors.
Install Bedrock add-ons and packs
Bedrock packs install by opening the downloaded file with Minecraft rather than copying it into a folder by hand. A .mcpack adds one pack, a .mcaddon can bundle a behavior pack and a resource pack together, and a .mcworld imports a full world.
- 1.Download the Bedrock file from the creator page or an accepted distribution page.
- 2.Open the .mcpack, .mcaddon, .mcworld, or .mcskin file with Minecraft.
- 3.Wait for the import confirmation before closing the app.
- 4.For a world add-on, open the target world's settings and turn on the behavior pack plus its matching resource pack.
- 5.Copy important worlds before testing a behavior pack or another add-on that changes gameplay.
Bedrock keeps its packs and worlds inside a folder named com.mojang, separate from the Java .minecraft directory entirely. On current Windows installs (Minecraft 1.21.120 and later, after Microsoft's move from UWP to GDK), that folder is at %appdata%\Minecraft Bedrock\users\shared\games\com.mojang. Older installs kept it nested at %localappdata%\Packages\Microsoft.MinecraftUWP_8wekyb3d8bbwe\LocalState\games\com.mojang instead. Importing through Minecraft itself, as above, avoids needing to find this folder by hand.
Quick checklist before you start Minecraft
- The file matches the edition: Java or Bedrock.
- The file matches the Minecraft version.
- The file matches the loader, if it is a Java mod.
- The file is in the folder for the exact profile, world, or server being used.
- Required dependency mods or companion packs are installed too.
- Important worlds are backed up before adding anything that changes terrain, entities, recipes, or world generation.
Fix the most common install mistakes
If a pack or mod does not appear, check the folder first. Resource packs do not go in mods, and mods do not go in resourcepacks. Data packs do not belong in the top-level game directory at all, only inside a world's own datapacks folder. When using a modpack app or a profile manager, open the profile folder from that app and add files there instead of guessing at the default .minecraft path. For fixes beyond folder placement, see the beginner troubleshooting checklist.
If Minecraft starts with an error, read the first lines of the error screen or log. The usual causes are a missing dependency, a mismatched Minecraft version, a mismatched loader, or two mods that do not work together. Remove the newest file added, restart once, then add files back one at a time until the problem is clear.
Once file locations are sorted, the beginner Minecraft resource roundup rounds up safe, well-supported picks across mods, shaders, and resource packs for a first setup.
