How Map Size Affects Rust Performance

The World Size you pick for a procedural Rust map sets how big the world is, and a bigger world costs the server more. Facepunch's own wiki puts it simply: "The larger the map, the more disk space and memory you need." This guide covers what map size changes, what it doesn't, and how to see whether your server is coping. Checked against Facepunch's Creating a Server wiki page, our plan sizes and Rust build 2635, October 2026.

What map size changes

• Memory. Facepunch's wiki lists 12 GB of free RAM as a starting point and adds "6k map will use more". It also says these values "are not fixed and highly depend on the use case and population of the server".
• Disk. A bigger map takes more disk space, according to the same page.
• The range. Facepunch says to use 1000 to 6000, and our World Size field on the Startup tab accepts the same range.

Facepunch gives no table of RAM against map size, and we haven't invented one. What we can say is how our own plans are sized:

How much RAM does a Rust server need? goes into the memory side. The Rust plans page has current plans.

Players and CPU

Facepunch's wiki says "The more players, the faster your computer CPU needs to be", and gives no number.

Facepunch's Naval Update post (February 2026) named the physics broadphase as Rust's largest bottleneck and said it was expensive "due to the size of the map in Rust and the density of colliders that large bases have". The post also described targeted changes to the physics engine that drastically sped up that stage.

See whether your server is coping

Open the Console tab. It shows CPU and RAM cards for the server.

1. Watch both while the server is busy, such as on wipe day.
2. If the RAM card sits near its limit, the map or the plugin list needs more memory. Go to the bigger plan.
3. If RAM has room but players lag, look at CPU load, which player count and large bases drive.

Why is my server lagging? goes through the graphs in more detail.

Change the map size

1. Take a backup in the Backups tab.
2. Open the Startup tab and set World Size and World Seed.
3. Save and restart. The server generates a new map on the way up, so players lose their bases. How to set your Rust wipe schedule, map and blueprint wipes covers doing it at a wipe.

Picking a size

• Small community or weekly wipes: 3000 matches our smallest plan.
• A larger, steady population: go up a size only with the RAM to match, using the table above.
• Unsure: start at 3000 and watch the RAM card for a full wipe before you grow.