
Server world admin · Java · Intermediate
How to Pre-Generate a Server World and Verify Coverage in the Map Viewer
Generating new terrain on the fly is the single biggest cause of server lag in Minecraft Java Edition. By pre-generating chunks within a set world border before players join, you shift that heavy CPU workload to an idle setup period. After running the generation task, you can use our browser-based World Map Viewer to visually audit your region files and ensure there are no missing gaps in the terrain.
What you need
- A Minecraft Java Edition server or singleplayer world folder
- A pre-generation server plugin or mod, or a command block script
- Sufficient free disk space (typically 1 GB to 15 GB depending on your target radius)
- Access to the World Map Viewer on this site (runs locally in your browser without uploading files)
Step by step
1Back Up Your World and Calculate Your Radius
Before modifying world settings or generating thousands of new chunks, create a full backup copy of your world folder. Decide on your center coordinates (usually `0, 0`) and a target radius in blocks, noting that storage needs grow quadratically because doubling the radius quadruples the total area. As a baseline estimate, a 5,000-block radius (a 10,000x10,000 block square) creates roughly 400 region files and consumes around 1.5 GB to 3 GB of disk space depending on world height and biome complexity.
Tip: Always check the size of a single fully generated `.mca` file in your specific setup to calculate a more accurate storage estimate for your target area.
2Configure the Vanilla World Border
Start your server and set the center point using the command `/worldborder center 0 0`. Next, apply the boundary limit by running `/worldborder set <diameter>`, remembering that the vanilla command requires the full diameter (twice your radius). Setting this physical barrier ensures players cannot wander outside your pre-generated zone and trigger fresh chunk generation lag during normal gameplay.
Tip: Add a small buffer of 64 to 128 blocks to your pre-generation radius beyond the world border so players standing at the very edge still see fully rendered terrain.
3Run the Pre-Generation Task
Use your preferred server pre-generation plugin or mod to queue chunk creation out to your target radius, or align it directly to the vanilla world border. Do not fly around manually in creative mode to do this, as manual exploration inevitably leaves spiral gaps and consumes massive amounts of server memory. Allow the automated task to run until completion with no other players online, then run `/save-all` and gracefully `/stop` the server so all file buffers flush cleanly to disk.
4Load the World in the World Map Viewer
Open the World Map Viewer on our site and click Open world folder or .zip to select your server's local world directory (or a downloaded `.zip` archive of the `region` folder). Because the tool runs entirely inside your browser, even multi-gigabyte worlds load instantly without waiting for network uploads. Once opened, the tool reads the `level.dat` file and parses the `.mca` files inside the `region` folder (or `DIM-1/region` for the Nether and `DIM1/region` for the End).
5Inspect the Region Grid for Missing Gaps
Zoom out in the World Map Viewer until you can see the entire square or circular boundary of your generated terrain. Look closely for dark or empty voids inside the boundary, as well as partially rendered 16x16 chunk slivers along the perimeter. If you spot empty patches, note their block or chunk coordinates shown in the viewer so you can return to the server and re-run your pre-generator specifically across those missing coordinates.
Tip: Toggle the grid overlay in the viewer if you need to pinpoint the exact `r.x.z.mca` region file responsible for a corrupted or missing section.
How it works
Minecraft Java Edition stores terrain data using the Anvil format inside the `region` directory for the Overworld, `DIM-1/region` for the Nether, and `DIM1/region` for the End. Each region file is named `r.x.z.mca`, where `x` and `z` represent the region coordinates. A single `.mca` file holds a 32x32 grid of chunks (1,024 chunks total), which corresponds to a 512x512 block area in the game.
When Minecraft generates a chunk, it does not do it in a single pass. Instead, each chunk progresses through a pipeline of generation steps recorded in its NBT data under the `Status` tag—moving from `empty` to `structure_starts`, `biomes`, `noise`, `surface`, `features`, `light`, and finally `full`. If a pre-generation task is interrupted or misconfigured, chunks at the edges might remain in a partial status like `features` or `light` without reaching `full`.
Our World Map Viewer parses the 8-kilobyte header at the beginning of each `.mca` file to check which of the 1,024 chunk slots actually contain compressed NBT payloads. By reading the chunk `Status` tag and heightmap arrays directly in your browser's memory, the viewer renders an accurate top-down preview, allowing you to immediately distinguish fully generated terrain (`Status: full`) from ungenerated void space.
Common mistakes
- Confusing radius with diameter: Setting `/worldborder set 5000` creates a border 2,500 blocks in each direction from the center, whereas setting a pre-generator to a 5,000-block radius generates a 10,000x10,000 block square, wasting four times the required disk space.
- Forgetting other dimensions: Pre-generating only the Overworld (`region` folder) leaves the Nether (`DIM-1/region`) and the End (`DIM1/region`) ungenerated, causing severe lag spikes the moment players enter portals.
- Inspecting files while the server is still running: Minecraft caches active chunks in RAM and writes them to `.mca` files periodically; inspecting the world folder before running `/save-all` and stopping the server will show false gaps in the viewer.
- Running out of disk inodes or storage space mid-task: If the host drive fills up during pre-generation, the server will fail to write chunk payloads, leaving corrupted zero-byte `.mca` files and permanent holes in the map.
FAQ
Why are there fuzzy or ragged edges outside my exact radius in the viewer?
Minecraft requires surrounding neighbor chunks to be partially generated (for structure bounding boxes, biome blending, and lighting) before a target chunk can reach the `full` status. These border chunks are normal and take up very little space.
Can I delete excess region files outside my world border?
Yes, if you accidentally generated too far, you can identify the outer `r.x.z.mca` coordinates in the World Map Viewer and delete those specific files from your `region` folder while the server is stopped, remember to always make a backup first.
Does pre-generating a world prevent future game updates from adding new features?
Yes. Once a chunk is saved to disk with `Status: full`, future Minecraft versions will not overwrite it with new structures or biomes; you would need to expand the world border or trim unused chunks to see new update content.
By planning your disk budget, running an automated pre-generation task within a fixed world border, and verifying the resulting `.mca` grid in our browser-based World Map Viewer, you can guarantee a lag-free exploration experience for your server players.