Vanilla vs Paper: Performance Difference Explained
Why Paper exists, what it changes compared to vanilla Minecraft server, performance benchmarks, and when you should stick with vanilla.
The vanilla Minecraft server (the .jar Mojang distributes) is the baseline that every fork builds on. Paper is the most popular fork, used by the majority of public servers. But what exactly does Paper change, and when should you stick with vanilla? This guide explains the performance differences and trade-offs.
What the vanilla server does
The vanilla server runs Minecraft exactly as Mojang coded it, including all its inefficiencies. It is single-threaded, loads chunks synchronously, processes every hopper every tick, lights chunks on the main thread, and does not expose a plugin API. It is the reference implementation: every vanilla mechanic works exactly as intended, and every redstone contraption behaves precisely as designed.
What Paper changes
Paper applies hundreds of patches to the vanilla server. The major categories are:
- Async chunk loading: Chunks load on worker threads instead of blocking the main tick loop. This eliminates the biggest source of lag spikes on vanilla servers.
- Starlight lighting engine: A completely rewritten lighting engine that is orders of magnitude faster than vanilla's.
- Hopper optimization: Paper skips empty-inventory checks and reduces item search frequency, cutting hopper-related lag by 80%+ on servers with large sorting systems.
- Entity activation range: Entities far from players tick less frequently. A zombie 48 blocks away does not need full AI every tick.
- Anti-exploit patches: Fixes for chunk banning, book exploits, map exploits, and other known griefing vectors that Mojang has not patched.
- Plugin API: Full Bukkit/Spigot/Paper API support, so you can run plugins.
Performance comparison
| Metric | Vanilla | Paper |
|---|---|---|
| Chunk loading | Synchronous (causes lag spikes) | Asynchronous (smooth) |
| Hopper TPS cost (1000 hoppers) | ~3-4 ms/tick | ~0.5-1 ms/tick |
| Lighting engine speed | Baseline | 20-50x faster (Starlight) |
| Entity tick cost (500 mobs) | Full tick all | Activation ranges reduce cost 40-60% |
| Max stable players (4 GB RAM, same hardware) | ~15-20 | ~40-60 |
| Chunk generation speed | Baseline | 30-50% faster |
| Memory usage | Baseline | Slightly lower (optimized data structures) |
What Paper breaks
Paper intentionally changes some vanilla mechanics for performance or security. These are the most notable:
- TNT duplication: Disabled by default. Many vanilla players rely on TNT dupers for quarrying. Paper patches this exploit. You can re-enable it in paper-global.yml.
- Sand duplication: Also patched. Can be re-enabled via config.
- Zero-tick farms: Fixed. Crops that grew instantly on vanilla by exploiting block update order do not work on Paper.
- Exact entity behavior: Entity activation ranges mean mobs far from players behave slightly differently. This can affect certain technical farms.
- Redstone quasi-connectivity edge cases: Paper preserves quasi-connectivity, but some extreme timing-dependent circuits may behave differently due to async chunk loading.
When to use vanilla
- You are building a technical Minecraft world where exact vanilla parity matters (TNT duping, precise redstone timing, zero-tick farms).
- You are recording content where viewers expect vanilla behavior.
- You run a very small private server (2-5 friends) and do not need plugins.
- You are testing or developing for vanilla Minecraft specifically.
When to use Paper
- You run a public server with more than 10 players.
- You want to use plugins (economy, permissions, protection, etc.).
- You need anti-exploit protection against griefers.
- You want smooth chunk loading without lag spikes.
- You run any sort of minigame, SMP, or community server.
Configuration options in Paper
Paper exposes over 200 configuration options across paper-global.yml and paper-world-defaults.yml. Some of the most impactful settings include: max-auto-save-chunks-per-tick which controls how aggressively the server saves chunks (lower values reduce autosave lag spikes), entity-per-chunk-save-limit which prevents chunk files from bloating when too many entities accumulate in one area, and anti-xray.enabled which hides ore veins from x-ray texture packs by sending fake block data to clients. These settings let you fine-tune performance and security in ways that vanilla does not support at all.
Profiling and monitoring
Paper bundles Spark, a powerful profiling tool that generates flamegraphs showing exactly what is consuming your server's tick time. On vanilla, you have limited visibility into performance issues. With Paper and Spark, you can identify which plugin, which entity type, or which world region is causing lag and take targeted action. This alone is reason enough to use Paper on any server where performance matters. Run /spark profiler for a 30-second capture and share the generated link with anyone helping you troubleshoot.
Switching from vanilla to Paper
Drop the Paper jar into your server directory, copy your world folder (it is the same format), and start the server. Paper generates its config files on first boot. Your world data, player data, and advancements carry over with no conversion needed. The only thing to watch for is farms that rely on patched exploits. Review paper-global.yml after first boot and decide whether to re-enable TNT duplication or sand duplication based on your community's preferences. The Paper documentation site explains every option.
Fabric as a server alternative
Paper is the standard for plugin-based servers, but Fabric is an alternative if you want server-side mods instead of plugins. Fabric servers run mods like Lithium (optimization), Carpet (technical features), and server-side content mods. The trade-off is that Fabric does not have the Bukkit plugin API, so thousands of Bukkit/Spigot/Paper plugins are incompatible. Fabric servers are popular for modded survival (where you run the same mods client and server) and for technical Minecraft communities that want vanilla parity with lightweight performance patches. For most community servers that need economy, permissions, protection, and administration plugins, Paper is the right choice. For modded servers or technical vanilla servers, Fabric is worth considering.
World format and data migration
Both vanilla and Paper use the same Anvil world format. Your region files, entity data, POI (point-of-interest) data, and player data files are fully interchangeable between vanilla and Paper. This means you can copy a vanilla world into a Paper server directory (or vice versa) with no conversion tools. The only additions Paper makes are its own config files and a cache directory for optimized data. If you ever need to switch back to vanilla, simply delete Paper's configs and use the vanilla server jar with the same world folder.
Bottom line
Vanilla is the reference implementation. Paper is the production server. If you care about performance, security, and plugin support, Paper is the correct choice. If you care about exact vanilla mechanics and do not need plugins, stick with vanilla. Most server owners should run Paper.
Looking for hassle-free hosting? Astroworld Hosting runs NVMe SSDs, Pterodactyl panel, full DDoS protection.