server.worldsize (Rust server ConVar)
What server.worldsize does in Rust, the 1000 to 6000 range, why changing it means a new map, and where to set it so it survives restarts.
Last updated Verified on Rust build 25582902, 2026-09-28
- Kind
- Variable
- Value on build 25582902
4000- Server help text
- (Generated) Width and height of the procedurally generated world in metres; larger values create a bigger map with more resources
- Applies
- On a new map (wipe)
- Persists in
- server.cfg
- Vanilla Rust
- Yes, native
- Example
server.worldsize 4000
Gotchas
- Only used when a procedural map is generated. The map and save files are named after it (proceduralmap.4000.<seed>.<version>.sav), so a new value means a new map, which is a wipe.
- Ignored while server.levelurl points at a custom map file.
- Not written to serverauto.cfg by server.writecfg, so keep it in server.cfg.
server.worldsize sets the width and height of a procedurally generated Rust map, in metres. The server's own help text, which Facepunch marks as generated: "Width and height of the procedurally generated world in metres; larger values create a bigger map with more resources". Facepunch's server guide gives the usable range as 1000 to 6000.
When the size is used
Only when the server generates a procedural map. On start, the log shows a line like this one from our test server:
Generating procedural map of size 4000 with seed 1420068679
The map, save and navmesh files in server/<identity>/ are named after the size and the seed, for example proceduralmap.4000.1420068679.289.sav. So a server started with a new size looks for a save under a new name, does not find one and builds a fresh map. Changing server.worldsize is a wipe, even if you meant it as a small tweak. Old files for the previous map stay in the folder until something deletes them.
The size is read when the map is built during startup, so set it before the server starts, not on a running server.
If you set server.levelurl in your config, the server's help text says it fetches and loads that map file instead of generating one, so the size is not used. Do not read too much into a non-empty server.levelurl on a running server, though: with server.autouploadmap on (it was True on our test server), Rust uploads its procedural map to Facepunch after startup, and on our server server.levelurl then showed a files.facepunch.com address that we never set.
Where to set it
Put it in server.cfg next to server.seed:
server.worldsize 4000
server.seed 1420068679
It also works as a startup argument (+server.worldsize 4000), but Facepunch's guide says server.cfg is read at startup and takes priority over the command line, so keep it in one place. server.writecfg does not save it: on our test server serverauto.cfg had no server.worldsize line.
Choosing a size
Facepunch's guide notes that a larger map needs more disk space and memory, and its requirements list 12 GB of free RAM, adding that a 6k map will use more. If the server is on a small box and gets killed while starting, the map size is one of the first things to look at.
In Panelra
World size lives under Settings, World, next to the seed and the custom map URL. The dashboard marks all three as wipe settings, used from the next wipe, manual or scheduled. Panelra writes the size to server.cfg for you.
Set it in Panelra
Change server.worldsize from the dashboard instead of editing files over SSH.
Frequently asked questions
Can I change server.worldsize without wiping?
What range does server.worldsize accept?
Related ConVars
- server.seed(Generated) Seed value used for procedural world generation; changing this produces a completely different map layout
- server.level(Generated) Map level to load on startup, e.g. 'Procedural Map', 'Barren', or a custom map name
- server.levelurl(Generated) URL to download a custom map file from; if set the server will fetch and load this map instead of generating one
Skip the manual work: install the Panelra agent
Wipes, updates, restarts, plugins and crash alerts for your Rust servers, from one dashboard. One install command on your Linux host, no inbound ports for the agent.
Free during the open beta. Pricing will be announced before the beta ends.