server.worldsize is the map edge in meters. Facepunch's creating a server wiki accepts 1000 through 6000 and notes that a larger world spends more RAM and disk. A friends server fits 2500 to 3000. Public communities often choose 3500 to 4250, while high-pop clan servers have room to spread out at 4500 or more.
Pick a size by pop and use
| Use | World size | Players who fit | What you get |
|---|---|---|---|
| Friends / solo-duo | 2500-3000 | 10-40 | Short walks, constant contact, compact monument set |
| Weekly community | 3000-3500 | 40-80 | Fast gear-up, dense roads |
| Monthly vanilla | 3500-4250 | 50-120 | Facepunch-style density, ring road on 4000+ |
| Modded PvP with teleports | 3000-4000 | 80-150 | Size follows how often people hop |
| Roleplay / PvE building | 4000-4500 | 40-100 | Room for compounds and towns |
| High-pop clans | 4500-6000 | 150-200+ | Long travel, more land per group |
Facepunch's wiki example command uses +server.worldsize 4000. Values below 4000 drop the ring road. The procedural rail network needs at least 4250. Facepunch raised its historical default from 4250 to 4500 in the Modular Vehicles update, and individual official servers may use another size.
How procedural size works
The dedicated server builds a Procedural Map from two numbers: server.worldsize and server.seed. Seed accepts 0 through 2147483647. Matching both numbers reproduces the same island. Change either value and the next boot writes a new world.
Monument count scales with land area. Tiny worlds pack roadside junk piles tightly. Launch Site wants more land before it appears. Preview a seed on RustMaps before you commit the wipe. Custom map files arrive through +server.levelurl. The .map file already has its own bounds. Editors such as RustEdit produce those files.
RAM, disk, and the wipe curve
Facepunch asks for 12 GB of free RAM and 15 GB of SSD, and calls out that a 6000-meter map spends more of both. Entity count climbs from wipe day to the night before the next reset. Size the box for that late-wipe peak.
On berrybyte, Rust plans attach RAM to the slot card: 8 GB at 50 slots, 12 GB at 75 slots (the Facepunch floor), 16 GB at 100 slots, 24 GB at 200 slots. A 6000-meter public room belongs on the top of that ladder. Peak-hour crash patterns live in Rust common issues.
Set world size
On a berrybyte panel, open Startup, set World Size to the meter value, save, and restart. The matching command-line flag is:
+server.worldsize 4250
+server.seed 1234
+server.level "Procedural Map"
server.cfg stores the bare keys, as in server.worldsize 4250. The cfg file wins when both places set the value. Changing size or seed on an existing identity generates a new procedural map. That boot is a map wipe. Rust wipe schedules covers keeping blueprints as you roll the terrain.
Troubleshooting
Players spawn on a different island than last week when the seed, the worldsize, or the server.identity folder moved.
You dropped to 2500 and want Launch Site back. Render fresh seeds on RustMaps until that monument appears at the new size.
The server sits on "Generating world" for a long time. 5000 and 6000 maps build navmesh and caves for minutes on first boot. Leave the process running.
RAM climbs every day of the wipe as entities accumulate. A scheduled restart during off-hours returns headroom until the next force wipe.
FAQ
What size do official Facepunch servers use? Facepunch raised its historical default to 4500 after using 4250. Individual official servers can use another size. Their browser titles often include the current map size.
Do larger maps include every monument? More land gives the generator room. A 4500 seed can bury a favorite monument in the ocean. Render the seed first.
Will the same seed work at two sizes? Each size is its own layout. Seed 1234 at 3500 and seed 1234 at 4250 are different islands.
How much storage should I leave for a 6k map? Start from Facepunch's 15 GB SSD floor and leave extra for monthly saves plus plugin data. NVMe is what the wiki prefers.
Rust server hosting attaches RAM to the slot count at checkout.