
Minecraft server lag typically falls into three categories: low server Ticks Per Second (TPS), high network latency, or low client-side frame rates. This guide explains how to identify the bottleneck on your server and adjust configurations, software, and hardware to maintain a stable 20.0 TPS.
Before changing settings, you must identify what kind of lag you are experiencing. Players often group three different problems under the word "lag":
On software like Paper, Purpur, or Fabric with profiling mods, you can check server health using commands like /tps. If TPS drops below 20.0, your CPU cannot keep up with the current workload.
A common question among administrators is why a modded or plugin-heavy Minecraft server lags even when it has plenty of free RAM. Shared hosts typically sell plans sorted by memory size, leading many to believe more RAM automatically increases speed.
In reality, Minecraft server performance depends mostly on single-thread CPU speed. The main game loop—handling entities, hopper transfers, redstone, and terrain ticks—runs largely on a single processor core. RAM simply holds loaded chunks, active players, mods, and plugins in memory.
If you lack sufficient RAM, the server will crash with an out-of-memory error or freeze frequently while Java tries to free up space. However, once you have enough RAM to hold your server's data, adding more memory will not fix low TPS caused by a slow CPU core. Furthermore, allocating excessive RAM without proper garbage collection settings can cause noticeable lag spikes when Java pauses the server to clean up unused memory at once.
The fastest way to reduce CPU load and memory usage is to limit how much of the world the server ticks and sends to players. In Minecraft 26.3, the default server.properties file sets both view and simulation distances to 10:
view-distance=10
simulation-distance=10
max-players=20
pause-when-empty-seconds=60Because chunks load in a square grid around every player, a distance of 10 loads a large area of chunks per player. Lowering these default values drastically reduces the workload:
simulation-distance below the default of 10 reduces the area where mobs, crops, and redstone are actively processed, directly saving CPU cycles.view-distance below 10 reduces how many chunks the server must read from the disk and send over the network when players fly or sprint across the map.You can use the hosting.9minecraft.net server.properties generator to adjust these settings cleanly before uploading them to your host.
Running the default Vanilla server jar is rarely optimal for multiplayer performance. Switching to optimized server software provides immediate TPS improvements:
Matching the right Java version and startup flags is also critical. According to the Mojang manifest, required Java versions scale with game updates:
To prevent garbage collection lag spikes, configure your startup script with Aikar flags—a widely used set of G1GC JVM flags designed specifically for Paper servers. You can generate a proper startup command with Aikar flags and the correct Java version using the start script generator and Java version lookup tools on our site.
If you are running on a free Minecraft server, hardware resources are tightly restricted. Free hosts usually stop the server when nobody is online, place starts in a queue, or show ads to cover costs. They also share physical CPU resources across many users, meaning your TPS can drop when other servers spike in activity.
To reduce lag spikes on a free or budget plan:
max-players=20 and lower simulation-distance below 10.If you outgrow free hosting and need consistent CPU performance, you can compare paid plans across 57 hosts and 331 plans with prices on hosting.9minecraft.net. Based on current site data, 4 GB plans cost from $3.60 to $30.00 per month (with a median of $9.89), while 8 GB plans cost from $5.28 to $60.00 per month (with a median of $20.47). You can use our RAM calculator at /tools/ram-calculator/ and the plan finder to match your player count and modpack size to an appropriate host.
Check your server's TPS (Ticks Per Second). If TPS drops below 20.0, the CPU is struggling to process the game loop and all players will feel the delay simultaneously. If TPS is a steady 20.0 while players still experience delayed block breaking or rubber-banding, the issue is network latency or packet loss.
Minecraft server performance relies mostly on single-thread CPU speed rather than total RAM. While mods require extra RAM to load assets and data, the ongoing tick calculations for modded machines, entities, and world generation still bottleneck on a single CPU core. Adding more RAM than needed can also cause garbage collection freezes if you do not use proper JVM flags.
Aikar flags are a widely used set of G1GC JVM garbage collection startup arguments for Paper servers. They do not make the CPU faster, but they smooth out memory cleanup so Java does not pause the server for long moments, eliminating sudden memory-related TPS drops.
Lowering simulation-distance and view-distance below the default of 10 is the most effective configuration change. It immediately reduces the number of active chunks, entities, and block ticks the server must process around every connected player.