How to Reduce Minecraft Server Lag in 2026 – Complete Guide

Nothing kills a Minecraft community faster than a laggy server. Rubber-banding, delayed block placement, and TPS drops frustrate players and drive them away. In this guide I'll walk through every major cause of Minecraft server lag and give you practical, tested fixes for each.

Understanding TPS – The Key Metric

Before diagnosing lag, you need to understand TPS (ticks per second). Minecraft runs on a game loop that should tick exactly 20 times per second. Each tick processes mob AI, redstone, player movement, entity updates, and more. When the server can't complete a tick within 50ms, it falls behind and TPS drops below 20.

Check your TPS in-game with /tps (requires Paper/Spigot or the EssentialsX plugin). If you see consistent drops below 18, work through the fixes below.

Fix 1: Use Paper Instead of Vanilla/Spigot

This is the single highest-impact change you can make. Paper is a high-performance fork of Spigot that includes hundreds of optimizations not present in vanilla Minecraft — async chunk loading, improved entity handling, and optimized mob AI among them.

Switching from vanilla to Paper typically improves TPS by 2–5 points under the same load. All XyleHosting Minecraft plans support one-click Paper installation from the Pterodactyl panel — no manual file management required.

Fix 2: Optimize Your JVM Startup Flags

The Java garbage collector handles memory management. Poor GC settings cause freeze-frames ("lag spikes") every few seconds as Java pauses to clean up memory. Use Aikar's flags for dramatically smoother performance:

Replace 4G with your plan's allocated RAM (e.g. 8G for the 8 GB plan). Set both Xms and Xmx to the same value to prevent GC thrashing.

Fix 3: Pre-Generate Your World

When players explore new terrain, Minecraft generates fresh chunks on-the-fly — a CPU and disk-intensive operation. On busy servers this causes major TPS drops. Pre-generating a fixed world border eliminates this entirely.

Use the Chunky plugin for Paper (free on Hangar). A 5,000-block radius pre-generation takes 10–30 minutes and permanently removes new-chunk generation lag. After pre-generating, set a world border with /worldborder set 10000 to keep players within the pre-generated area.

Fix 4: Reduce Entity and Mob Counts

Entities (mobs, item drops, minecarts, arrows) are the single biggest TPS consumer in most servers. Each entity is processed every tick. Recommended limits in paper.yml:

• Set max-entity-collisions: 2 (default 8)
• Set mob-spawner-tick-rate: 2 (default 1)
• Enable merge-radius.item: 3.5 to merge dropped items
• In bukkit.yml, reduce spawn-limits monsters to 50 (from 70)

Also use the ClearLagg plugin to automatically remove excessive item drops every few minutes.

Fix 5: Audit Your Plugins

Poorly written plugins that execute code every tick are one of the most common causes of TPS drops on community servers. Use the Spark profiler plugin to identify exactly which plugins are consuming the most CPU time:

1. Install Spark from Hangar (free)
2. Run /spark profiler start during a lag spike
3. Stop after 60 seconds with /spark profiler stop
4. Review the report URL and identify the heaviest plugin calls
5. Disable or replace plugins consuming >10% of tick time

Fix 6: Upgrade Your Hardware

If you've optimized settings and plugins but still see TPS drops, your underlying hardware may be the bottleneck. The most impactful upgrade is moving to a higher single-core clock speed CPU. XyleHosting's AMD Ryzen 9 plans offer up to 5.1 GHz boost clock — the highest available in our lineup — directly translating to better TPS under load.

Similarly, if your current host uses SATA SSDs or HDDs, moving to a provider with NVMe storage eliminates chunk loading stalls. See our infrastructure page for full hardware specs.

Quick Fix Checklist

Frequently Asked Questions