Quick answer: The fastest way to reduce Minecraft server lag is to lower view-distance and simulation-distance in server.properties (both default to 10), switch to Paper for its optimizations, and keep entity and chunk counts under control. Here’s the full checklist.
Server lag (low TPS — ticks per second) shows up as delayed block breaking, rubber-banding, and mobs freezing. It’s almost always caused by the server doing too much work per tick, not your internet. Work through these fixes in order. Many of these live in server settings you can edit directly.
1. Lower View Distance and Simulation Distance
These two server.properties settings are the biggest lever you have:
view-distance(default 10) — how many chunks of world data the server sends each player, as a radius. Dropping it to 6–8 dramatically cuts the server’s load with little visual loss.simulation-distance(default 10) — how far from players entities and blocks are actively updated (ticked). Lowering it to 4–6 is often the single biggest TPS win, because it shrinks how much the server has to simulate.
You can set both quickly with our free Server Properties generator.
2. Use Paper (or Purpur)
If you’re on vanilla or CraftBukkit/Spigot, switching to Paper is the highest-impact single change you can make. Paper rewrites huge parts of the server for performance and adds deep tuning in paper-world.yml (mob spawn limits, entity activation ranges, and more). Purpur (a Paper fork) adds even more toggles. Paper still runs all your Bukkit/Spigot plugins.
3. Control Entities and Mobs
- Cap mob farms and animals. Huge stacks of mobs, item frames, armor stands, and hoppers are common TPS killers. Reduce mob-farm sizes and use hopper minecarts sparingly.
- Lower
entity-broadcast-range-percentage(default 100). It controls how far entities are sent to players; reducing it eases the load when there are many entities. - Tune spawn limits in Paper’s config to cap how many monsters/animals load per player.
4. Give It Enough (But Not Too Much) RAM
An under-fed server lags and crashes; an over-fed one can stutter from long garbage-collection pauses. Match RAM to your player count and plugins/mods — see how to allocate RAM. Just as important is the quality of the hardware: a server on fast, high-clock-speed CPU cores will hold TPS far better than one on slow shared hardware, because Minecraft’s main loop is largely single-threaded.
5. Audit Plugins and Chunks
- Remove or replace heavy plugins. Run a timings/spark report (Paper’s
/timingsor the spark plugin) to see exactly what’s eating tick time, then cut the worst offenders. - Pre-generate and trim your world. Constantly generating new chunks is expensive; pre-generating the play area and trimming unused chunks reduces spikes.
- Watch always-loaded chunks from spawn chunks and chunk-loaders — they tick constantly.
If you’ve tried all of this and still lag, the hardware may simply be the ceiling — a Minecraft server hosting plan on fast dedicated cores removes that bottleneck.
FAQ
What causes Minecraft server lag?
Low TPS from the server doing too much per tick — usually high view/simulation distance, too many entities, heavy plugins, or slow CPU hardware. It’s rarely your internet connection.
Does lowering view distance really help?
Yes — view-distance and especially simulation-distance are the biggest, easiest TPS wins. Dropping simulation distance to 4–6 often fixes the worst lag instantly.
Will more RAM fix low TPS?
Only if you were starved for memory. TPS lag is usually CPU/workload-bound, so switching to Paper and lowering simulation distance helps more than adding RAM.
Ready to play?
Run your own Minecraft server with XGamingServer
Spin up an always-on Minecraft server your friends can join in minutes — no port-forwarding, no tech headaches.
