Minecraft mods end up scattered across a few different locations depending on how they were installed, which is why “just delete the mod” sometimes leaves more behind than expected. The right removal steps also depend on which loader you’re running, since Forge, Fabric, and custom launchers like FTB or Technic each organize files a little differently.
Check which loader your profile uses first
Open the Minecraft Launcher and go to Installations. Find your modded profile and confirm exactly what it says, something like Forge 1.20.1 or Fabric 1.21. This matters because deleting files from the wrong loader’s folder structure won’t actually remove anything, and mixing up Forge and Fabric mod files is a common source of confusion when a “removed” mod still somehow loads.
Removing individual mod files
For a standard Forge or Fabric setup, the mods themselves live in one folder, and getting there is the same regardless of which loader you’re using.
- Open the Minecraft Launcher and select your modded profile.
- Go to Installations, hover over the modded installation, and click the folder icon. This opens your main
.minecraftdirectory directly, without you needing to hunt through AppData manually. - Open the
modsfolder inside it. Every installed mod shows up here as a.jarfile. - Delete the
.jarfile for whichever mod you want removed, or delete all of them if you’re clearing the profile entirely.
Large modpacks built for FTB or Technic work differently, since those run through their own custom launchers rather than the standard Minecraft Launcher. In that case, the mods aren’t in a shared folder at all, they’re bundled inside that specific pack’s instance folder, so removing the pack means deleting the entire instance rather than picking through individual files.
Cleaning up configuration and leftover data
Deleting the .jar file removes the mod itself, but most mods also write settings, cache data, or generated content elsewhere in the .minecraft folder that a simple file deletion doesn’t touch.
- Open the
configfolder inside.minecraftand look for files or subfolders matching the mod you removed. Delete only those, since this folder holds settings for every mod and for the loader itself, not just the one you’re removing. - Check the main
.minecraftfolder for standalone folders some mods create outside ofconfig, things likejourneymaporschematicsare common examples. Delete these if you want a fully clean removal. - If the mod you removed was a dependency for other mods, or depended on a separate API mod itself, check whether those related mods are now doing nothing on their own. Orphaned dependency mods don’t cause errors most of the time, but they’re dead weight if the mod that needed them is gone.
Removing the mod loader entirely
If Forge or Fabric was only installed to support mods you no longer want, you can remove the loader itself and return to a vanilla setup rather than just clearing out the mods folder.
- Open the Minecraft Launcher and go to Installations.
- Find the modded profile, listed under its loader name and version.
- Click the three dots next to it and select Delete.
This removes the modded profile and the loader files tied to it, while leaving your base Minecraft installation and your saved worlds completely untouched.
Confirming everything worked
Restart the Minecraft Launcher, select a vanilla profile, and launch the game once to confirm it starts cleanly with no errors referencing mods or a loader that no longer exists. This applies the same way whether you were running Forge or Fabric, since both leave the same kind of leftover error if something wasn’t fully removed. If you’re loading an existing world that previously had modded content in it, don’t be surprised by a warning about missing registry entries when it loads. This is expected, not a sign anything went wrong. Minecraft simply discards the content it can no longer recognize and continues loading the rest of the world normally.
A quick reference by situation
| What you want to do | Where to look |
|---|---|
| Remove one specific mod | .minecraft/mods folder, delete that mod’s .jar |
| Remove an FTB or Technic modpack | Delete the entire instance folder in that launcher |
| Clear mod settings and generated data | .minecraft/config and mod-specific folders in the root directory |
| Return to vanilla Minecraft entirely | Delete the modded profile from Installations in the launcher |
Conclusion
Removing a Minecraft mod cleanly comes down to knowing that a single .jar file rarely tells the whole story. The mod itself, its configuration, any generated data folders, and the loader profile it depends on are four separate things that can each be left behind if you only handle one of them. Working through them in order, mod file, config and data, then the loader profile if you want it gone too, is what actually gets you back to a clean installation rather than one that just looks clean until something references a file that’s no longer there.