World width, length and seed can only be set before a world is generated. The official wiki is clear that the world settings in serverconfig.json only take effect before a world is created, so changing them later does nothing to the world you already have. If you want a genuinely different size, you need to generate a fresh world, which means your current one is gone unless you back it up first. Still choosing where to run that new world? See our best Vintage Story server hosting comparison.
Also: never edit serverconfig.json while the server is running. The official wiki says the server must be stopped before you edit the file, and changes made while it’s live can be lost. Always stop the server first.
Setting a new map size
data/Saves folder now — regenerating a world with a new size deletes it. If you’re bringing this world elsewhere instead of resizing it, see our guide to uploading an existing world to a server instead — you don’t need to resize anything for that.serverconfig.json, and edits made while it runs can be lost.WorldConfig section, WorldConfiguration is null by default. Replace it with an object that holds both values in blocks (the seed is a separate Seed entry in WorldConfig, not part of WorldConfiguration):“Seed”: null,
…
“WorldConfiguration”: {
“worldWidth”: “100000”,
“worldLength”: “100000”
},
…
}
serverconfig.json also has separate top-level MapSizeX and MapSizeZ entries (default 1,024,000 each), and some host panels show map size under those names. If you edit the file by hand, set worldWidth/worldLength as above and give MapSizeX/MapSizeZ the same values so the two never disagree. Leave Seed as null for a random world, or set your own value to pick a seed. The wiki notes a seed does not guarantee exactly the same world every time..vcdbs file out of data/Saves (or point SaveFileLocation at a new file name) and start the server. When the file it points to doesn’t exist, the server creates a fresh world there using your new size./worldconfig worldWidth [number] and /worldconfig worldLength [number] commands, which the wiki lists as available only during the world create stage, rather than editing the file directly.Smaller than the default, almost always
The default 1,024,000 × 1,024,000 blocks is enormous — designed to never realistically be fully explored. For a normal group, a smaller world isn’t a compromise, it’s usually the better choice. Terrain is only generated where players actually go, so the size limit doesn’t change day-to-day RAM use, but it caps how far people can spread out and how much terrain, and save file, can ever pile up. Day-to-day load comes from the chunks loaded around players, which is covered in our server settings guide — a smaller world and a sensible MaxChunkRadius work together, not separately.
One thing to check if you shrink the world a lot: climate bands are set by polarEquatorDistance, the distance from pole to equator (100,000 blocks in the Standard preset). On a 25,000-block world players only ever see a narrow slice of climates, so lower polarEquatorDistance too if you want hot and cold regions on a small map. Like the world size, it can only be set before the world is created.
| Group size | Suggested world size | Why |
|---|---|---|
| 2–4 players | 25,000 × 25,000 | Plenty of room for a small group |
| 5–10 players | 50,000 × 50,000 | Space to spread bases out comfortably |
| Larger community | 100,000 × 100,000 | Still a small fraction of the default, but genuinely vast in practice |
| Default (not recommended) | 1,024,000 × 1,024,000 | Far more than almost any server will use |