Skip to content
Guide

How to Fix Minecraft Server Lag

Minecraft server lag means low TPS — the "Can't keep up!" warning, blocks breaking slowly, mobs stuttering. The fix is switching to Paper/Purpur, tuning view and simulation distance, capping entities and mob spawns, applying Aikar's flags, profiling with spark, and pre-generating the world. Here's how to get back to a solid 20 TPS.

9 min read Intermediate Anti-DDoS hosting

TPS (ticks per second) is Minecraft's heartbeat — 20 is healthy. When the server can't finish a tick in 50 ms you get the "Can't keep up!" warning and everything feels sluggish. The usual causes are too many loaded chunks, entity and mob-farm overload, an unoptimised server type, or a weak CPU. Work through them and TPS recovers.

Below is the fix, from biggest win to hardware. For settings context see our best settings to reduce lag; if the CPU is the wall, our Minecraft hosting runs fast dedicated cores.

Before you start

What you'll need

A quick checklist before you begin — have these ready and the rest is easy.

  • Access to server.properties and the server type (Paper/Purpur).
  • The spark plugin to profile tick time.
  • A pre-generation plugin (Chunky) for the world.
  • Aikar's flags and sensible -Xmx/-Xms values.
  • A fast high-clock CPU (Minecraft is single-thread bound).
Step by step

Fix Minecraft server lag, step by step

1

Switch to Paper (or Purpur)

The single biggest win. Paper (and Purpur on top of it) add extensive performance patches vanilla and Spigot lack — chunk loading, entity limits, mob-spawn control. Switching to Paper alone often fixes most lag on a vanilla/Spigot server. Your world and plugins carry over.

2

Lower view & simulation distance

View distance is how far chunks render; simulation distance is how far the server actually ticks entities and blocks — the heavier of the two. Drop simulation-distance to 4-6 and view-distance to 6-8. This is often the fastest single fix.

# server.properties
view-distance=8
simulation-distance=5
3

Cap entities & mob farms

Item stacks, mobs and giant mob/XP farms are heavy. In Paper's config, cap entities per chunk, tune mob-spawn ranges, and merge dropped items. A single unoptimised mob farm can drag a whole server's TPS down.

4

Apply Aikar's flags & right-size RAM

Aikar's flags are a tuned G1GC set that smooths out garbage-collection pauses on servers with 4 GB+. Apply them and set sensible -Xmx/-Xms — but don't over-allocate RAM, which can make GC pauses worse.

java -Xms4G -Xmx4G  -jar paper.jar nogui
5

Profile with spark

Install the spark plugin and run /spark profiler during lag. It shows exactly which plugin, mob or task is eating tick time — so you fix the real cause instead of guessing.

/spark profiler --timeout 60
6

Pre-generate the world

Generating new chunks as players explore is a big lag source. Use a pre-generation plugin (Chunky) to build the world out to your border in advance, so exploration doesn't hitch the server.

/chunky radius 5000
/chunky start
7

Give it a fast CPU

Minecraft is single-thread bound, so TPS lives on one core's speed. If the server is optimised and TPS still dips, the CPU is the wall — a fast high-clock dedicated core is the fix, not more RAM.

Hold 20 TPS

Biggest wins first

Paper is the #1 fix

Switching from vanilla/Spigot to Paper (or Purpur) adds performance patches that fix most lag on their own. Do this first — your world and plugins carry over.

Simulation distance is the heavy one

It's not render distance that hurts most — it's simulation-distance, which ticks entities and blocks. Drop it to 4-6 for a fast TPS gain.

spark finds the real cause

Don't guess. /spark profiler shows exactly which plugin, mob or task eats tick time, so you fix the actual bottleneck.

TPS lives on one core

Minecraft is single-thread bound. When it's optimised and TPS still dips, a fast high-clock core — not more RAM — is what restores it.

Troubleshooting

Common problems & fixes

Hit a snag? These are the issues people run into most — and how to solve them.

TPS drops when players explore new areas

Chunk generation is the cause. Pre-generate the world with Chunky out to your border so exploration doesn't generate chunks live.

TPS tanks near a specific base or farm

An unoptimised mob/XP farm or entity pile-up. Profile with /spark, cap entities per chunk in Paper's config, and tune the farm.

Still laggy after switching to Paper

Lower simulation-distance, apply Aikar's flags, and run /spark to find the offending plugin or task. If clean, the CPU is the wall.

Optimised everything and TPS still dips

Single-core speed is the limit. Move to a host with a fast high-clock dedicated core.

Skip the setup — host it with ESAGAMES

Optimised the server but TPS still dips under load? Our Minecraft hosting runs fast high-clock dedicated cores on NVMe with DDoS protection and one-click Paper/modpacks — the hardware side of a solid 20 TPS.

Minecraft hosting
FAQ

Frequently asked questions

Why is my Minecraft server lagging?

Lag means low TPS — the server can't finish a tick in 50 ms. The usual causes are running vanilla/Spigot instead of Paper, too-high view/simulation distance, entity and mob-farm overload, or a slow CPU. Switch to Paper, lower simulation distance, profile with spark, and check the hardware.

How do I fix "Can't keep up! Is the server overloaded?"

That warning means TPS dropped below 20. Switch to Paper/Purpur, lower simulation-distance (to 4-6) and view-distance, cap entities and mob farms, apply Aikar's flags, and profile with /spark to find the specific cause. If it persists on a clean setup, the CPU is the bottleneck.

Does Paper reduce Minecraft server lag?

A lot — it's usually the single biggest fix. Paper (and Purpur on top) add extensive performance patches vanilla and Spigot don't have: chunk loading, entity limits, mob-spawn control. Switching to Paper alone often resolves most lag, and your world and plugins carry over.

What is TPS and what's a good value?

TPS is ticks per second — the server's heartbeat. 20 is healthy (each tick fits in 50 ms). When TPS drops below 20 you get the "Can't keep up" warning and everything feels sluggish. The goal of every lag fix is holding a solid 20 TPS.

Should I lower view distance or simulation distance to fix lag?

Simulation distance first — it controls how far the server actually ticks entities and blocks, which is the heavier of the two. Drop simulation-distance to 4-6 and view-distance to 6-8. Simulation distance usually gives the bigger TPS gain.

Does more RAM fix Minecraft server lag?

Usually not — Minecraft is CPU-bound, so low TPS with spare RAM means the single core is the bottleneck. Over-allocating RAM can even make GC pauses worse. Optimise (Paper, distances, spark), then move to a faster high-clock core.

More guides

Keep reading

Ready to launch?

Protected, low-latency game hosting in Frankfurt — online in minutes with 24/7 support.

Payments Secure checkout with cards, banking apps and digital wallets.

Choose the payment flow that fits your stack and region without leaving the platform.

Pay by Zen Visa Mastercard Paysafecard PaysafeCash Skrill Trustly Bancontact UnionPay iDeal WebMoney