Learn · concepts
NeoForge vs Forge: Minecraft Mod Loaders Compared
NeoForge is the community fork that leads Forge-based modding on current Minecraft. Here's how the two differ and which one to pick.
NeoForge is the community-run fork of Forge that started in 2023 and now leads the Forge ecosystem on current Minecraft versions. Forge is the original loader that carried most large modpacks for years. Understanding the split and their differences helps you pick the right one for your setup.
What each one is
Forge is the original Minecraft mod loader, released around 2011. It dominated large-scale modding through the mid-to-late 2010s. Forge's architecture centers on an event bus, a registry system, and ASM-based class transformation.
NeoForge is a community fork that split from Forge in 2023. It keeps the same broad architecture (registries, capabilities, event bus) but runs under community governance with a more open contribution model and faster development cycles.
Why the fork happened
The split was about governance and leadership direction, not a technical rewrite. A group of Forge developers and community members moved to a community-owned project after disagreements over Forge's development pace and decision-making process. Because NeoForge started from Forge's codebase, the two loaders are recognizably related.
Over time, the two have drifted. NeoForge has reworked parts of the API, added new conventions, and updated internal systems. A mod built for modern NeoForge is not guaranteed to load on Forge, and vice versa.
How they differ
| Aspect | NeoForge | Forge |
|---|---|---|
| Origin | 2023 community fork | Original loader (~2011) |
| Governance | Community-owned, open contributions | Traditional Forge project leadership |
| Architecture | Same base (registries, capabilities, event bus) | Registries, capabilities, event bus |
| Version focus | Current Minecraft versions (1.20+) | Older and legacy versions |
| Development pace | Fast, responsive to community | Slower, carefully considered |
| Mod catalog | Growing on modern versions | Deep catalog on older versions |
| API stability | Changing, optimized for current versions | Stable, backward-compatible where possible |
Which versions each supports
NeoForge:
- 1.20.1, 1.20.4, 1.21+
- Active development, new versions supported quickly
- Where most active modding happens now
Forge:
- 1.12.2 and older (legacy support)
- 1.16.5, 1.17, 1.18, 1.19, 1.20.1 (but NeoForge preferred on newer versions)
- Slower updates for modern versions
Which to choose
Use NeoForge if:
- You play current Minecraft versions (1.20+)
- Your mods list NeoForge support
- You want actively maintained loader with community involvement
- You're building a new modpack
Use Forge if:
- You're running an older modpack built on Forge
- Your mods only support Forge
- You need maximum backward compatibility
- You play 1.12.2 or older (versions with no NeoForge support)
Check the mod's page. The same mod author often publishes Forge builds for old versions and NeoForge builds for new ones.
How to tell which loader a mod needs
- Go to the mod's download page (Modrinth, CurseForge, etc.)
- Look at the version list
- It will specify "Forge" or "NeoForge" for each release
- Download the build matching your loader
If you try to load a NeoForge mod on Forge, it crashes with a class-not-found error. The reverse also crashes. Version and loader must match exactly.
The modding ecosystem shift
The transition is still ongoing. Large, active mods have moved to or already support NeoForge on modern versions. Some legacy mods stick to Forge. For players on current versions, NeoForge is becoming the default; for players on 1.12.2 or running decade-old modpacks, Forge is still the standard.
Neither loader is disappearing. NeoForge is the forward-looking option; Forge maintains legacy support. The split means modders no longer wait for slow Forge updates to play on new versions.
Where Terminus fits
Terminus runs on Fabric, not the Forge family. Fabric is a separate, lighter ecosystem with its own mod format and API. If you want to run utility mods alongside Terminus, you use Fabric mods, not Forge or NeoForge mods. Fabric and Forge-family mods are not cross-compatible.
FAQ
On current Minecraft versions (1.20+), most of the community treats NeoForge as the successor for active modding. Forge still exists and serves older versions, so neither has fully replaced the other.
Not reliably. While the two share roots, the APIs have diverged enough that a mod built for Forge won't always load on NeoForge. Install the version your loader is built for.
No. NeoForge comes from the Forge lineage with an event-bus and registry system. Fabric is a separate, lighter loader with mixin-based patching. They're different ecosystems with different mod formats.
NeoForge is trending upward on current versions. Most active modding development now targets NeoForge on 1.20+. Forge remains dominant on older versions and legacy packs.