Home › Guides › How to Host a Paper Server (Plugins + Performance Tuning) — 2026
How to Host a Paper Server (Plugins + Performance Tuning) — 2026
Paper is the performance fork of Spigot and the default choice for plugin servers — survival, SMPs, minigames, factions. It runs vanilla-compatible worlds far faster than the vanilla jar and gives you deep config knobs to tune away lag. Here's how to host and tune one properly.
How much RAM does a Paper server need?
Paper is efficient — it's built to squeeze more players onto the same hardware. Plugins, not the core, drive your memory needs: a lightweight survival server sips RAM, while a big economy/land-claim/minigame stack with a large loaded world needs more.
| Players | Recommended server RAM | Notes |
|---|---|---|
| 1–10 | 2–3 GB | Vanilla-style survival with a few plugins. |
| 10–30 | 4–6 GB | Typical SMP with an economy/claims plugin set. |
| 30–75 | 6–10 GB | Busy public server; tune view-distance + spawns. |
| 75+ | 10 GB+ | Large network; consider splitting worlds/proxies. |
Setup steps
- Pick a plan with 4 GB RAM as a solid default for a survival/SMP server.
- Choose 'Paper' from the installer — MineXEngine fetches the matching Paper build for your Minecraft version and selects the right Java.
- Set your view-distance and simulation-distance before first boot (see the tuning section — this is the single biggest lever).
- Drop your plugins into the plugins folder and restart (see below).
- Set difficulty, whitelist and spawn protection, then hand out the IP.
Installing plugins the right way
- Use plugins built for Paper/Spigot and your exact Minecraft version — a plugin for 1.20 may silently break on 1.21.
- Install one plugin at a time and restart, so a broken plugin is easy to trace in the log.
- Watch startup for 'incompatible' or 'unsupported version' warnings — an out-of-date plugin is the most common source of console errors.
- Keep essentials lean: a permissions plugin, an economy/claims plugin, and anti-grief cover most survival servers without bloating RAM.
Performance tuning that actually moves the needle
Paper's real advantage is its config files. A handful of settings do more for smoothness than any amount of extra RAM.
| Setting | Where | Recommendation |
|---|---|---|
| view-distance | server.properties | 6–8 for busy servers (10 is often overkill) |
| simulation-distance | server.properties | 4–6 — the biggest tick-cost lever |
| mob spawn limits | bukkit.yml | Lower monster/animal caps on crowded servers |
| merge-radius (items/xp) | paper-world.yml | Merge nearby drops to cut entity count |
| ticks-per mob-spawns | bukkit.yml | Raise slightly to spread spawn load |
MineXHost runs Paper servers on MineXEngine — our launcher auto-detects the modpack, picks the right Minecraft loader and Java version, tunes the JVM for your RAM, and auto-recovers from the crashes that normally end a modded server's evening. Pick your RAM, paste the pack, and play.
See hosting plansFrequently asked questions
How much RAM does a Paper server need?
A small survival/SMP server runs well on 2–4 GB; a busy public server with a full plugin stack wants 6–10 GB. Paper is memory-efficient, so don't over-allocate — an oversized heap causes longer GC pauses.
Why is my Paper server lagging with plenty of RAM?
Usually view-distance and simulation-distance are too high, or mob spawn limits are letting entities pile up. Drop simulation-distance to 5–6 and lower mob caps — that cuts per-tick load far more than adding RAM.
Can I use Bukkit and Spigot plugins on Paper?
Yes — Paper is a fork of Spigot (which forks Bukkit), so it runs Bukkit/Spigot/Paper plugins. Just match each plugin to your Minecraft version and install them one at a time so a bad one is easy to spot.
Does Paper support mods?
No — Paper runs plugins, not Forge/Fabric mods. If you want mods, host a Forge, NeoForge or Fabric server instead. Some hybrid servers (like Mohist) bridge both but trade away stability; plain Paper is the reliable plugin choice.