How to Set Up World Borders on Your Minecraft Server

Leaving a Minecraft server without a world border is asking for trouble. Players explore outward forever, the world file balloons to dozens of gigabytes, chunk generation hammers the CPU, and eventually the TPS starts dropping during peak hours. A well-placed border keeps performance predictable, disk usage sane, and the gameplay experience tight for everyone. This guide walks through both the vanilla approach and the WorldBorder plugin, then covers pre-generation so your border actually works smoothly from day one.

Why world borders matter

Every new chunk a player loads has to be generated on the fly. Terrain shaping, structure placement, biome blending, cave carving, it all hits the main thread. On a busy server, two or three players exploring in different directions can tank the tick rate from 20 TPS down to 12 in minutes. A border eliminates runaway exploration and guarantees that every chunk inside the boundary can be pre-generated before anyone logs in.

Disk space is the quieter problem. A 50,000-block radius world in 1.21 can easily exceed 30 GB. Backups slow down, panel file managers time out, and migration between hosts becomes a headache. Keeping the radius sensible avoids all of that.

Recommended border sizes by server type

Server type	Recommended radius	Approximate area	Notes
Survival (SMP)	10,000 – 15,000	~314 – 707 km²	Plenty of biomes and structures
Large survival	20,000 – 30,000	~1,257 – 2,827 km²	Only with pre-gen and good hardware
Factions / PvP	3,000 – 5,000	~28 – 78 km²	Forces conflict, keeps raiding viable
Towny / Nations	10,000 – 20,000	~314 – 1,257 km²	Room for towns without endless sprawl
Skyblock / OneBlock	N/A	N/A	Void worlds, border is irrelevant

These numbers describe diameter, not radius. A "10,000 border" means the playable area spans 10,000 blocks from edge to edge, so the radius from center is 5,000.

Vanilla /worldborder command

Minecraft ships with a built-in border system that works without any plugins. It renders a translucent wall at the edge and pushes players back if they try to cross. Every command below runs from the server console or with operator permission.

Setting the center

/worldborder center 0 0

This pins the border center to coordinates 0, 0. If your spawn is somewhere else, use those coordinates instead. The center does not have to match the world spawn point, but keeping them aligned is the most intuitive layout.

Setting the size

/worldborder set 10000

This sets the total diameter to 10,000 blocks. The border instantly snaps to that size. You can also shrink or expand over time:

/worldborder set 10000 300

This transitions the border to 10,000 blocks wide over 300 seconds. Players see the wall moving inward or outward in real time, useful for events or a gradually shrinking UHC match.

Adding or removing distance

/worldborder add 2000 60

Adds 2,000 blocks to the current diameter over 60 seconds. Use a negative number to shrink.

Warning settings

/worldborder warning distance 50
/worldborder warning time 15

Warning distance tints the screen red when the player is within 50 blocks of the edge. Warning time does the same thing when the border is actively shrinking and will reach the player within 15 seconds. Both are visual cues that help players avoid getting crushed.

Damage settings

/worldborder damage amount 0.2
/worldborder damage buffer 5

If a player somehow clips past the border, they take 0.2 hearts per block per second beyond a 5-block buffer zone. The defaults are fine for most servers, but increasing the damage discourages glitch exploiters.

WorldBorder plugin (per-world control)

The vanilla command only affects the world the player is standing in. If you run Multiverse with separate worlds for resource gathering, events, or creative plots, you need the WorldBorder plugin (by Brettflan) to manage each world independently.

Install by dropping WorldBorder.jar into your plugins/ folder and restarting the server. The core commands:

/wb set 10000 spawn        # sets border in current world, centered on spawn
/wb world_nether set 5000  # sets border for the Nether specifically
/wb <world> fill           # pre-generates chunks inside the border
/wb <world> trim           # deletes chunks outside the border

The fill command is powerful but CPU-heavy. Run it during off-peak hours or before the server goes public. The trim command reclaims disk space by removing chunks players ventured into before you added the border.

Pre-generating with Chunky

Even with a border in place, the first player to explore each chunk still triggers generation lag. The solution is Chunky, a modern pre-generation plugin that works on Paper and Fabric. Install it, then:

/chunky center 0 0
/chunky radius 5000
/chunky start

Chunky generates chunks at a controlled pace, printing progress in the console. A 5,000-radius world typically takes 20–60 minutes depending on hardware. Once it finishes, every chunk inside the border is already saved to disk, and exploration lag disappears.

For servers that care about TPS during pre-generation, Chunky lets you throttle the rate. If you already have a border set via the WorldBorder plugin, Chunky can read it directly with /chunky worldborder.

After pre-generating, consider pairing this with a solid server optimization setup to keep tick times stable even under heavy player load.

Border per dimension with Multiverse

When using Multiverse-Core, each dimension is treated as a separate world. The Nether and End may need smaller borders or no border at all. A common setup:

• Overworld, 10,000 diameter, centered at 0,0
• Nether, 1,250 diameter (Nether distances are 1:8, so this matches the Overworld border)
• End, 5,000 diameter, centered at 0,0 (covers the main island and inner ring of outer islands)

Match the Nether border to the Overworld border divided by eight. Otherwise players can build a portal outside the Overworld border by walking far in the Nether.

Common mistakes

• Forgetting the Nether ratio, setting both worlds to 10,000 lets players bypass the Overworld border through Nether portals at 80,000 blocks out.
• Not pre-generating, the border stops exploration but does nothing for the chunks already inside. Pre-gen fills them all in advance.
• Center mismatch, centering the border at 0,0 when spawn is at 3000, 1500 gives lopsided exploration range.
• Setting the border too small on launch, expanding later is easy, but players get frustrated if they feel cramped from day one. Start with at least 10,000 for survival.

Need reliable hosting for your server? Astroworld Hosting offers NVMe SSD, Pterodactyl panel, and DDoS protection. See features , plans from €6.39/mo.