Forge vs Fabric vs Paper: Minecraft Server Software Explained
Pick the right server type up front — it decides whether your server runs plugins, mods, both, or neither.
By Lodgichost Team · Last updated: August 19, 2026
The software you choose when creating a server is the single most important hosting decision, because it decides everything that can run on that server afterwards. Paper is the high-performance fork of Spigot that powers most vanilla-style servers and runs Bukkit API plugins such as ranks, protections, and economies. Forge is the heavyweight mod loader with the largest mod library, and NeoForge is its community-maintained successor for modern versions. Fabric is the lightweight alternative, popular for performance and quality-of-life mods. Vanilla runs only the official Mojang jar with no extras. Your choice is practically permanent: switching software means reinstalling and re-uploading your world. Match the type to your community before you start.
The Three Server Types at a Glance
Every Minecraft server runs on executable server software. Vanilla is the official Mojang jar that adds nothing new. Paper is a fork of Spigot, which is itself a fork of the vanilla server tuned for performance and management — it exposes the Bukkit plugin API. Forge is a mod loader: the Forge server jar loads mods written against its API. Fabric is a separate, younger loader with its own smaller API. The practical rule is simple: plugins belong to the Paper family, mods belong to the loaders, and the two worlds only meet inside experimental hybrid forks.
Server type API/loader Mods Plugins Notes Vanilla official jar No No stock behaviour Paper Spigot -> Bukkit No Yes perf fork; plugin standard Forge Forge loader Yes No large mod library Fabric Fabric API Yes No lightweight; perf mods
Plugins (Paper) vs Mods (Forge, Fabric)
A plugin is a single .jar file dropped into the plugins/ folder of a Paper server. Players install nothing, and the game client is never modified. A mod is a .jar loaded by Forge, NeoForge, or Fabric on the server and on every connecting client, and the version set must match exactly. Because plugins go through the Bukkit API, they mix freely and usually survive server updates with a simple re-upload.
- Plugins: /plugins/ folder on Paper, no client setup for players, ideal for survival, minigames, and moderation tools.
- Mods: /mods/ folder on the server and on every client, with the same loader, the same Minecraft version, and the same mod choices, or clients get kicked.
- A mod set mismatch shows up as a registry difference or an immediate disconnect the moment a player tries to join.
Forge and NeoForge in Depth
Forge has been the dominant mod loader since 2011 and hosts the largest mod library of any loader. From version 1.13 on, Forge maintains a separate loader build for every Minecraft version, and modern versions in the 1.20.1+ range are handled by NeoForge, the community-maintained continuation. The loader version and the Minecraft version are both part of the install's identity, and both have to match the client. Modpacks built on Forge are usually large, RAM-hungry bundles of tech, magic, and exploration mods.
Forge server jar: forge-1.20.1-47.2.0.jar
NeoForge server: neoforge-1.20.1-47.1.106.jar
Rule: same Minecraft version + same loader version +
the same mod set on the server and every clientFabric: The Lightweight Loader
Fabric loads mods through a small API plus a tiny services layer, which lets it boot faster and use less baseline memory than Forge. Most performance mods such as Sodium, Lithium, and Phosphor target Fabric first, which makes it the favourite for hardware-unfriendly packs and vanilla-plus servers. Fabric mods still demand version precision: each mod declares a supported Minecraft range, and the loader refuses to start on an incompatible combination.
Hybrid Forks and How Server Software Is Installed
Hybrid forks such as Mohist and Arclight try to load Forge mods and Bukkit plugins at the same time. They exist but lag upstream versions, and their interactions are the first place you find crashes, so treat them as experimental. In the Lodgichost panel you choose the software when the server is created; after that, moving from Paper to Forge is a full reinstall that wipes the world unless you back it up first. For most new servers, Paper is the correct default.
In the panel (at creation): Software -> Paper (default), Forge, NeoForge, Fabric, Vanilla Modpack install: one unit = many mods + loader + config Plugin install: drop a single .jar into plugins/ Switching: software change = reinstall; re-upload your world backup Tip: start with Paper unless you know you need mods
Troubleshooting
- Client can't join with 'Outdated client': update the client to the server's exact Minecraft version.
- Forge or Fabric server won't start: check the loader version matches the Minecraft version and that every mod jar is present.
- Players get kicked with a registry mismatch: a client has a different mod set from the server; compare the mods/ folders on both sides.
- Plugin simply doesn't work: it targets the wrong API — confirm it is a Paper/Spigot plugin, not a Fabric or Forge mod.
FAQ
Which server type should I start with?
Paper. It runs Bukkit plugins, performs better than vanilla, and asks nothing from players. Move to a mod loader only when your community explicitly wants mods.
Can Paper run Forge mods?
No. Paper runs Bukkit and Spigot plugins only. Forge mods need a Forge or NeoForge server, except inside experimental hybrid forks such as Mohist or Arclight.
Do players need to install mods themselves?
For mods, yes — every client must run the same loader and mod set as the server. For plugins, no; plugins are entirely server-side.
What is NeoForge?
NeoForge is the community-maintained successor to Forge used for modern Minecraft versions around 1.20.1 and newer. Servers on those versions typically install NeoForge instead of legacy Forge.
Can I switch from Paper to Forge later?
Yes, but it requires a reinstall, and the world resets unless you back it up in the panel and re-upload it after the switch.
Related Guides
- Installing Modpacks — a modpack is many mods plus a loader
- Installing Plugins — the Paper side of the plugin story
- Server Mods vs Plugins — the exact install paths for each
