Fabric vs NeoForge vs Forge: which loader in 2026?
Choose the loader by the Minecraft version you target and the mods your players already use. On Modrinth, NeoForge has the most mods for 1.21.1, Fabric has the most for 1.21.11 and every 26.x version, and Forge has the most for 1.20.1 and older long-lived versions such as 1.16.5 and 1.12.2. All three are maintained for 26.x. If you only need to change a server and players should join without installing anything, write a Paper plugin instead of a mod.
Last checked on 3 November 2026, from each project’s own docs and version files and from Modrinth’s search API.
What are the loaders, in one table?
Section titled “What are the loaders, in one table?”| Fabric | NeoForge | Forge | Quilt | Legacy Fabric | |
|---|---|---|---|---|---|
| Minecraft versions | 1.14 to 26.3 (48 releases in Fabric’s metadata) | 1.20.1 (as net.neoforged:forge 47.1.x) and 1.20.2 to 26.3 |
1.1 to 26.3 (77 versions on Forge’s file site) | The official Quilt template stops at 1.20.6 | 1.3.1 to 1.13.2 (36 releases) |
| Newest build on 3 Nov 2026 | Loader 0.20.1 | 26.3.0.101 for 26.3 | 66.1.5 for 26.3 (66.1.0 recommended) | Loader 0.30.2 (0.31.0 in beta) | Loader 0.20.1 |
| Gradle plugin | Loom (net.fabricmc.fabric-loom, or -remap before 26.1) |
ModDevGradle or NeoGradle | ForgeGradle | Quilt Loom | Loom with legacy-looming |
| Its API | Fabric API (a separate mod) | Built into NeoForge | Built into Forge | Quilted Fabric API; Quilt Standard Libraries ended in December 2025 | Legacy Fabric API |
| Hooks into the game | Fabric API’s events, and Mixin | Events on a game bus and a mod bus, and Mixin | Events, and Mixin | Quilt and Fabric APIs, and Mixin | Legacy Fabric API, and Mixin |
| Runs other loaders’ mods | No | No | No | Most Fabric mods | No |
Sources for each cell are listed at the end. This guide covers 1.12.2 and newer.
How many mods does each loader have per version?
Section titled “How many mods does each loader have per version?”Mod projects on Modrinth that list both the loader and the Minecraft version:
| Minecraft | Fabric | NeoForge | Forge | Quilt |
|---|---|---|---|---|
| 1.12.2 | 167 | 84 | 2,748 | 63 |
| 1.16.5 | 3,067 | 519 | 4,292 | 885 |
| 1.18.2 | 5,461 | 805 | 6,060 | 2,131 |
| 1.19.2 | 7,575 | 1,040 | 8,187 | 3,145 |
| 1.20.1 | 17,894 | 5,149 | 25,476 | 4,991 |
| 1.20.4 | 10,167 | 4,353 | 6,076 | 3,373 |
| 1.21.1 | 19,929 | 21,847 | 5,544 | 4,854 |
| 1.21.4 | 13,831 | 9,541 | 4,407 | 4,320 |
| 1.21.11 | 18,228 | 8,350 | 4,565 | 4,481 |
| 26.1.2 | 13,591 | 8,456 | 3,521 | 3,503 |
| 26.2 | 13,645 | 7,125 | 3,550 | 3,525 |
| 26.3 | 9,144 | 5,241 | 2,649 | 2,699 |
| All versions | 47,608 | 30,474 | 35,572 | 10,613 |
One caveat: Modrinth’s search matches whole projects, so a mod with a Forge 1.20.1 file and a NeoForge 1.21.1 file also counts in the NeoForge 1.20.1 and Forge 1.21.1 cells. That inflates the smaller cells, but Forge leads on 1.20.1 and the older modpack versions, NeoForge leads on 1.21.1, and Fabric leads on every other version checked from 1.19.4 on (21 release versions were checked, and the table shows 12). CurseForge isn’t counted, because its API needs a key.
Which loader should you choose?
Section titled “Which loader should you choose?”| Your situation | Choose | Why |
|---|---|---|
| You’re adding to a modpack | The pack’s loader and version | A mod only loads on the loader it was built for |
| You target 1.20.1 | Forge, or Fabric | Forge has 25,476 mods there, Fabric 17,894 |
| You target 1.21.1 | NeoForge, or Fabric | NeoForge 21,847, Fabric 19,929; Forge only 5,544 |
| You target 1.21.11 or 26.x | Fabric, or NeoForge | Fabric has 1.6 to 2.2 times NeoForge’s count on each |
| You target 1.12.2 | Forge | 2,748 mods; Legacy Fabric exists but is small |
| You want one mod on several loaders | Fabric and NeoForge from one codebase | See below |
| You only change a server | A Paper plugin | See mods vs plugins |
If none of these fits, pick the loader whose docs you find easier to follow for your version. Fabric, NeoForge and Forge all have a version picker in their docs.
How does the code differ between Fabric and NeoForge?
Section titled “How does the code differ between Fabric and NeoForge?”The game’s code is the same. What differs is how you register things and hook into the game. Here is a block registered on 1.21.1 in the two tested templates:
Fabric registers straight into the game’s registry when the class loads:
public static final Block RUBY_BLOCK = register("ruby_block", new Block(BlockBehaviour.Properties.of().strength(5.0F, 6.0F)));
private static Block register(String name, Block block) { return Registry.register(BuiltInRegistries.BLOCK, GuideMod.id(name), block);}NeoForge queues the block in a DeferredRegister, which registers it at the right moment on the mod event bus:
public static final DeferredRegister.Blocks BLOCKS = DeferredRegister.createBlocks(GuideMod.MOD_ID);
public static final DeferredBlock<Block> RUBY_BLOCK = BLOCKS.registerSimpleBlock("ruby_block", BlockBehaviour.Properties.of().strength(5.0F, 6.0F));NeoForge’s docs warn: “Do not call new Block() outside registration! As soon as you do that, things can and will
break.” Forge uses the same DeferredRegister idea, because NeoForge started as a fork of it.
Where the loader has no event for what you need, all three use Mixin, which changes the game’s classes as they load.
NeoForge posts gameplay events on its game bus (NeoForge.EVENT_BUS) and setup events, such as registration, on the
mod bus each mod gets in its constructor (NeoForge: Events).
The full block, with every file it needs, is in How to add a block.
What is the difference between Forge and NeoForge?
Section titled “What is the difference between Forge and NeoForge?”NeoForge began on 12 and 13 July 2023, when most of Forge’s team left and started the NeoForged project. Its first post
says “NeoForged is a fork of MinecraftForge” and “We remain compatible with existing Forge for the present time”
(NeoForged, 13 July 2023). Its 1.20.1 builds were still published as
net.neoforged:forge 47.1.x. With 1.20.2 the package became net.neoforged and the mod id neoforge
(NeoForge 20.2, 30 October 2023), so from 1.20.2 a mod is built for one or
the other. Forge is still released, and its file site lists builds for 26.3 (66.1.5 latest, 66.1.0 recommended on
3 November 2026).
Is Quilt still worth it?
Section titled “Is Quilt still worth it?”Quilt Loader loads most Fabric mods. Quilt’s FAQ says “In most cases, yes! We have a list of all Fabric mods that aren’t compatible with Quilt, and it’s a pretty small number.” Quilt-only mods don’t run on Fabric. Quilt Loader has “been in beta since April 2022”, and Quilt Standard Libraries were discontinued in December 2025 because “keeping up with new releases of Minecraft while maintaining compatibility with Fabric API wasn’t feasible” (Quilt FAQ). For a new mod, Fabric reaches Fabric and Quilt players both.
What is Legacy Fabric for?
Section titled “What is Legacy Fabric for?”Legacy Fabric brings Fabric Loader to old versions, 1.3.1 to 1.13.2 in its metadata (legacyfabric.net). It is the Fabric option for 1.12.2 and 1.8.9. On 1.12.2, Forge has far more mods (2,748 against Fabric’s 167 on Modrinth).
Can one mod run on several loaders?
Section titled “Can one mod run on several loaders?”Yes, from one codebase, though each loader still gets its own jar. You put shared code in a common module and add a
small module per loader that registers things the loader’s way. Architectury and
the MultiLoader Template are two community setups for this.
Plan for it early, because the registration code above is where the loaders differ most.
Should you write a mod or a plugin?
Section titled “Should you write a mod or a plugin?”| Mod (Fabric, NeoForge, Forge) | Plugin (Paper, Spigot, Bukkit, Purpur) | |
|---|---|---|
| Runs on | The client, the server or both | The server only: Paper loads plugins “from the plugins folder in the server directory” |
| Players install | The mod and its loader, to use client-side content | Nothing |
| What you write against | The game’s own code, with the loader’s API and Mixin | The server API (Bukkit, Spigot or Paper API) |
| Entry point | A ModInitializer or an @Mod class |
A class that extends JavaPlugin, named in plugin.yml |
| Java on 26.x | 25 | 25 (“Paper requires at least Java 25 to run”) |
Plugins suit server rules, commands, minigames and economy. New blocks, items, mobs and textures need a mod. See How to make a Paper plugin.
In Linen
Section titled “In Linen”Linen is a desktop IDE for Minecraft mods and plugins, in private beta.
- New mod writes projects for Fabric, Forge, NeoForge, Quilt and Legacy Fabric, and plugins for Paper, Spigot, Bukkit and Purpur, on any version from 1.12.2 to 26.x. Free covers one mod across several loaders and versions too.
- One mod can target several loaders and versions in one Linen window. Linen’s multi-loader templates (a
commonmodule and one per loader for Fabric, NeoForge and Forge) cover 1.20.1, 1.21.1, 1.21.11, 26.2 and 26.3. - The Java, Gradle and plugin versions each template writes are listed in Set up by loader.
Sources
Section titled “Sources”Checked on 3 November 2026.
- Fabric: game versions and loader builds from meta.fabricmc.net/v2/versions; Fabric for Minecraft 26.1 (Loom plugin ids, Yarn)
- NeoForge: builds from maven.neoforged.net
and, for 1.20.1,
net.neoforged:forge; “What is happening?” - The NeoForged project (13 July 2023); NeoForge 20.2 for Minecraft 1.20.2 (30 October 2023); Blocks (1.21.1), Events (1.21.1) - Forge: promotions_slim.json (latest and recommended builds for every version, 1.1 to 26.3)
- Quilt: Quilt FAQ; loader builds from meta.quiltmc.org
- Legacy Fabric: game versions and loader builds from meta.legacyfabric.net
- PaperMC: How plugins work, Getting started
- Modrinth: search API, with the facets
project_type:mod,categories:<loader>andversions:<version>