Minecraft
Paper vs Purpur: choosing software for your Minecraft server
Compare Paper and Purpur by the features you need, then plan a safe test before switching a live world.
Choose Paper for a plugin server when you want a straightforward starting point. Consider Purpur when you have specific gameplay changes in mind and want to manage them through configuration. Start with the features your community needs, then test your plugin stack before switching a live world.
Both projects serve Minecraft Java Edition. Neither choice turns a Paper plugin server into a Forge or Fabric modpack server. If your players need client-side mods, check that requirement before comparing these two options.
The difference that matters
Paper provides a server platform for Bukkit, Spigot and Paper plugins. Purpur builds on Paper. The Purpur team describes its project as a configurable replacement for Paper with additional gameplay features in its official documentation.
That relationship makes Purpur worth considering when you want its extra settings. It does not prove that Purpur will run your particular server faster. Your plugins, settings, world and hardware affect the result, so a claim about one server cannot replace a test of yours.
| Decision | Paper | Purpur |
|---|---|---|
| You want a conventional plugin SMP | A sensible starting choice | Consider it if you need an additional feature |
| You want extra gameplay controls | Check Paper settings and compatible plugins | Check Purpur's configuration reference for the exact option |
| You need a particular plugin | Check its supported versions | Check those versions and the author's fork support |
| You want to solve lag | Profile the workload first | Profile before and after a controlled test |
Write down your reason for switching
List the behaviour you want to change in plain language. “We need players to use a particular mechanic in this world” gives you a testable requirement. “Purpur has more options” leaves you with work to do and no clear success check.
For each requirement, find the relevant setting in the documentation for your chosen build. Purpur keeps its additional options in purpur.yml; consult its configuration reference for the supported keys and their effects. Keep your edits in a change log so another administrator can understand them.
Ask your moderators about player expectations before changing survival mechanics. A setting that suits a private world may affect a public economy or a farm players spent weeks building. Tell players which behaviours you intend to change and when you will test them.
Check plugins and Java before you move
Make a list of plugins and their versions. Check each project's release page for the Minecraft version you intend to run, required dependencies and any warning about server forks. Follow our plugin installation guide when you need to add or update a component.
Match Java to the Minecraft release as well. Paper's current requirements table recommends Java 21 for Minecraft 1.20 through 1.21.11 and Java 25 for 26.1 onward. Recheck that table before a future upgrade instead of assuming one Java image suits every release.
Test a copy of the server
- Create a backup and confirm it completed. Keep a separate copy of important files.
- Record the current server build, Java version, startup settings and plugin versions.
- Ask support about a separate test instance or use an isolated copy. Give it a different address and restrict who can join.
- Start the copy on the intended build. Read the console for startup errors before inviting testers.
- Check joining, permissions, commands, inventories, dimensions and the gameplay feature you want.
- Restart the test copy, then check the same features again. Record failures and the relevant log lines.
Keep the test environment away from live economy databases, webhooks and other integrations unless you have arranged safe test credentials. A copied configuration can still point at a production service. Review those connections before starting the copy.
Make the live change reversible
Arrange a short maintenance window and take a fresh backup once players have stopped making changes. Follow the panel's software-change process or ask support to confirm it. A reinstall may erase files, so do not choose that action as a shortcut for changing the server JAR.
Keep the old build and configuration with the backup. If you also upgrade Minecraft, do not assume the newer world can run on an older version; read Paper's migration guidance and plan a full restore where needed. Check the first live session before calling the change complete.
You can compare CloudExa Minecraft hosting options before launch. If you already host with us, send support your current build, plugin list and the feature you want. That gives us a better basis for advice than choosing a fork by name alone.
Technical references checked on 8 November 2026. This comparison does not claim benchmark results for either project.
