Change Rust worldsize & seedControl map size and the procedural map

Published on August 4, 2026 · last updated on November 8, 2026

worldsize: the map size

server.worldsize determines the edge length of the map. Technically, values from about 1000 to 6000 are possible; in practice, 3000 to 4500 is usually what works:

• 3000 - compact, fast encounters, good for small groups and lower RAM requirements.
• 3500 - 4000 - a balanced standard for most community servers.
• 4500 - large, more monuments and space, higher RAM and performance requirements.

Larger maps need more RAM and CPU. Match the worldsize to your plan and the expected number of players.

seed: the specific map

server.seed is an integer from which Rust generates the map procedurally. The same combination of seed + worldsize always produces exactly the same map. Without a fixed seed, the server rolls a new map at every map wipe. If you set a fixed seed, you keep your favorite map across several wipes.

Set the values

Enter both values in the server.cfg or in the startup parameters:

server.worldsize 4000
server.seed 1337

As startup parameters, use a leading plus accordingly: +server.worldsize 4000 +server.seed 1337. A map wipe/restart is needed for the new map to load - ideally in line with your wipe cycle.

Preview on RustMaps.com

Before you take a map live, it is worth checking RustMaps.com: there you enter seed and worldsize and see the generated map including monuments, islands, rivers and resources. That way, you can specifically find a seed with a good monument distribution and balanced terrain - and transfer exactly these values to your server.cfg.

What to look for when choosing a map

Not every seed produces a good map. In the preview, it is worth looking at four things before you commit:

• Monument distribution. Are the large monuments spread across the map or crowded into one corner? A cluster means all the action takes place there and the rest of the map stays empty.
• Buildable space. Too many mountains look good, but leave little room for bases. Players who cannot find building space leave the server quickly.
• Road connections. A continuous road network makes vehicles usable and connects the monuments. Maps with broken roads feel fragmented.
• Islands and amount of water. A lot of water reduces the usable area considerably - a 4500 map can then feel like a 3500 one.

The combination of seed and worldsize produces exactly one map: if either value changes, a completely different world is created. So write down both when you like a map.

Think about size and player count together

The most common wrong decision for a new server is a map that is too large. It sounds generous, but it means ten players never run into each other in an evening - and a Rust server without encounters is not a Rust server.

As orientation: around 3000 to 3500 of map size per 50 expected players. For a group of 20 to 30 people, 3000 to 3500 is usually better than 4500. Better a dense, lively map than an empty one - and you can always readjust at the next wipe.

The second effect is server load: a larger map costs noticeably more performance, regardless of how many players are online. If you are struggling with performance, check the map size before tinkering with plugins - see Improve performance.

When the values take effect

Both values only take effect when a new world is generated. On a running server, you can enter them as often as you like - nothing happens as long as the existing map state is there. That is not a bug; it prevents an accidental typo from destroying everyone's world.

The right moment is therefore the map wipe, usually in line with the monthly force wipe. Enter the new values in the server.cfg, remove the old map state and restart.

Expect some waiting time: Rust generates the map on the first start and is not visible in any server list during that time. With large maps, that takes quite a few minutes - do not abort the process. Back up the identity folder via WebFTP or SFTP beforehand; with us, backups are self-service across the board, see Create backups.

Frequently asked questions