If you’ve outgrown vanilla Minecraft and want to add mods to your home server, the first decision you’ll face is which mod loader to use. Forge and Fabric are the two major options, and picking the right one shapes which mods you can run and how your server performs. Here’s how they compare, plus how to actually set either one up using the same Docker image from our setup guide.

Forge vs. Fabric: The Quick Answer

• Pick Fabric for lightweight setups, performance-focused mods, quality-of-life additions, and the fastest support for brand-new Minecraft versions and snapshots
• Pick Forge (or its modern successor, NeoForge, on 1.21+) for large “kitchen-sink” content modpacks and access to a deep legacy mod library going back years

What Is Fabric?

Fabric is a modular, lightweight mod loader made up of two parts: Fabric Loader (the minimal bootstrap that loads mods) and Fabric API (a separate mod most other Fabric mods depend on for extra functionality).

Strengths:

• Lightweight — lower resource overhead than Forge
• Fast to support new Minecraft versions, often within days of release
• Popular for performance mods (like Sodium) and smaller, focused mod collections

Trade-offs:

• Smaller overall mod library compared to Forge’s legacy catalog
• Less suited for massive “everything and the kitchen sink” content modpacks

What Is Forge (and NeoForge)?

Forge has been the dominant modding platform for most of Minecraft’s history, with an enormous, mature mod ecosystem spanning nearly every Minecraft version back to the very early days. NeoForge is a community fork that has taken over much of Forge’s momentum on modern versions (1.21+), so on newer Minecraft releases, NeoForge is generally the one to look for rather than classic Forge.

Strengths:

• Massive, mature mod ecosystem — ideal for large tech, magic, or “kitchen sink” content packs
• Deep legacy support if you want to run an older modpack on an older Minecraft version

Trade-offs:

• Heavier and more resource-intensive than Fabric due to its broader API surface
• Typically slower to support brand-new Minecraft versions compared to Fabric

Setting Up a Fabric Server

Using the same itzg/minecraft-server image from our main setup guide, switching to Fabric is just a matter of adding one environment variable:

docker run -d -it \
  -p 25565:25565 \
  -e EULA=TRUE \
  -e TYPE=FABRIC \
  -v /path/to/data:/data \
  --name mc-fabric-server \
  itzg/minecraft-server

By default, this installs the latest Fabric loader against the latest Minecraft version. Most Fabric mods also require the Fabric API mod itself to be installed alongside them — you can add it automatically through the image’s Modrinth integration by including it in your mods list.

Setting Up a Forge or NeoForge Server

Same image, different TYPE value:

docker run -d -it \
  -p 25565:25565 \
  -e EULA=TRUE \
  -e TYPE=NEOFORGE \
  -v /path/to/data:/data \
  --name mc-forge-server \
  itzg/minecraft-server

Use TYPE=NEOFORGE for modern versions (1.21+), or TYPE=FORGE if you’re specifically targeting an older Minecraft version that predates the NeoForge split.

Adding Mods

Once your server type is set, adding mods generally works the same way regardless of loader:

• Drop mod .jar files into a /mods folder mounted to the container, or
• Use the image’s built-in Modrinth or CurseForge integration to automatically download and install specific mods by name, keeping everything managed through environment variables rather than manual file management

One important distinction: mods (used by Forge/Fabric/NeoForge) generally need to be installed on both the server and every connecting client, while plugins (used by server-only platforms like Paper or Spigot) only need to be installed on the server itself. Don’t mix up the two when following mod installation instructions.

Memory Considerations for Modded Servers

Modded servers need meaningfully more RAM than vanilla — see our RAM and CPU requirements guide for specifics, but as a general rule, budget significantly more headroom than you would for a vanilla server, especially for large Forge/NeoForge content packs.

Which Should You Actually Choose?

If you’re not sure yet, ask yourself what you want out of modding:

• Want a handful of performance and quality-of-life mods, and care about running the newest Minecraft version quickly? → Fabric
• Want to run (or build) a large, deep content modpack with hundreds of mods? → Forge/NeoForge

There’s no wrong answer here — plenty of servers run happily on either, and the “right” choice comes down entirely to which mods you actually want to play with.

Getting Started

If you haven’t set up your base server yet, start with our Minecraft home server guide, then come back and swap in the TYPE variable above once you’re ready to go modded.