Paper vs Purpur: Which Is Better? Performance, Plugins and 26.3

Paper vs Purpur in short: Purpur is Paper plus one extra configuration file, purpur.yml, with hundreds of gameplay options; it runs the same Paper, Spigot and Bukkit plugins, and with default settings it performs like Paper. Pick Paper for vanilla-style gameplay and the fastest updates after a new Minecraft release; pick Purpur if you want to change mechanics such as ridable mobs, bigger barrels or anvil rules without extra plugins. Paper and Purpur are the two most popular server jars for plugin-based Minecraft servers in 2026, but they are not really competitors: Purpur is built on top of Paper and follows it a little later after every Minecraft update.

Want your own Minecraft server? At HostValues from €2.80 per month, online within minutes. View plans →

Paper vs Purpur at a glance

What Paper is in 2026

Paper is the high-performance server that most plugin servers run, directly or through a fork. It rewrites large parts of the server for speed and fixes many vanilla bugs and exploits. In December 2024 Paper hard forked from Spigot: from 1.21.4 on, it no longer follows Spigot's changes. Existing Spigot plugins keep working, but plugins that rely on Spigot API added after the fork may not.

Since 1.21 Paper also bundles the spark profiler, so /spark profiler start works out of the box when you hunt for lag. Paper has the largest community and the most complete documentation, and it is usually first with a new Minecraft version. For 26.3, released by Mojang on 15 September 2026, the first Paper build appeared a few hours later.

What Purpur adds

Purpur describes itself as "a drop-in replacement for Paper servers designed for configurability, and new fun and exciting gameplay features". All extras live in purpur.yml: global options under settings, and per-world options under world-settings, where default applies to every world without its own section. A few popular examples:

• Ridable mobs: set ridable: true for a mob under mobs and players can ride and steer it with WASD.
• Bigger storage: barrels with up to 6 rows (barrel.rows) and six-row ender chests (ender_chest.six-rows), optionally per permission.
• Silk touch spawners: silk-touch.enabled under gameplay mechanics, combined with the purpur.drop.spawners and purpur.place.spawners permissions.
• Anvil rules: allow incompatible enchantments together or levels above the maximum, such as Efficiency VI.
• Mob behaviour: creepers and endermen that do not grief (allow-griefing: false), villagers that follow players holding emerald blocks, per-mob health and other attributes.
• AFK handling: instead of kicking idle players, show an [AFK] tag in the tab list and broadcast when someone goes AFK.
• Extra commands: /ping, /uptime, /tpsbar, /compass and /purpur reload to reload purpur.yml without a restart.

The important part: according to Purpur's own FAQ, none of these changes take effect unless you enable them. If you do not edit purpur.yml, running Purpur is no different from running Paper.

Paper vs Purpur performance

Purpur inherits all of Paper's optimisations by design, and with an untouched purpur.yml it runs the same code paths as Paper. With the same world, plugins and settings you should not expect a meaningful TPS difference. Features you switch on, such as ridable mobs or extra mob logic, naturally do their own work, but that is a choice you make per option.

What really decides performance is the same on both: view and simulation distance, entity counts, redstone and farms, plugins, and the Paper settings in paper-world-defaults.yml. Use spark to find the cause of lag before blaming the jar.

Plugin compatibility

• Paper plugins on Purpur: they work. Purpur's FAQ says the only incompatibilities come from plugins that hard-code support for CraftBukkit or Spigot and ignore Paper and its forks.
• Purpur plugins on Paper: not always. Purpur has its own API on top of Paper's, and a plugin that uses it only runs on Purpur. Such plugins are rare and list Purpur as a requirement.
• Old Spigot plugins: the same story on both, because both follow Paper's hard fork.

Purpur 26.3 and Paper 26.3: support status

Mojang released 26.3 on 15 September 2026. Paper published its first 26.3 build (alpha) the same day, moved 26.3 to the beta channel on 28 September and released its first stable 26.3 build (175) on 11 October 2026. Purpur's first 26.3 build (2634) followed on 16 September; as of 7 October 2026, all its 26.3 builds, up to build 2644 from 6 October, are marked experimental, while purpurmc.org still lists 26.2 as the current version.

