Minecraft servers
A Minecraft server lag troubleshooting checklist
Separate network, client and server lag, then test entities, chunks, plugins, CPU and memory in a useful order.
By AppLaunch Editorial · Reviewed 2026-08-25
Direct answer
First classify the symptom: rubber-banding for everyone suggests server tick or network trouble, one player may have a route/client issue, and low client FPS is not server TPS. Capture evidence during the event before restarting and erasing the useful state.
What this means in plain English
“Lag” can mean several different problems. If one player has trouble while everybody else is fine, their device or internet route may be the cause. If everyone sees blocks return after breaking or creatures freeze, the server may be falling behind. Low frames per second on one computer is a graphics problem, not server TPS.
Start by writing down who was affected, where they were and what was happening. Do this before restarting if the server is still safe to inspect. A restart may make the problem disappear for a while, but it can also remove the clues that explain it.
Where should diagnosis start?
| Scope | One player, one area or everyone |
|---|---|
| Server | Game-update time, memory and a performance recording |
| Network | Delay, lost data and the route from affected players |
A simple example
Players report lag every time three people fly into new land. Tick time rises during those trips but memory stays comfortable. That points toward world generation work. If only one player reports delay and the server numbers stay normal, check that player’s connection before changing the server.
What to do, step by step
1. Record time, player locations and activity.
Start here before buying anything or changing several settings at once. It gives you a clear starting point based on scope: one player, one area or everyone. Write the result down so you can compare it later.
2. Check game-update speed and memory at that time.
Use the same files, versions and settings that the real project will use. A quick test with an empty or different setup can look successful while completely missing the problem you are trying to solve.
3. Use a performance recording to find the slow work.
Try the busiest realistic situation, not the easiest one. Include the people, data, traffic or background work you genuinely expect, then watch for slowdowns and errors rather than relying on a single headline number.
4. Change one cause and repeat the same test.
Finish by checking the result against network: delay, lost data and the route from affected players. Keep the old setting or release available until you know the change works and can be reversed safely.
One more useful tip
Change one thing at a time. If you remove plugins, lower distances and add RAM together, you may improve the server but still have no idea which change mattered or which setting can safely be restored.
Common mistakes and how to avoid them
Installing “lag-fix” plugins blindly.
This gives a misleading or unsafe result because it leaves out scope. A better approach is to record time, player locations and activity, then check the result before making the change permanent.
Deleting entities without evidence.
This gives a misleading or unsafe result because it leaves out server. A better approach is to check game-update speed and memory at that time, then check the result before making the change permanent.
Confusing low FPS with server performance.
This gives a misleading or unsafe result because it leaves out network. A better approach is to use a performance recording to find the slow work, then check the result before making the change permanent.
Words explained
- CPU
- The part of the computer that does the calculations. Minecraft needs the CPU to finish each game update quickly so players do not feel delay.
- plugin
- An add-on for server software such as Paper. Plugins can add commands and features without usually requiring every player to install them.
- TPS
- Ticks per second. Minecraft aims for 20 game updates each second. A lower number means the server is falling behind.
- chunk
- A 16-by-16 block section of a Minecraft world. The server loads and processes many chunks around each player.
Quick checklist
- Record time, player locations and activity.
- Check game-update speed and memory at that time.
- Use a performance recording to find the slow work.
- Change one cause and repeat the same test.
Common questions
What is the simple answer?
First classify the symptom: rubber-banding for everyone suggests server tick or network trouble, one player may have a route/client issue, and low client FPS is not server TPS. Capture evidence during the event before restarting and erasing the useful state.
What should I check first?
Start with scope: one player, one area or everyone. That is usually more useful than choosing from a marketing label or copying somebody else’s setting.
How can I make the change safely?
Record time, player locations and activity. Then change one thing at a time, keep a backup or old version, and use the same real-world test after each change.
What is the easiest mistake to avoid?
Installing “lag-fix” plugins blindly. Avoiding that one mistake makes the rest of the comparison much more trustworthy.