If Minecraft server lagging only for me, the first check is whether the slowdown is your computer or the server. Open F3: if FPS is low but TPS is 20, it is client-side; if TPS drops, the server is struggling. This guide gives quick tests, targeted fixes, and when to look at /help/slow-server.
Is it your computer or the server? (FPS vs TPS)
Two numbers tell most of the story. FPS is frames per second on your screen. TPS is how many game logic ticks the server processes per second; a healthy server holds 20. When TPS falls below 20, every player on the server usually feels the same block-breaking delay and rubber-banding. If you are the only person complaining, TPS is often fine and the problem is on your side.
That said, server-side problems can single out one player. Your connection might take a poor route to Frankfurt, where our servers run. Or you might be standing in a chunk with an over-active redstone contraption while your friends are elsewhere. The tests below separate all of these.
Quick tests: F3, ping, and server timings
Run these before changing anything.
- Press F3 (or Fn+F3 on some laptops) in Minecraft. Look at the upper-left overlay. Find your FPS and, if your server runs Paper or Spigot, the tick rate (TPS) line. If FPS is low and TPS is 20, the lag is client-side.
- Open a terminal or command prompt and ping your server's IP or domain (the address shown in your panel). Look at the time column. Latency under about 50 ms feels responsive; above 100 ms can cause noticeable delay. Ping measures your route, not the server's tick rate.
- On AtrbCode, open the Server doctor card in your panel. It reads the server's log and crash report and lists what it found in plain words, with a button to fix common problems such as turning a broken plugin off. If something is wrong server-side, this is the fastest way to see it.
- If your server runs Paper or a fork with timings, run
/timings reportand read the report. Our panel also includes performance tools such as spark and Chunky. Use them alongside the timings report to investigate further.
Client-side fixes: RAM, render distance, drivers
When F3 shows low FPS but TPS stays at 20, fix your own client first. The table shows the most common client issues and what to change.
| Symptom | Likely cause | Fix |
|---|---|---|
| Low FPS near lots of mobs or redstone | CPU or GPU load | Lower render distance, reduce graphics settings, close background apps |
| FPS drops after playing for a while | Minecraft running out of allocated memory | Increase RAM in your launcher (4-6 GB is usually plenty; do not give it all your system RAM) |
| Stuttering or screen freezes | Outdated graphics drivers or power settings | Update your GPU driver and set your laptop to High Performance |
| High block lag or rubber-banding with good FPS | High or unstable network latency | Switch from Wi-Fi to Ethernet, restart your router, or ask your ISP about the route |
Work through these one at a time, not all at once, so you know which one helps.
Allocate RAM properly and lower render distance
In the official launcher, find the installation settings and raise the -Xmx value. For most players, 4-6 GB is a good range. Giving Minecraft 16 GB can make things worse because garbage collection pauses get longer. Then in-game, lower render distance from 16 chunks to 10 or 8 and turn particles to minimal. FPS usually jumps.
Check drivers and power
Old GPU drivers are a common cause of sudden FPS drops, especially after a Minecraft update. Update your graphics driver from the maker's site. On laptops, Windows may be on power saver; set it to high performance while plugged in.
Server-side fixes: find the TPS drop with timings, remove laggy plugins
If F3 shows TPS dropping below 20 while FPS on your client is fine, the server is the problem. Other players might not notice because they are not in the same area, or they tolerate the lag. Start with these steps.
- Open the Server doctor card in your AtrbCode panel. It reads the log and crash report and lists findings such as a broken plugin or an overloaded world. Use the fix button to turn off the problem plugin.
- If you are on Paper, run
/timings on, wait a minute, then/timings report. The link it gives you shows what the server spent time on. Look for a chimney of red. - Remove or replace the laggy plugin. Our plugin store has one-click installs from Modrinth, Hangar, and Spigot, so you can try a lighter alternative without uploading files by hand.
- If your world has too many entities in a small area, consider using the performance tools available in the panel (such as Chunky) to help reduce the load when players move around.
The full walkthrough is in our guide /help/slow-server. It covers the same checks in order and tells you what to do before changing anything.
When a plan upgrade actually helps
More RAM fixes lag only when the server is consistently out of memory. You can check this by reading the server log via the Server doctor; if it lists out-of-memory messages or frequent memory pressure, a plan with more RAM may help. But if the timings report shows a single plugin consuming most of the tick time, adding RAM will not help. Find and fix that plugin first.
Our Minecraft plans run from 512 MB RAM with 5 GB SSD storage up to 16384 MB RAM with 120 GB SSD storage. All Minecraft plans have unlimited player slots; the plan's RAM is the practical limit. So a small group with a few plugins is fine on less, but a modpack or many plugins can need more. Use the plan range to match your actual usage. Compare our plans at /minecraft.
FAQ
Why am I the only one lagging on a Minecraft server?
Usually because the lag is on your side: low FPS from your computer, high latency on your network route, or a render distance that is too high for your hardware. Server TPS can also be the cause if you are in a heavy chunk, but then you can confirm it with the timings report or Server doctor.
How do I check if lag is from my computer or the server?
Press F3 and look at FPS and TPS. Low FPS with TPS at 20 means your computer is the bottleneck. Low TPS means the server is struggling. Ping the server and check the Server doctor in the AtrbCode panel to be sure.
Can high ping cause lag for only one player?
Yes. Ping measures the network path from your device to the server. If your ISP routes you through a congested exchange or you are on Wi-Fi, you can have high latency while another player on the same server does not.
What should I do if the server TPS is fine but I still lag?
Work through client-side fixes first: lower render distance, allocate 4-6 GB RAM in the launcher, update drivers, and use Ethernet instead of Wi-Fi. If the problem continues, try a different network or ask your ISP about packet loss on the route.
When should I upgrade my Minecraft server plan?
Upgrade when the server's log or timings report shows it is consistently out of memory and TPS drops align with memory pressure. More RAM helps with more players, larger worlds, and heavier modpacks, but it does not fix inefficient plugins.
Start with the step-by-step checks in /help/slow-server. Our Server doctor and performance tools show what is actually happening server-side, and if you need more headroom, compare the full range at /minecraft. For a deeper look at general lag causes, read /blog/13/minecraft-server-lag-causes-fixes-and-prevention.
