Paper or Fabric? Start with the extensions you need
Choose Paper for Bukkit, Spigot or Paper plugins. Choose Fabric when your mods or modpack require Fabric. For a survival server with permissions, land protection and administration plugins, Paper is a practical starting point. For a particular modpack, follow the loader and Minecraft version specified by its author.
| Decision | Paper | Fabric |
|---|---|---|
| Extensions | Bukkit, Spigot and Paper plugins; check each plugin's supported versions | Fabric-compatible mods and their dependencies |
| Player setup | Usually an ordinary Java client | Server-only mods may allow ordinary clients; content mods often require matching client mods |
| Performance | Server optimizations and profiling tools | A mod loader; performance improvements depend on the mods you install |
| Vanilla mechanics | Some mechanics differ from Vanilla | Depend on the chosen mods |
| Docker server type | TYPE: PAPER | TYPE: FABRIC |
Plugins and mods solve different problems
Paper's plugin ecosystem is useful for managing a shared server: permissions, moderation, protection, economies or minigames. Check that each plugin supports your Paper and Minecraft versions. A plugin targeting an older release is not guaranteed to work just because its loader is compatible.
Fabric lets you assemble a modded setup. Some mods only change server behavior, while others add blocks, items or systems that players also need on their clients. Read each mod's installation requirements, including dependencies such as Fabric API where required. Keep the Minecraft version, loader and mod versions aligned across the server and the clients that need them.
Paper does not load Fabric mods, and Fabric does not load Paper plugins. Choosing one ecosystem means choosing its extensions too; a similar feature in the other ecosystem may have different settings and stored data.
Performance and Vanilla behavior are separate choices
There is no useful universal claim that Paper is faster than Fabric. A lightly configured Paper server and a Fabric server with several performance mods are different workloads. Player activity, world generation, entities, view distance and individual extensions can dominate the result.
If your current server lags, first use the TPS/MSPT and profiling guide. Compare the same world, hardware and player activity before deciding that another server type fixes the problem.
For technical survival, test the farms and redstone mechanics you actually use. Paper has behavior changes and configurable alternatives; its Vanilla-like experience guide explains the relevant settings. Adjusting them can also affect performance. Fabric's behavior depends on its installed mods, so a performance mod should be evaluated for its mechanics as well as its speed.
Choose the official Vanilla server if the unmodified server implementation is your priority and you do not need a plugin or mod loader. Datapacks can still customize gameplay, but they do not provide the Paper plugin or Fabric mod APIs.
What about Forge, NeoForge and Quilt?
Use Forge, NeoForge or Quilt when the mods or pack you want name that loader. They have their own installation and compatibility requirements. Do not substitute Forge for NeoForge, or Quilt for Fabric, without confirming support for the exact pack release and every dependency.
For an existing modpack, start from its server installation instructions rather than building a new combination of loaders and mods yourself.
Plan the migration before switching software
Back up the complete server while it is stopped, then test the switch on a separate copy. Include worlds, player data, plugin or mod configuration and any external databases used by extensions.
World storage layouts and migration steps can differ by server release. Follow the Paper migration documentation for your starting software and target version, including any intermediate conversion it requires. Changing only the JAR or Docker TYPE is not a migration plan.
A world with modded blocks, items or other custom data cannot be assumed to survive a move to Paper or Vanilla intact. Plugins also need replacement mods when moving to Fabric, and their data may need a separate conversion. On the test copy, check every dimension, player inventories, important builds and extension data before reopening the live server.
Generate the Docker configuration for your choice
In the Minecraft Docker Compose Generator, select Paper or Fabric and the Minecraft version you intend to run. The generated configuration uses itzg/minecraft-server; choose the Java image tag required by your server or pack using the Java version guide.
For a new server, follow the generator's quick start to save and run the Compose file. For an existing server, preserve its data mounts and settings, and complete the migration test before using the new configuration in production.