Tune Paper and Spigot configs to cut lag
Change the Paper, Spigot and Bukkit settings that affect performance, with each default and what you give up by changing it.
Paper ships with sensible defaults, and a handful of settings in its config files are worth changing when a busy server drops below 20 TPS. This guide covers the ones with a documented effect on performance, what each default is and what you trade away by changing it. Spigot is not a server type here, but Paper reads spigot.yml and bukkit.yml as well as its own files.
Checked against Paper 26.3 (build 211) and PaperMC's configuration reference, October 2026.
Before you change anything
- Measure first. Run
spark profiler start --timeout 120in the Console while the lag is happening. Paper bundles spark, so there is nothing to install. Reduce lag with plugins shows how to read the report, and you can also watch the TPS reading in the left rail. - Create a backup in the Backups tab.
- Open the files in the File Manager, edit one value at a time and restart the server from the Console afterwards. Edit bukkit.yml, spigot.yml and Paper config gives the file locations and the safe way to save.
Paper's own troubleshooting page says to revert values you copied from a pre-made optimisation guide if you see strange farm, redstone or spawning behaviour. Change a few settings, measure, and keep the ones that helped.
Start with the distances
The Config Editor has View distance (chunks) and Simulation distance (chunks), both 10 by default. The editor's own note calls view distance the biggest lever on RAM and CPU, and simulation distance the cheaper one to cut. You can also set view-distance and simulation-distance under world-settings.default in spigot.yml, where default means "use the value from server.properties".
spigot.yml
These sit under world-settings.default.
Lowering entity-activation-range can save a lot, but Paper's reference warns that items in water streams may rubber-band when misc is low. Reduce entity lag on a Paper server covers the entity settings in more detail.
config/paper-world-defaults.yml
When config/paper-world-defaults.yml already exists, our installer sets optimize-explosions to true on Paper, Purpur and Folia, so a reinstall resets that line. Do not raise tick-rates.container-update above 1. Paper warns that higher values can cause item desync and visual lag.
bukkit.yml
spawn-limits holds the global mob caps, such as monsters: 70, animals: 10 and water-animals: 5. ticks-per.autosave is 6000. Paper lets a world override the limits in entities.spawning.spawn-limits in the world config, where -1 means "use bukkit.yml".
Check the result
Restart, repeat the spark profile under the same load and compare the TPS card. If a change made no difference, put the old value back so you are not carrying settings that do nothing.
Paper deprecates /reload for removal, and /paper reload is unsupported and does not reload spigot.yml. Restart after every edit.
Was this guide helpful?
Related guides
Reduce entity lag on a Paper server
Find which entities are piling up with paper entity list, then limit mob caps, activation ranges and dropped items on Paper.
Minecraft TPS and the types of lag explained
What TPS and MSPT mean, how server, network and client lag differ, how to read the Ticks per second card and which commands show TPS.
Reduce Minecraft lag with spark and plugins
Measure lag with spark, then use Chunky and ClearLaggEnhanced from the Plugins tab, with the console commands and settings this guide covers.
