How to Back Up, Restore and Move a Rust Server World
Which files make up a Rust server, how to copy them safely, how to roll the world back without costing players their blueprints, and why a backup from before a forced wipe will not load afterwards.
The full identity folder: save, map, player databases and cfg, plus your plugin data if you run Oxide or Carbon.
Stop the server, put back the matching .sav, keep identity, seed and world size the same, then start.
They live in their own file. Restore only the .sav and players keep what they learned since the backup.
A save from before the monthly update cannot be loaded afterwards. Keep config and plugin data, not the old map.
Where a Rust server keeps its data
Everything that belongs to one server lives in a folder named after its server.identity, usually under server in the install directory. That setting is the reason one install can run several servers: each identity gets its own folder. Facepunch’s server wiki lists what is inside, and it is shorter than most people expect.
| File or folder | World and bases | Terrain | Blueprints | Admins and bans |
|---|---|---|---|---|
*.sav | Yes | No | No | No |
*.map | No | Yes | No | No |
player.blueprints and -wal | No | No | Yes | No |
cfg folder | No | No | No | Yes |
player.tokens and companion.id hold the Rust+ pairing. Without them players have to pair again.The game files themselves never need backing up, because SteamCMD reinstalls them. Your world, your players and your settings are all in the identity folder.
Two details trip people up. The .sav name ends in a number, and that number is the protocol version, which goes up at every forced wipe. And the player databases come with a -wal file next to them, a journal Rust uses when it writes. The database and its journal belong together.
How to take a backup you can actually restore
Rust autosaves every ten minutes by default (server.saveinterval 600), so a copy taken at a random moment can miss up to ten minutes of building. A running server is also still writing to its databases. The routine below avoids both problems.
say a warning, then run server.save.quit in the console.-wal files and plugin data included.- Warn your players:
say Server restarts in 5 minutes for a backup. - Run
server.saveto write the world now. - Stop the server from your panel, or with
quitin the console. - Copy the whole identity folder,
-walfiles included. If you run plugins, copy theoxideorcarbonfolder as well. - Keep one copy somewhere other than the server, then start it again.
The plugin folder matters more than it looks. Economy balances, kit cooldowns, clans and zones live in the plugin data folder, and unlike a map they cannot be regenerated. If your host has scheduled backups, check that they include it. Our game server backups explainer covers how often to schedule them.
Restoring the world, step by step
Say an admin command wiped a base, or a plugin spawned something it should not have. Rolling back means putting an older save in place.
- Stop the server.
- Move the current
.savout of the folder rather than deleting it. You may want it back. - Copy the
.savfrom your backup in. Rust also keeps a few older copies next to the live save with a number added to the end of the name. To use one of those, remove only that last number, and leave the protocol number before.savalone. - Bring the
.mapas well if you use a custom map or have changed the map since the backup. - Check that
server.identity,server.seedandserver.worldsize(or the custom map) are exactly what they were when the backup was made. - Start the server and join before you let anyone build.
Step five is the one that fails. Rust builds the save’s file name from the current map. If no file with that name exists, the server starts a fresh map instead of loading your old one, and your backup sits untouched beside it. If your restored world comes up empty, the name does not match, so check seed, size and identity first.
Blueprints: restore the save, not the database
Blueprints are stored in player.blueprints, separate from the save. That gives you a choice. Restore only the .sav and your players keep the blueprints they learned since the backup, while the world goes back in time. Restore the blueprint database as well and they lose those too. Deleting the file forces a blueprint wipe, which is what some servers do deliberately at wipe time.
If you do restore a database file, restore its -wal file from the same backup with it. Do not leave the current -wal next to an older database.
After a forced wipe
Rust updates every month with a forced wipe, and the protocol number in the save name goes up with it. A save from before the update will not load on the new build. Facepunch’s wiki calls renaming an old save to get around this “dangerous and ill-advised”, so do not try it.
A pre-wipe backup is still useful: your cfg folder, admins, bans and plugin data all carry over. Take a backup right before each wipe, and expect to restore the world only within the same build.
Moving a Rust server to a new host
A transfer is a restore on a different machine, and the same rules apply. Stop the old server, copy the identity folder across, and set the new server up with the same identity, seed and world size, or the same custom map. Both servers must be on the same Rust build, which matters in the days around a monthly update. Start it and check your bases before you announce anything. Rust+ pairing needs player.tokens and companion.id to come across too, otherwise players have to pair again.
Many Rust hosts schedule backups and let you restore from the panel. Compare UK Rust hosts, including what each one includes, in our roundup.
Compare the best Rust server hostsRust backup and restore FAQ
Which files do I need to back up on a Rust server?
The whole identity folder: the .sav, the .map, the player databases with their -wal files, and cfg. Add the oxide or carbon folder if you use plugins.
Can I restore a backup from before a forced wipe?
Not the world. The monthly update raises the protocol number and the new build will not load an older save. Your config, admins, bans and plugin data are still worth restoring.
How do I restore a Rust save without wiping blueprints?
Stop the server and restore only the .sav. Leave player.blueprints and its -wal file untouched, and players keep what they have learned.
Why did my restored Rust server start on a new map?
The save name did not match the running map, so Rust generated a fresh one. Check that server.identity, server.seed and server.worldsize match the backup, or that the custom map is the same one.
How often does Rust save the world?
Every ten minutes by default, set by server.saveinterval in seconds. Run server.save to save immediately before stopping the server or copying files.
More Rust server guides
Compare Rust hosts, size your server and set up plugins.
Rust updates, file names and host panels change. Where the current game or your host’s panel works differently from what is described here, follow what you see on your server.