Minecraft Forge and the Other Mod Loaders

Vanilla Minecraft has no plugin system. The game code is compiled, closed, and has no concept of third-party additions. A mod loader solves that by inserting itself between the game and your mods: it patches the game at runtime, exposes a stable set of hooks that mods can attach to, and resolves the dependency graph between the mods you have installed.

That last job matters more than people expect. When forty mods all want to modify how the world generates, something has to arbitrate. The loader is what stops them overwriting each other, and it is also what fails loudly when two mods genuinely cannot coexist.

Because each loader patches the game differently, mods are compiled against one specific loader. A Fabric mod contains Fabric-specific entry points. Drop it into a Forge installation and the loader simply does not recognise it — no error, or a cryptic one, and no mod.

Forge is the original. It has the deepest historical catalogue, particularly for versions 1.12.2 through 1.20.1, and the large tech and magic mods that defined modded Minecraft were built on it. Its development slowed considerably, and for current versions it has effectively been superseded.

NeoForge is a 2023 fork of Forge created by most of Forge's own contributors after a governance dispute. For 1.20.2 and newer it is where Forge-style development actually happens. If a guide tells you to install Forge for 1.21, it is out of date — you want NeoForge.

Fabric is a lightweight alternative built around fast updates. It typically supports a new Minecraft version within days of release, where Forge historically took months. It dominates performance mods, visual mods and quality-of-life additions.

Quilt is a fork of Fabric with a different governance model and some technical additions. It can load most Fabric mods. Its ecosystem is small and, for a beginner, there is no compelling reason to choose it.

The numbers below are pulled live from Modrinth's public API, counting how many mods declare support for each loader. They overlap — plenty of mods ship for two or three — but the shape of the result is clear enough.

Fabric now carries more mods than Forge. That single fact reverses the advice on a large number of guides still ranking well in search, most of which were written when Forge was the assumed default and never revisited.

Download the installer from files.minecraftforge.net, choosing the version that matches the Minecraft version you intend to play. The site offers a Latest and a Recommended build — take Recommended unless a specific mod tells you otherwise.

The download is a .jar file. Run it, select 'Install client', and point it at your .minecraft directory if it does not find it automatically. It writes a new launcher profile rather than modifying your existing installation, so nothing you already have is at risk.

Open the Minecraft launcher, pick the new Forge profile from the dropdown next to Play, and launch once. That first launch creates the mods folder. Quit, add your .jar files to it, and launch again.

Every mod page on Modrinth and CurseForge lists supported loaders and Minecraft versions before you download. On Modrinth these appear as filter chips at the top of the files list; on CurseForge they are columns in the file table.

Filter first, download second. The most common installation failure in modded Minecraft is not a broken mod — it is the right mod for the wrong loader, downloaded because someone grabbed the top file without checking.

If a mod offers builds for several loaders, they are separate downloads. Grabbing the Fabric build and the Forge build and putting both in the same folder causes exactly the conflict it sounds like it would.

No, and this comes up constantly. They patch the game in incompatible ways and cannot occupy the same profile. There is no configuration that makes it work.

What you can do is keep separate profiles or separate instances — one Fabric, one NeoForge — and switch between them from the launcher dropdown. Tools like Prism Launcher make this considerably tidier, giving each instance its own mods folder, its own configs and its own memory allocation.

A partial exception worth knowing: Sinytra Connector is a compatibility layer that can run some Forge mods inside Fabric. It works for a subset of mods and breaks on others. It is not a general solution and is not something to rely on while you are learning.

If you have been away from modding for a couple of years, you may have a working Forge setup on 1.20.1 and a desire to move to something current. The migration is less painful than it sounds, but it is not a drop-in replacement and you should not try to convert an existing profile in place.

Create a new profile rather than editing the old one. NeoForge and Forge write different metadata, and mixing them in one installation produces confusing failures that look like mod problems. Keeping the old profile intact also means you can go back if a mod you rely on has not been ported.

Then check each mod individually. Most actively maintained mods now publish NeoForge builds alongside Forge ones, but abandoned mods never will. That is the real cost of migrating: any mod whose author stopped updating is left behind on 1.20.1 permanently.

Worlds do not transfer cleanly between major versions either. A world built on 1.20.1 with a hundred Forge mods will not open sensibly on 1.21.4 with their NeoForge equivalents, because block and item identifiers change. Treat a loader migration as a fresh start rather than a continuation.

The official Minecraft launcher updates the vanilla release automatically. That is convenient for vanilla players and actively hostile to modded ones, because a loader install is bound to one exact Minecraft version.

The symptom is familiar: everything worked last week, you did not change anything, and now nothing loads. What changed is that the launcher quietly moved your installation to a newer release which your loader does not support.

The fix is to pin the version. In the launcher's Installations tab, edit the profile and set the version explicitly rather than leaving it on latest-release. A modded profile should always name a specific version.

Third-party launchers such as Prism handle this properly by default, giving each instance a fixed version that nothing can move. That is one of the better arguments for using one once you are running more than a single mod setup.

Occasionally the problem is not a mod but the installer. Three failures come up repeatedly and all three have quick answers.

If the installer will not open at all and nothing happens when you double-click it, you probably have no Java runtime available outside Minecraft, or .jar files are associated with an archive tool. Installing a JDK, or running the file from a terminal with java -jar, resolves it.

If the installer reports that it cannot find the Minecraft directory, point it at the folder manually — it offers a browse button. This is common when the game was installed somewhere non-standard or through a package manager on Linux.

If the install completes but no new profile appears in the launcher, the launcher was open during installation. Close it completely, reopen it, and the profile will be there.