How to Fix Minecraft Server Lag: A Step-by-Step Guide for 2026

Nothing kills a Minecraft community faster than lag. Players blame the server, the admin blames the host, and the real cause is often a five-minute settings change nobody knew to make. This guide shows you exactly how to fix Minecraft server lag in 2026 — whether you're running vanilla, Paper, or a heavy modpack.

Before you spend money on more RAM, you need to know which lag you have. Minecraft lag falls into three buckets: TPS lag (server can't keep up), network lag (high ping), and chunk lag (world loading freezes). Each has a different fix. We'll cover all three, then show you the hosting-level changes that prevent lag from coming back.

Step 1: Diagnose the type of lag

Open your server console or join as an op and run one command:

/tps

On Paper, this returns a number like 20.0, 19.2, or 15.0. Anything below 19.0 means TPS lag — the server is dropping ticks. If TPS is fine but players are rubber-banding, it's network lag. If everyone freezes when exploring new terrain, it's chunk lag.

Still unsure? Use the Spark plugin. Run /spark profiler --timeout 60 and it will tell you exactly which plugin, entity, or chunk is eating your tick time.

Step 2: Fix TPS lag with server settings

TPS lag is the most common problem on small-to-medium servers. It means the server is trying to process more than the CPU can handle in 50 milliseconds per tick. Here are the fixes that work, ranked by impact.

Lower view-distance and simulation-distance

Open server.properties and change these two values:

view-distance=8
simulation-distance=6

View distance controls how many chunks are sent to each player. Simulation distance controls how many of those chunks are actually ticked. Dropping from the default 10 to 8 typically cuts CPU and RAM use by 30–50% with no visible gameplay change. This is the single biggest performance win on most servers.

Pre-generate your world

New chunk generation is one of the worst TPS spikes. Install the Chunky plugin, then run:

/chunky radius 3000
/chunky start

Let it finish in the background. Your players will no longer cause lag spikes just by walking in a straight line.

Limit entities and mob farms

Add these values to spigot.yml or paper-world.yml:

entity-activation-range:
  animals: 16
  monsters: 24
  raiders: 48
  misc: 8
mob-spawn-range: 4

Large animal farms and mob grinders are silent TPS killers. These settings stop distant entities from burning CPU cycles while keeping combat normal.

Audit plugins with Spark

Bad plugins are a bigger cause of lag than most admins expect. Run a 60-second Spark profiler, look at the top tick consumers, and ask: do you really need that plugin? Common offenders include poorly written anti-cheats, old permissions plugins, and map renderers running on the main thread.

Step 3: Fix network lag and high ping

If your TPS is 20 but players still rubber-band, the problem is not your server — it's the network path between them and the machine.

• Choose the right region. UK players on a US server will see 100–150 ms ping no matter how good the hardware is. Use UK hosting for UK players, US hosting for US players. If you have both, consider a proxy network.
• Use wired connections. Players on Wi-Fi or mobile hotspots will always have worse ping. You can't fix this server-side, but you can tell your community.
• Check for DDoS attacks. If ping spikes during peak hours, your server may be under attack. A host with game-aware DDoS filtering, like SurfNode's 800 Gbps shield, stops this at the edge before it reaches your server.

For UK communities, SurfNode's UK Minecraft hosting is based in London with sub-15 ms latency to most of the country. For US players, cheap US Minecraft server hosting starts at $2.69/mo.

Step 4: Fix chunk lag and world loading freezes

Chunk lag feels like short freezes when players explore, fall through invisible blocks, or see terrain pop in late. It is almost always caused by slow storage or ungenerated chunks.

• Use NVMe storage. A standard SATA SSD is 4× slower for random reads, and a hard drive is 50× slower. Minecraft is random-read heavy. If your host is not on NVMe Gen4, chunk lag is guaranteed.
• Pre-generate again. We already said it, but it solves both TPS and chunk lag. Do it.
• Reduce world border. A 30,000-block border is enormous and mostly empty. Most communities work fine with 5,000–10,000 blocks.
• Throttle map renderers. Dynmap and BlueMap are great, but their render queues can thrash disk I/O. Lower their update frequency or pause rendering during peak hours.

Step 5: Right-size your RAM

Under-allocated RAM causes long garbage-collection pauses, which feel like sudden freezes. Over-allocated RAM can also cause longer pauses because Java's garbage collector has too much heap to scan.

Our Minecraft RAM sizing guide has the full breakdown. The quick version:

• Vanilla / Paper, 2–10 players: 2–4 GB
• Paper with plugins, 10–30 players: 4–6 GB
• Modded packs (ATM10, Better MC, RLCraft): 8–12 GB
• Heavy custom packs: 12–16 GB

Step 6: Tune the JVM

If your host does not apply Aikar's flags automatically, you are leaving 10–20% of performance on the table. These flags tune the G1GC garbage collector for Minecraft's memory pattern and are considered the standard across the Paper, Purpur, and Pufferfish communities.

On SurfNode, Aikar's flags are applied by default on every Minecraft server. If you're self-hosting, copy the official flags from Paper's docs and paste them into your startup script.

The hosting layer matters more than tweaks

Settings can only fix lag caused by bad settings. If your server is on a slow CPU, shared SATA storage, or an oversold node, no amount of config will save it. The three hardware factors that matter most are:

• CPU single-thread performance. Minecraft is mostly single-threaded. Look for high-clock AMD Ryzen or Intel Xeon cores.
• NVMe Gen4 storage. This directly impacts chunk load times and TPS during exploration.
• Game-aware DDoS protection. UDP game attacks cause lag even when they don't knock you offline.

Quick-fix checklist

If you need results in the next ten minutes, do this in order:

1. Run /tps to confirm TPS lag.
2. Set view-distance=8 and simulation-distance=6.
3. Install Spark and run a 60-second profiler.
4. Install Chunky and pre-generate a 3,000-block radius.
5. Check that your server has at least the recommended RAM for your player count and server type.
6. Move to a UK or US host with NVMe Gen4 and DDoS protection if the hardware is the bottleneck.

Still stuck? Read our advanced tuning guide how to reduce Minecraft server lag for profiler-driven fixes, or choose the right amount of RAM for your setup.

Ready to stop lag for good? Start a UK Minecraft server from £1.99/mo or get US Minecraft hosting from $2.69/mo with instant setup, Pterodactyl control panel, and NVMe Gen4 storage.