That pattern is normal. For 26.2 (released 16 June), Paper went stable on 26 July, and Purpur dropped the experimental label on 13 July. Purpur typically has a first build within a day or two of Paper, but both need a few weeks before their builds count as production-ready. Both need Java 25 for 26.x.

Paper 26.3 has been stable since 11 October 2026: for a busy server on Paper, check your key plugins for 26.3 builds first and make a backup (Java 25). On Purpur, wait for stable builds and for your key plugins to support 26.3. For a small server with friends, a beta or experimental build is usually fine, as long as you make a backup first.

When Paper is the better choice

• You want the fastest and most conservative update path after every Minecraft release.
• You play vanilla-style and have no use for extra gameplay tweaks.
• You want the biggest pool of documentation and support answers.
• You would rather solve the few things you want to change with a plugin you can remove at any time.

When Purpur is the better choice

• You want to change vanilla mechanics (mobs, storage, anvils, spawners, AFK) without stacking extra plugins.
• You build a community or survival-plus server with its own identity.
• You already run Paper and want more options without changing plugins or worlds.
• A plugin you want requires the Purpur API.

How to switch between Paper and Purpur

1. Make a full backup of the server, including worlds and config files.
2. Stop the server and replace the jar with the Purpur (or Paper) build for exactly the same Minecraft version.
3. Start the server. On first start Purpur creates purpur.yml; your worlds, plugins and Paper configs stay as they are.
4. Change the options you want in purpur.yml and restart, or use /purpur reload.

Going back from Purpur to Paper works the same way: Paper simply ignores purpur.yml, and Purpur-only features stop working. One catch: vanilla barrels and ender chests have three rows, so empty any extra rows first, or those items can be lost. Plugins that need the Purpur API will no longer load.

On HostValues Minecraft hosting (from €2.80 per month) you switch between Paper and Purpur with the version switcher in the game panel, and you can set the right Java version as described in set the Java version. Create a backup in the panel before you switch.

Frequently asked questions

Is Purpur better than Paper?

Not better, but more configurable. Purpur is Paper plus purpur.yml. If you want to change gameplay mechanics, Purpur saves you plugins; if you do not, Paper is the simpler choice with slightly faster updates.

Will my plugins break if I switch from Paper to Purpur?

No. Purpur is a drop-in replacement for Paper, so Paper, Spigot and Bukkit plugins keep working. You replace the jar, restart, and purpur.yml is added next to your existing configs.

Does Purpur support Minecraft 26.3?

Yes, but only with experimental builds so far (since 16 September 2026; the latest is build 2644 from 6 October, as of 7 October 2026). Paper 26.3 has been stable since 11 October 2026. For production servers on Paper, check your key plugins for 26.3 builds first and make a backup (Java 25); on Purpur, 26.2 is still the safe choice until stable 26.3 builds arrive.

Is Purpur slower than Paper?

No. With an unchanged purpur.yml, Purpur behaves exactly like Paper and inherits all its optimisations. Only features you enable yourself add their own work.

Can I switch back from Purpur to Paper?

Yes. Stop the server, put the Paper jar for the same Minecraft version back and start again. Empty any extra barrel or ender chest rows first, because vanilla only has three, and remove plugins that require the Purpur API.

Should I use Paper or Purpur?

Use Paper if you want vanilla-style gameplay, the biggest pool of documentation and the fastest updates after a new Minecraft release. Use Purpur if you want to change mechanics such as ridable mobs, bigger barrels, spawners or anvil rules through purpur.yml instead of extra plugins. You can switch later by swapping the jar for the same Minecraft version.

What is the difference between Purpur and Paper?

Purpur is built on top of Paper: it contains Paper's code and optimisations and adds purpur.yml with hundreds of gameplay options, its own plugin API and extra commands such as /ping, /uptime and /tpsbar. Until you change purpur.yml, a Purpur server behaves like a Paper server.