What a Seed Really Is

A seed is a string of numbers that Minecraft uses as the “starting point” for its random number generation when building a vanilla world. When you create a new world, the game uses this seed to decide: terrain height, the distribution of ocean and land, caves and ore deposits, biomes (desert/snowy/jungle…), and where structures like villages, temples, and strongholds appear.

The key property is that it’s reproducible: as long as the seed is the same, the game version is the same, and the world type is the same, the generated map will be basically identical. That’s why “good seeds” get shared online—type that string of numbers into the world-creation screen and you’ll get the same patch of terrain someone else discovered.

This number is recorded in the world save’s level.dat (along with metadata like the name, game mode, and spawn point). To learn what else level.dat stores, see What the level.dat file is.

What a Seed Affects, and What It Doesn’t

  • Affects: vanilla “procedurally generated” terrain. The layout of mountains, coastlines, biomes, caves, and structures like villages/temples is all computed from the seed plus the generation algorithm.
  • Doesn’t affect: places you’ve already played. Once you’ve explored a chunk, it’s physically written into the save (in db/ on Bedrock, in region/.mca on Java Edition), and the seed’s job is done. Changing the seed value after the fact won’t redraw old chunks—it will only affect distant terrain generated later, and the old and new terrain tend to show an obvious seam at the boundary. To understand how chunks are stored and why the file grows as you explore more, see What a chunk is.

In other words: a seed is a one-time random starting point used “when the world is created,” not a switch you can flip to swap maps at any time. To get a completely different patch of vanilla terrain, the normal approach is to start a new world with a new seed.

Real-Map Worlds and Random Seeds Are Two Different Things

This is the easiest point to confuse. Turning a real place into a world with TopoBlocks doesn’t rely on a seed—it relies on real data. After you search for a real location, it reads OpenStreetMap’s public data (building outlines, roads, water) plus open elevation (terrain relief), then uses open-source tools to generate an importable .mcworld. So the urban fabric you see comes from the real world, not from some random number’s calculation.

Worlds like this do of course also have a level.dat and a seed field, but that string of numbers doesn’t decide what the streets and buildings in front of you look like. And precisely because it’s an approximate reconstruction based on public data, not a block-by-block copy of real buildings, how good it looks depends mainly on whether local data coverage is dense enough—so before generating, TopoBlocks gives the map a quality score for free and provides a low-resolution 3D preview, letting you see the coverage clearly before deciding whether to generate (the quality score is a data-coverage estimate, not an accuracy guarantee). To learn more about “how accurate and how true-to-life the result is,” see How accurate are real-map worlds, and for a deeper walkthrough see Real-map-to-world tutorial.