Server Software

Spigot vs Paper: Which One to Run

Both run your Bukkit plugins. Paper is a fork of Spigot that holds a flatter TPS, fixes more bugs, and exposes far deeper config. For nearly every server in 2026, Paper is the right default, here is exactly why and when Spigot still makes sense.

console,  same hardware, same 12 plugins
SPIGOTstable
$ java -jar spigot-1.21.4.jar nogui
[INFO]: Loading libraries, please wait...
[INFO]: Done (14.812s)! Type "help"
> tps
TPS: 16.40, 17.92, 18.10
> timings report
chunk gen + entities heavy
PAPERoptimized
$ java -jar paper-1.21.4.jar nogui
[INFO]: Applying optimizations...
[INFO]: Done (9.204s)! For help, type "help"
> tps
TPS: 20.0, 20.0, 19.98
> spark profiler
MSPT: 8.1ms  flat 20 TPS
Spigot~17 TPS
Paper20 TPS

The short version

1
Know the family tree
Bukkit defined the plugin API, Spigot forked it for performance, and Paper forks Spigot again with deeper optimizations. Paper is a strict superset, so anything that runs on Spigot runs on Paper.
2
Check plugin compatibility
Both load the same Bukkit/Spigot plugins (EssentialsX, LuckPerms, WorldEdit, Vault). Paper adds its own API events that newer plugins target, so some plugins are Paper-only, almost none are Spigot-only.
3
Compare the performance
Paper rewrites chunk loading, entity ticking, and collision math. On the same hardware you typically hold a flat 20 TPS where Spigot dips to 16-18 during chunk gen or large mob farms.
4
Look at the config depth
Spigot gives you spigot.yml and bukkit.yml. Paper adds paper-global.yml and per-world paper-world.yml with hundreds of tunables: mob spawn limits, redstone modes, anti-xray, view-distance per world.
5
Pick Paper unless you have a reason
Download paper-VERSION.jar from papermc.io, swap your jar, restart. Your worlds and plugins carry over untouched. Choose plain Spigot only if a specific tool you depend on explicitly refuses Paper.

What you need

paper-VERSION.jar

Flat 20 TPS

paper-world.yml

Same plugins

Quick answers

Is Paper just Spigot with extra features?

Paper is a downstream fork of Spigot. It includes everything Spigot does, then layers on performance patches, bug fixes, and an expanded API. Think of it as Spigot+.

Will my Spigot plugins break on Paper?

Almost never. Paper keeps full Bukkit and Spigot API compatibility, so EssentialsX, LuckPerms, WorldGuard and the rest load unchanged. Migration is usually just swapping the jar.

Does Paper really run faster?

Yes, measurably. Paper's async chunk loading and optimized entity ticking keep TPS near 20 under load where Spigot drops. The gap widens on bigger servers and busier farms.

Can I switch from Spigot to Paper without losing my world?

Yes. Stop the server, replace spigot.jar with paper.jar, start it again. Paper reads the same world folders and plugin data. Always back up first, but no conversion is needed.

Is there any downside to Paper?

Paper changes some vanilla edge-case behaviors for performance (certain redstone and duplication mechanics). Most servers want those changes, but tech players who rely on exact vanilla quirks should test first.

What about Purpur or Folia?

Purpur forks Paper for more gameplay toggles. Folia forks Paper for multi-threaded regions on huge servers. Both build on Paper, which is why Paper is the sensible default base.