World Spawn: Where You Start and Why It Moved

How the game picks your spawn

Since 1.18 the game doesn't go looking for a nice biome anymore. It scores spots near the origin by the climate noise (land, not too hot, not too wild) and keeps the best one, then hunts for a grass block or similar surface close to it. Players then drop somewhere within the spawnRadius gamerule of that point, 10 blocks by default on Java. That's why two friends joining the same world for the first time rarely land on the same block.

Before 1.18 it was a different game. The old search looked for a spawn-friendly biome like plains, forest or taiga inside a box around 0, 0, and it almost never left that box. You can see the difference in the numbers below, and it's bigger than we expected.

So modern spawns hug the origin way more often, but the tail is long. In 1.16 the worst case was a corner of the search box. In 26.3 about one seed in twelve puts you more than 512 blocks out, and 11 of the 2,000 went past 1,000.

The weird ones: 0, 0 on the dot, and seed 541

773 of our 2,000 seeds spawned on the origin itself. That happens when the very first spot the game checks already scores well enough, so it never moves on. The text seed chunkscout is one of them: spawn at 0, 0 in a snowy taiga on 26.3. Same for 8675309123456789, which lands at 0, 0 in a sparse jungle. Seed 0 is close but not quite, at −32, 0 in a forest, and 123456789 sits at 64, −48, also forest.

Then there's seed 541. Its spawn is at −1,120, −520 in a savanna, 1,235 blocks from the origin, the farthest of the 2,000. If you type 541 into a speedrun seed list and wonder why the coordinates people post look huge, that's why. On 1.16 the same seed spawned you at 208, 224, about 300 blocks out, so old tutorials for it are useless now.

Version changes move spawns around a lot. chunkscout spawned at 80, −208 in a taiga on 1.16, and 0, 0 on everything from 1.18 to 26.3. If you're following an old seed video, set the version on the map to whatever the video used before you trust any coordinate.

What you spawn in

Out of the same 2,000 seeds on 26.3, the biome under the spawn block came out like this. Forest and plains are the classic starts, but one seed in twelve drops you in snow, and deserts and beaches show up more than you'd think.

Honestly, the spawn biome matters less than what's around it. A dark forest spawn is miserable for the first night, sure, but a village 300 blocks away fixes that. The spawn point finder shows the spawn biome on hover, and the village finder tells you how far the nearest bed and bread are.

Spawn chunks are gone in 26.3

This one catches people out. For years the area around spawn stayed loaded with nobody there, and that's where you built iron farms, mob sorters and redstone clocks. Here's how it changed on Java:

• Beta 1.3 to 1.13.2: chunks within 128 blocks of spawn stayed loaded, roughly 16×16 chunks, with entities only active in the inner 12×12 or so.
• 1.14 to 1.20.4: 19×19 chunks with entities and redstone running, 21×21 with block ticks, 23×23 loaded in total.
• 1.20.5 to 1.21.8: the spawnChunkRadius gamerule, default 2, which shrank the active part to 3×3 chunks. Set it to 0 to switch spawn chunks off, or up to 32 for more.
• 1.21.9 and newer, so 26.3: spawn chunks and the gamerule are gone. Nothing stays loaded around spawn on its own.

If your farm is in an old world that you've updated, it now only runs while someone is nearby. The fix on a world with cheats is /forceload add on the farm's chunks. On a server without cheats, park an AFK player there. Bedrock never had spawn chunks at all; use /tickingarea there.

The spawn chunk calculator has every one of those versions in its dropdown, so for an older world you can type the spawn and get the exact chunk and block ranges to build in.

Moving spawn, beds and Bedrock

The world spawn isn't sacred. /setworldspawn moves it to where you stand, and setting spawnRadius to 0 makes everyone appear on exactly that block, which is nice on a server with a proper spawn build. Beds and respawn anchors only change *your* respawn point, not the world spawn, and if your bed is broken you go back to world spawn.

On Bedrock the game picks its spawn its own way, and nobody has published how 1.18+ Bedrock does it. The finder shows the Java estimate for Bedrock seeds, which is often close but not guaranteed, so use it as a hint. Structure positions on Bedrock are a different story: those are exact, so the village and portal distances from your real spawn still hold.