How does Purpur differ from Paper and other Minecraft server software?
Updated
Purpur is Minecraft server software built on top of Paper. It keeps Paper's performance and plugin compatibility, then adds a large set of configuration options and gameplay features on top. If you already run Paper and want more control without changing your plugin stack, Purpur is a drop-in-style alternative; if you want the smallest possible surface area or you rely on a different server platform's ecosystem, staying where you are may make more sense.
The relationship: Purpur sits on top of Paper
PurpurMC describes Purpur as "minecraft server software based on Paper." That single line explains most of the practical differences:
- Inherited from Paper: performance work, bug fixes, and the plugin API behavior that Paper provides.
- Added by Purpur: extra configurability and "fun and exciting gameplay features" that Paper does not ship by default.
Because Purpur is downstream of Paper, it generally tracks Paper's releases rather than defining its own separate plugin ecosystem.
Plugin compatibility
Purpur states that it "supports plugins designed for bukkit, spigot and paper APIs."
In practice this means:
| Plugin built for | Works on Purpur? |
|---|---|
| Bukkit API | Yes, per Purpur's stated support |
| Spigot API | Yes, per Purpur's stated support |
| Paper API | Yes, per Purpur's stated support |
So moving from Paper to Purpur does not require rewriting or replacing plugins that target those APIs. That is the main reason Purpur is often described as a low-friction switch rather than a migration.
What Purpur adds: configurability first
Purpur's stated focus is "providing as much configurability as possible, to allow server owners to customise their server to their liking."
That is the core philosophical difference from Paper. Paper aims to be a performant, broadly compatible base. Purpur takes that base and exposes more knobs and gameplay toggles so a server owner can tune behavior without writing custom code or stacking extra plugins for every small change.
If your priority is "run Paper and change as little as possible," Paper is the simpler choice. If your priority is "run Paper but tune many behaviors from config," Purpur is aimed at you.
The wider PurpurMC ecosystem
PurpurMC is described as "an open source organization that focuses on the development of Purpur," and it also develops other software around the Minecraft modding/plugin ecosystem. Two projects are listed alongside Purpur itself:
PurpurExtras
A plugin for Purpur and Paper servers. It offers "additional features that were deemed easier to implement and maintain as a separate plugin." Notably, it runs on Paper too, not only Purpur — so it is not a reason by itself to switch server software.
PurpurPacks
A set of datapacks that "add additional features to your minecraft world." These are world-level additions rather than server-software changes.
How to decide
- Choose Purpur if: you want Paper's performance and Bukkit/Spigot/Paper plugin compatibility, plus more configuration options and built-in gameplay features.
- Stay on Paper if: you prefer a leaner base and do not need the extra configurability.
- Consider PurpurExtras separately if: you want those extra features but are not ready to change your server jar — it supports Paper as well.
- Consider PurpurPacks if: what you actually want is world content via datapacks, which is independent of the server software choice.
Getting it and verifying
PurpurMC provides Download, Read the docs, and See source code links for Purpur, PurpurExtras, and PurpurPacks. Before switching a live server, the reliable sequence is: read the docs for the version you intend to run, confirm your plugins target Bukkit/Spigot/Paper APIs, and test on a copy of your world before replacing the production jar.
The site also notes that development is "driven by free time and passion," with support options via OpenCollective and GitHub Sponsors — relevant if you want to help keep the API and build servers online.