Quick wins for a faster PC:
Clear out junk files and repair common Windows errorsFree Scan →Scan for outdated or missing drivers - takes under a minuteDriver Scan →Repair Windows errors before they cause bigger problemsFix Now →Change a Rust server’s map by editing its launch configuration or hosting-panel Startup settings, then restarting the server. For a procedural map, set server.seed and server.worldsize; for a downloaded custom map, set server.levelurl. Changing the seed or world size creates a new world, so back up the existing save before you restart.
Prefer not to run the server on your own PC? Godlike.Host offers hosted Rust servers with free DDoS protection and up to three free backups a day.
What changing the map actually means
Rust does not provide a normal in-game button for changing the server’s world. The map is selected when the dedicated server launches. You therefore make the change in one of three places: the command used to start the server, a server.cfg configuration file, or the Startup area of a game-server control panel. The server must then be stopped and started again before the new settings take effect.
| # | Preview | Product | Price | |
|---|---|---|---|---|
| 1 |
|
Rust Key Cards, Rust Red Key Card, Cobalt Restricted Access Cards, Rust Gift For Gamers, Blue Key... | $25.00 | Buy on Amazon |
| 2 |
|
Rust Video Game Notebook | $15.00 | Buy on Amazon |
| 3 |
|
Rust Game Props Large Furnace (S) | $14.99 | Buy on Amazon |
As an Amazon Associate I earn from qualifying purchases.
Windows Errors? Fix Them Before They Spread
Repair common Windows errors and clear accumulated junk for a smoother, more stable PC - no reinstall needed.Free scan · no reinstallCrashes, No Sound, or Screen Glitches?
Random freezes, missing sound and display glitches usually trace back to one bad driver. Find and replace yours safely.Free scan · under a minuteThere are two fundamentally different map choices:
- Procedural Map: Rust generates a world from a numeric seed and a world-size value.
- Custom map: Rust downloads or reads a specific
.mapfile from the URL supplied inserver.levelurl.
These choices are not interchangeable. A custom map uses the file supplied by server.levelurl; the seed and world-size settings are ignored while that custom level is active.
Choose procedural generation or a custom .map file
| Choice | Settings used | Best for | Important limitation |
|---|---|---|---|
| Procedural Map | server.level, server.seed, server.worldsize |
Communities that want a fresh, naturally generated island and control over its layout through a seed | Changing the seed or size generates a new world and removes the current world state |
| Custom map | server.levelurl |
Hand-built, event, role-play, or downloaded maps supplied as a .map file |
server.seed and server.worldsize do not alter the custom file |
If you only want a different coastline, monument arrangement, or starting terrain while retaining Rust’s normal procedural behavior, use a new seed. If you need a deliberately designed island, use a custom map URL.
#1 Best Overall
- Inspired by the Rust Video Game – These cards replicate the iconic keycards found in Rust (Red, Blue, Green).
- High Quality PVC Plastic – Printed on both sides, durable and water-resistant. Not a sticker.
- Great Rust Gift Idea – Perfect for fans of Rust, whether for cosplay, loot-themed gifts, or collection.
- Wallet-Size Replica – Standard 3.375x2.125 inches, 30 mil thick—fits in any wallet.
- NOT a sticker*
Rust map settings you need to know
| Convar | Purpose | Accepted or documented values |
|---|---|---|
server.level |
Selects the map type | For the normal generated world, use Procedural Map |
server.seed |
Chooses the procedural world layout | Integer from 0 through 2,147,483,647 |
server.worldsize |
Sets the approximate procedural map size | Facepunch’s Rust Wiki lists a recommended range of 1,000 to 6,000 |
server.levelurl |
Points the server to a custom .map file |
A direct URL to the map file; seed and world size are then ignored |
The current default world size is not safe to assume. Published references disagree: one listing gives 4,000, another guide mentions 3,000, and a historical account says the default changed from 4,250 to 4,500 during the Modular Vehicles update. Check the value on your own server instead of relying on any of those figures.
Before changing anything
Warn players about downtime and a possible wipe
Changing only a launch setting still requires a restart. Tell players when the server will be offline and whether you are changing the world. A seed or world-size change is not a cosmetic refresh: the generated terrain and save are different, so bases, deployables, containers, vehicles, and other placed objects from the old world will not appear in the new one.
Do these 3 things before closing this tab:
1Scan for outdated or missing drivers - takes under a minute2Clear out junk files and repair common Windows errors3Fix the driver behind crashes, sound loss and screen glitchesBack up the existing save
Stop the server before copying its world data. The exact directory depends on the installation and host, but one hosting guide identifies server/server1/ as the save location. Treat that path as an example rather than a universal rule: inspect your server’s file manager or installation directory and copy the complete world folder to storage outside the live save location. Include the seed and world size in the backup name, such as before-map-change-seed-12345-size-3500, so you can identify it later.
Check resources before choosing a large world
Guides consistently report that memory requirements rise as world size increases, but no authoritative source in the available documentation supplies a dependable gigabyte requirement for every Rust version, plugin set, and player count. Do not treat an advertised RAM number as universal. If your server is already close to its memory limit, choose a conservative size, monitor the host during generation, and test a larger map during a maintenance window.
How to change to a new procedural map
1. Choose and preview a seed
Select Procedural Map as the level type and decide on a seed between 0 and 2,147,483,647. A seed determines the generated layout; the same seed and world-size combination is intended to produce the same procedural arrangement for the relevant Rust build. Preview the candidate before committing it. RustMaps is commonly cited for seed previews, but treat a preview as a planning aid rather than a guarantee that every monument, road, or terrain detail will match after a game update.
2. Select the world size
Use a value in the documented 1,000–6,000 range unless your server software or host imposes a narrower limit. A small value reduces the playable area; a large value gives players more territory but consumes more resources. Do not change the size accidentally when you only meant to change the seed: both values participate in the generated world.
What’s actually slowing this PC down?
Pick the symptom - the matching free tool is one click away.
3. Save the old world
With the server stopped, make the backup described above. Do not overwrite the backup when the new world is generated. If the new map has a problem, a separate copy is what gives you a practical way to return to the previous world.
4. Edit the launch configuration
Use the syntax appropriate to your installation. A typical startup command contains entries like these:
+server.level "Procedural Map" +server.seed 12345 +server.worldsize 3500In a configuration file, the equivalent settings are commonly written one per line:
server.level "Procedural Map"
server.seed 12345
server.worldsize 3500Some control panels do not show a file at all. Instead, open the server’s Startup or Launch Parameters section, locate the fields for level, seed, and world size, enter the new values, and save. Panel labels and layouts vary, so use the field descriptions supplied by your host. Do not paste a complete command into a field that expects only a number.
Rank #2
5. Restart and allow generation to finish
Start the server after saving the settings. Rust must generate the new world before players can use it. Keep the console visible during the first launch and wait for the server to finish loading rather than repeatedly restarting it. A restart alone does not convert an existing save into a different map; the new seed or size causes Rust to create a separate world state.
6. Verify the values in the console
After the server is online, query the values from the server console:
server.seed
server.worldsizeConfirm that the returned values match the ones you intended. One forum report describes an apparent off-by-one result in which the effective seed was one higher than the entered value. That report is not an official rule, so use the console output and an in-game inspection to determine what your installation actually generated.
How to load a custom Rust map
1. Obtain a compatible .map file URL
You need a direct URL that serves the custom .map file to the server. A page that merely displays a map, requires a browser login, or redirects to a download form may not work. Check that the file is reachable from the server and that its creator identifies it as compatible with your Rust version.
2. Back up the current procedural world
Make the same offline backup before switching to the custom level. The old procedural world is still valuable if you later return to it, even though the custom map does not use its seed or size.
3. Set server.levelurl
Replace the procedural settings with the custom-map URL in the startup command, configuration file, or panel field. Conceptually, the launch settings look like this:
server.levelurl https://example.invalid/my-map.mapThe address above is an illustration of the required format, not a real map location. Use the exact direct URL supplied by the map creator or host. Because the URL selects the complete map file, changing server.seed or server.worldsize will not resize or regenerate it.
4. Restart and read the console
Save the setting, restart the server, and watch for download or map-loading errors. If the file cannot be fetched, the server may fall back, stop loading, or leave you with a world that is not the one you expected. Resolve the URL or file-compatibility problem before inviting players back.
Where to make the change
| Server setup | Where to edit | What to check |
|---|---|---|
| Self-managed dedicated server | The startup script or the server’s configuration file | The edited file must be the one the launch script actually reads; preserve the existing executable and other required arguments |
| Managed hosting panel | The Startup, Launch Parameters, or similar configuration page | Save the panel form, confirm that the values remain after reopening it, then perform a full restart rather than only reconnecting a game client |
Provider interfaces are illustrative rather than standardized. If a panel regenerates the startup command automatically, manual edits to a generated file may be overwritten the next time you press Save or Restart. Make the change in the panel’s supported Startup fields whenever they are available.
What happens to the old world
A new seed or world size produces a new procedural world with no old save objects. Players should expect their bases, storage, monuments’ previous loot state, and other placed or changed objects to be absent. This is why the backup must happen before the first launch with the new settings.
Rank #3
- Acrylic Painting Pla Plastic
To return to the previous world, stop the server, restore the backed-up world folder to the location used by your installation, and restore the original map settings. Because folder names and save layouts differ between installations, verify the target path in your file manager or host documentation before replacing anything. Keep the backup untouched until the restored world has been verified in game.
Independent reader supportYour contribution helps us test, update, and keep practical guides available for everyone.Troubleshooting map changes
The map did not change
- Confirm that the server was fully restarted after saving the setting; reconnecting to a running process is not enough.
- Check the actual launch command or active configuration file, not a similarly named template.
- Query
server.seedandserver.worldsizein the console and compare the returned values with your intended values. - If a control panel rewrites startup parameters, re-open the Startup page and verify that your entries were retained.
The server loads an unexpected seed
First compare the console output with the value you entered. The documented seed range is inclusive from 0 to 2,147,483,647. A forum report has described an effective value one higher than the requested seed, but this is not established as a universal behavior. Record the actual console value and use that value when comparing a preview or documenting the world for players.
The Tool Desk
Outbyte PC Repair FREEClear out junk files and repair common Windows errorsFree Scan →Outbyte Driver Updater FREEScan for outdated or missing drivers - takes under a minuteDriver Scan →The custom map is ignored or fails to load
- Check that the setting is
server.levelurl, not a web page URL or a local path that the server cannot access. - Verify that the URL points directly to a
.mapfile and that the file is still available. - Remove assumptions that seed and world size will modify the custom map; those convars are ignored when
server.levelurlis active. - Read the startup console for download, permission, or compatibility errors and correct the file or URL before restarting again.
The server struggles after increasing world size
Reduce the size and test again if memory use becomes excessive. Available guides agree that larger worlds require more memory, but they do not provide a single verified RAM figure that applies across Rust versions and server configurations. Measure your own server under its expected player load instead of selecting a size from an unqualified hardware chart.
Players report that bases disappeared
That is the expected result when the server is running a newly generated seed or size, not evidence that the client map cache is wrong. Stop the server and restore the pre-change save and settings if you intended to preserve the old world. If the wipe was intentional, communicate the new seed and size so players understand that they are on a fresh world.
How to decide on a practical world size
There is no universally correct size. Use the recommended 1,000–6,000 range as a boundary, then balance the playable area against the resources available to your server. A compact community server may prefer a smaller world that keeps players closer together. A larger community or a server designed for exploration may choose more territory, provided its hardware and maintenance process can handle the additional memory demand.
Do not confuse the documented range with a promise of identical performance. Plugins, concurrent players, Rust updates, and other server settings affect resource use. If you need a larger world, test it with a copy of the server and watch memory during generation and normal play. Since no verified universal RAM table is available, publish your own observed limit only after measuring it on the exact setup you operate.
Worked configuration examples
New procedural world with a chosen seed
+server.level "Procedural Map" +server.seed 987654 +server.worldsize 3000This requests a procedural map with seed 987654 and world size 3,000. It replaces the active procedural world, so the old save must be backed up first.
Custom event map
server.levelurl https://example.invalid/event-island.mapThis requests the complete map file at the supplied direct URL. The numeric seed and world size do not determine the terrain in this mode.
Checking the running procedural world
server.seed
server.worldsizeUse the returned values as the authoritative record for the running process, especially when a panel, script, or reported seed appears inconsistent.
Quick Recap
Final pre-restart checklist
- Choose Procedural Map or a custom
.mapfile. - For procedural generation, select a seed from 0 to 2,147,483,647 and a world size in the documented 1,000–6,000 range.
- For a custom map, obtain a direct, compatible
.mapURL and remember that seed and world size will be ignored. - Warn players about downtime and whether the change creates a fresh world.
- Stop the server and copy the complete existing save folder;
server/server1/is one reported location, not a universal path. - Edit the active startup script, configuration file, or hosting-panel Startup fields.
- Restart once, wait for generation or download to finish, and inspect the console.
- Run
server.seedandserver.worldsizeto verify the live values. - Keep the backup until the new map has been tested and accepted by your players.
Product prices and availability are accurate as of the date/time indicated and are subject to change. Any price and availability information displayed on Amazon at the time of purchase will apply.
