How to Reduce Lag on a Minecraft Server
Work out whether lag is the server, the network or the player's computer, and fix the common causes.
"Lag" can mean three different problems. Work out which one first.
| What players see | Likely cause |
|---|---|
| Blocks reappear, mobs freeze, everyone rubber-bands | The server is overloaded (low TPS) |
| Only one player rubber-bands or has high ping | That player's connection |
| Low FPS, stuttering, even in singleplayer | The player's computer |
Check the server
Run spark health in Console (install spark from Package Manager first if it says the command doesn't exist). TPS should be 20 and MSPT under 50. Also check the CPU and memory graphs on Console.
If the server is the problem, run a profile to find the cause: see How to Find Lag With spark.
Common fixes
- Lower
simulation-distanceinserver.propertiesto 6–8. This is the biggest single win. - Lower
view-distanceto 8–10. - Pre-generate the world so exploring doesn't generate chunks live: see How to Pre-Generate a World.
- Run Paper for plugin servers, or add performance mods on Fabric: Lithium, FerriteCore, C2ME.
- Cut entity counts: huge mob farms, item piles and hopper chains are common culprits.
- Restart regularly with a schedule.
Memory
If Console shows memory near your plan's limit, or the log shows OutOfMemoryError, the server needs more RAM or fewer mods. You can change plan from Service & billing.
Still lagging? Open a ticket with a spark profile link.
More in Minecraft
Still stuck?
Ask the community on Discord, or open a ticket and we'll reply within 4 hours on business days.