Minecraft Bedrock Server Lag Fix: Stop Lag and Rubber Banding

To fix Minecraft Bedrock server lag, lower view-distance to 10 to 16 and keep tick-distance at 4 in server.properties, clear piles of dropped items and mobs, update the server to the same version as players, and check heavy add-ons. Rubber banding is usually network lag or too many entities near a farm, not a lack of RAM.

Is it server lag, connection lag or low FPS?

Bedrock lag comes in three kinds, and each has a different fix. Figure out which you have first.

If only one player is affected, it is almost never the server. Ask them to try a wired connection or move closer to their router, and to close downloads and streams. If everyone lags at the same moment, read on.

Lower view-distance in server.properties

view-distance is how many chunks the server sends to each player. Its default of 32 is very high for a server, and every extra chunk costs memory and bandwidth for every player online. This is the single biggest Bedrock lag fix.

view-distance=12
tick-distance=4

Players whose own render distance is lower still see less. Restart the server after changing it.

Keep tick-distance at 4

tick-distance (range 4 to 12) is how many chunks around each player are simulated: mobs move, crops grow, redstone runs. The area grows as a square, so raising it from 4 to 8 means about four times the simulated chunks. Leave it at 4. If a farm really needs more, try 6 and watch whether the lag comes back.

Also leave client-side-chunk-generation-enabled=true, which lets players' devices draw distant scenery themselves and takes that load off the server. Every key is explained in Bedrock server.properties explained.

Clear dropped items and too many mobs

Entities are the most common cause of sudden lag on a Bedrock world that used to run fine. Item piles from broken farms, hundreds of animals in a pen and mob farms without a kill system all add up.

From the server console, or in game as an operator with cheats on:

kill @e[type=item]
kill @e[type=xp_orb]
kill @e[type=arrow]

These remove dropped items, XP orbs and stuck arrows across loaded chunks. Do not run kill @e on its own, it removes every entity including pets, villagers and players.

Then fix the source:

• Animal pens: keep breeding pens under 30 to 40 animals each.
• Mob farms: make sure they kill mobs quickly and collect drops into hoppers and chests.
• Item farms: check hopper chains are not full, which leaves items lying on the ground.
• Villager halls: large numbers of villagers in one place are expensive. Split them up.

Check game rules that add work

A few game rules raise server load if someone changed them:

Check a rule with gamerule randomtickspeed. Set it back with gamerule randomtickspeed 1.

Fix rubber banding on a Bedrock server

Rubber banding means the server corrected your position. On Bedrock that happens when the server is lagging, the player's connection is unstable, or strict movement checks are on.

1. Check if it happens to everyone. If yes, it is server lag: work through the sections above.
2. If it is one player, it is their connection.
3. Check server-authoritative-movement-strict in server.properties. When true, players with higher ping get pulled back more. Set it to false on a private server.
4. Leave player-position-acceptance-threshold at its default unless you know why you are changing it.

Add-ons and scripts can lag the server

Behavior packs with scripts, custom entities or big structures can cost more than the whole vanilla game. If lag started after you added an add-on:

1. Remove it from the world's world_behavior_packs.json (back up first) and restart.
2. If the lag stops, check for an updated version of the pack.
3. Look in the console for repeated script errors. A script that throws an error every tick can lag a server on its own.

After 26.50, add-on entity files are validated more strictly, so an old pack may also spam errors after an update. See how to add add-ons to a Bedrock server.

Do I need more RAM?

Only if memory is actually full. Bedrock Dedicated Server is native code and light: 2 GB holds a group of up to 10 on a normal survival world. You need more when the world is large and heavily explored, you run heavy add-ons, or you have 25 or more players. If lag is the same with 2 players as with 10, RAM is not the cause. Settings and entities are.

Update the server after Minecraft updates

An old server can cause odd behaviour, and players on a newer version cannot join at all. After every Minecraft update, update the server so it matches. The current release is covered in our Bedrock 26.50 server update.

Bedrock lag on GamezServers

1. Change view-distance and tick-distance in the Files tab in server.properties, then restart.
2. Use the Console for the kill @e[type=item] style commands.
3. Click Update game after Minecraft updates. Your world is backed up first.
4. If the world has outgrown its plan, upgrade from the dashboard. 4 GB suits 10 to 25 players with a busy world, 6 GB suits large explored worlds and up to 50.

Plans and crossplay details are on Minecraft Bedrock server hosting.

FAQ

Why is my Minecraft Bedrock server so laggy?

Usually a high view-distance, too many entities near farms, or a heavy add-on. Lower view-distance to around 12, keep tick-distance at 4 and clear dropped items.

What is the best view distance for a Bedrock server?

10 to 12 on a 2 GB server and 12 to 16 on 4 GB and up. The default of 32 is too high for most servers.

How do I clear lag on a Bedrock server with commands?

Run kill @e[type=item] and kill @e[type=xp_orb] from the console to remove dropped items and XP orbs. Never run kill @e without a type.

Why do I rubber band on a Bedrock server?

Either the server is lagging, your connection is unstable, or server-authoritative-movement-strict is on. If only you rubber band, it is your connection.

Does more RAM fix Bedrock server lag?

Only when memory is full, which is rare for a friend group on 2 GB. Settings, entities and add-ons cause most Bedrock lag.