To reduce lag in Minecraft, first find out which kind of lag you have: FPS lag, server lag or network lag. They look similar (stuttering, blocks reappearing, mobs teleporting) but have completely different causes. Lowering your render distance won't fix an overloaded server, and a faster internet plan won't fix a GPU that can't keep up. Here's how to tell them apart and fix each one, on Java and Bedrock.
The three kinds of Minecraft lag
| Type | Symptoms | Where it comes from |
|---|---|---|
| FPS lag (client) | Choppy camera, low frame rate even in single-player | Your PC or device |
| Server lag (low TPS) | Blocks reappear after breaking, mobs freeze or teleport, crops and furnaces slow down, everyone affected | The server can't keep up with its 20 ticks per second |
| Network lag (ping) | Delayed hits, rubber-banding, other players jumping, only you affected | Your connection or the route to the server |
Quick tests:
- Lags in single-player too? It's FPS lag.
- Everyone on the server complains at once? It's server lag.
- Only you lag, and only online? It's your network or the route.
On Java Edition, press F3 to see FPS and chunk information, and hold Tab to see each player's connection bars. Minecraft servers run at 20 ticks per second (TPS): if the server's TPS drops below that, the whole world slows down.
Fix FPS lag (your PC)
Video settings
- Render distance: the biggest single setting. Try 8–12 chunks instead of 16–32.
- Simulation distance: how far around you the world is active. Lower it to 6–8.
- Graphics: Fast instead of Fancy or Fabulous.
- Clouds: Off or Fast. Particles: Minimal. Smooth lighting: Off or Minimum.
- Max framerate: set a cap your PC can hold steadily, and turn off V-Sync if it causes stutter.
Performance mods (Java)
- Sodium (with Fabric) rewrites the rendering engine and often doubles or triples FPS on the same hardware.
- OptiFine is the older alternative with many visual options; Sodium is usually faster.
- Lithium and similar mods optimise game logic, which also helps single-player worlds.
RAM and hardware
- Allocate the right amount of RAM in the launcher's installation settings: 2–4 GB for vanilla, 6–8 GB for big modpacks. Too much can cause stutter.
- Use the dedicated GPU on laptops: set Java (javaw.exe) or Minecraft to "High performance" in Windows graphics settings.
- Update graphics drivers and close heavy background apps.
- Bedrock: lower render distance and turn off fancy graphics and "beautiful skies" in video settings.
Fix server lag (if you run the server)
- Use an optimised server such as Paper instead of the vanilla server jar.
- Pre-generate the world with a chunk pre-generation plugin, so the server doesn't create new terrain while players explore.
- Lower view-distance and simulation-distance in
server.properties. - Limit entities and redstone: large mob farms, item piles and clocks are the classic TPS killers.
- Give the server enough CPU and RAM, and host it close to most players.
If you don't run the server, all you can do is report it, play at quieter times or choose another server. Server lag isn't caused by your connection.
Fix network lag (ping)
- Choose a server near you. Ping depends mostly on distance: a server on another continent will always add 100+ ms. For Realms, the region is chosen when the Realm is created.
- Play on Ethernet instead of Wi-Fi: Wi-Fi vs Ethernet for gaming.
- Stop other traffic on your network, and fix bufferbloat if ping jumps when others use the internet.
- Check for packet loss, which causes rubber-banding: how to fix packet loss.
- Improve the route to distant servers. If you play on a server in another region and ping stays high on a clean wired connection, a ping booster can shorten or stabilise the path. Check that it supports Minecraft and your server, and test with a free trial: current deals on the ExitLag promo code page, more options in ExitLag alternatives.
What counts as good ping for Minecraft: under 80 ms is comfortable, up to 150 ms is playable for building and survival, and PvP feels best under 50. More in what is a good ping.
Minecraft lag checklist
- Identify the type: single-player test, other players, F3 and Tab
- FPS: render and simulation distance down, graphics Fast, Sodium on Java
- RAM: 2–4 GB vanilla, 6–8 GB for modpacks
- Dedicated GPU and updated drivers
- Server: Paper, pre-generated world, fewer entities (if it's yours)
- Network: nearby server, Ethernet, no background downloads
Most Minecraft lag is FPS or server lag, not internet. Start with the quick tests above and you'll know where to spend your time. If you can't sign in or your Realm won't load, see Minecraft Realms down? For lag in other games, see how to fix lag in games.



