Paper vs Spigot vs Vanilla: Which server should you use?

Choose Vanilla for the closest match to Mojang's unmodified dedicated server, Spigot when you need Bukkit plugins and specifically target Spigot, and Paper for most modern plugin-based servers that want broader configuration and performance tooling.

Paper is not a magic replacement for good hardware or careful plugins. It is a server implementation with different goals and some behavior changes.

Quick comparison

Server software	Plugins	Main strength	Main tradeoff
Vanilla	No Bukkit/Paper plugins	Closest to Mojang behavior	Fewer administration and optimization tools
Spigot	Bukkit/Spigot plugins	Established plugin compatibility	Fewer Paper-specific features and fixes
Paper	Bukkit, Spigot, and Paper plugins	Performance focus, configuration, profiling	Some technical behavior differs from Vanilla

Mods are a separate ecosystem. Fabric, Forge, and NeoForge are not interchangeable with Bukkit-style plugins.

Vanilla server

The Vanilla dedicated server is Mojang's reference implementation. It is the best baseline when exact behavior matters more than plugins or advanced administration.

Choose Vanilla when:

You want an unmodified private survival experience.
A technical build depends on Vanilla-specific behavior.
You do not need Bukkit-style plugins.
You want to reproduce a bug against Mojang's server.

Vanilla still supports datapacks and normal server configuration. It simply does not load the plugin ecosystem that Spigot and Paper expose.

Spigot server

Spigot provides the Bukkit plugin API and has powered plugin servers for years. Many plugins label themselves “Spigot” because that API became the common compatibility target.

Choose Spigot when a plugin vendor explicitly supports it but not Paper, or when you have a tested deployment whose behavior you do not want to change. For a new server, verify whether the same plugins support Paper before deciding.

Paper server

Paper describes itself as a Minecraft Java server designed to improve performance and provide more advanced features and API. Paper is a drop-in replacement for CraftBukkit or Spigot in the ordinary migration path, according to its getting-started documentation.

Paper also bundles the spark profiler in current releases, making it easier to investigate tick-time problems. Its configuration exposes many controls, but changing every setting for a lower number can alter gameplay. Optimize against a measured problem.

Choose Paper when:

You want Bukkit/Spigot plugins on a new server.
You value integrated performance diagnostics.
You need Paper-only plugins or APIs.
You are willing to test technical farms and plugin behavior after migration.

Will Spigot plugins run on Paper?

Most conventional Bukkit and Spigot plugins run on Paper, but “most” is not a guarantee. Native code, unsupported internals, version-specific hooks, and unusual loading relationships can fail.

Back up first, update the plugins, start a copy of the world, and inspect logs/latest.log. Paper documents plugin dependencies and duplicate-plugin failures in its installation guide.

Does Paper automatically fix lag?

No. Paper can reduce or move some work and gives operators better controls, but it cannot make an overloaded main thread finish inside the 50 ms tick budget. A heavy plugin, uncontrolled entities, live chunk generation, slow storage, or host CPU contention can still produce low TPS.

Use the TPS and spark profiler guide to measure the cause. If performance changes with the time of day rather than your own workload, check the host contention guide.

What gummies.cloud supports

Paper is the native launch server type in gummysnacks. The panel provisions it and provides live console access, command completion, file editing, SFTP, backups, settings, and dashboard TPS. Additional native game types and customer-defined templates are planned, not launch claims.

Sources and review

Reviewed July 15, 2026 against Paper's administration documentation, Paper's migration notes, and its Paper plugin reference.