31 October 2026

How to Wipe a Rust Server: Map, Blueprint and Full Wipes

How to wipe a Rust server: which files a map, blueprint and full wipe delete, where the saves live, choosing a new seed, clearing Oxide and Carbon plugin data, and why a running server brings the old world back.

Looking for Rust server hosting?Rent now

To wipe a Rust server, stop it, open its identity folder (server/<identity>/, where everything the world needs is kept) and delete the map and save files, then start it again with a new seed if you want a new map. Add the blueprint database for a blueprint wipe, or every database in the folder for a full wipe. That's the whole job, really. What catches people out is everything around it: the save files Rust rotates and keeps, the plugin data that quietly survives the wipe, and the server that writes the old world straight back because it was still running when the files went.

How to wipe a Rust server

  1. Pick the kind of wipe, and the seed. A map wipe clears the world and keeps learned blueprints, a blueprint wipe clears blueprints and keeps the map, and a full wipe clears both along with all player data. If you want a new map, choose the seed now, while the server's still up.
  2. Update first on force wipe day. Facepunch's monthly update lands on the first Thursday of the month, and its default wipe timer points at 19:00 London time. Update as part of the wipe, so the server comes back on the new build. The update alone starts a fresh map, because the save version in the file names goes up, but the old files stay on disk until you delete them.
  3. Stop the server properly. Use quit or your host's Stop button. Then wait until it's fully down.
  4. Back up the identity folder. Copy all of server/<identity>/ somewhere safe, so a wrong delete can be put back.
  5. Delete the map files. That's every .map, every .sav file and its numbered copies (.sav.1, .sav.2), the _occlusion_ .dat files, the .navmesh files, and the sv.files, player.states, relationship and clans databases, each with the -wal file beside it. player.deaths can go too if you like.
  6. For a blueprint wipe, delete player.blueprints.*.db and its -wal. Leave the map files alone if the map should stay.
  7. For a full wipe, delete every .db and -wal file in the folder. That takes player identities and Rust+ pairings with it. Leave companion.id where it is.
  8. Clear the plugin data that belongs to the old wipe. Plugin clans, kit cooldowns and backpacks live in oxide/data (or carbon/data on Carbon), and none of it is touched by deleting the save files.
  9. Set the seed you picked, then start the server. Change server.seed (and server.worldsize, if the size should change too) before it boots.

Tip: On LOW.MS, wipes run from the Wipe section of your server's Manage tab in the control panel. Each wipe stops the server and takes a backup before it deletes anything. You can list the plugin files it should clear and the seeds it should rotate through, and a schedule will run it on the first Thursday for you. The full walkthrough is in the Guides tab of your server.

The Wipe section of a Rust server's Manage tab, with Wipe now, Wipe schedule and Wipe options
Wipe now, the wipe schedule and the options every wipe uses, on one page

Map wipe, blueprint wipe or full wipe: what each one deletes

Think of the three wipes as three sets of files. Side by side, it's much easier to be sure you've deleted the right ones.

Files in server/<identity>/ (each .db with its -wal) Map wipe Blueprint wipe Full wipe
.map, .sav and its copies, _occlusion_ .dat, .navmesh Deleted Kept Deleted
sv.files, player.states, relationship, clans Deleted Kept Deleted
player.blueprints Kept Deleted Deleted
player.identities, player.tokens (Rust+), player.deaths Kept Kept Deleted
companion.id, cfg/ Kept Kept Kept

The second row is the one people miss. Those are the files Facepunch's own force wipe replaces, since their names carry the save version that goes up with every forced wipe, and they hold Rust's own clans and teams, so a map wipe that leaves them behind opens with last wipe's clans already formed.

When most community servers say "wipe", they mean a map wipe: a new world, and everyone still knows how to craft what they'd learned. Blueprint-only wipes are rare. Honestly, I'd only reach for one if your players are asking for a progression reset and want to keep their bases. Then there's the full wipe, the proper fresh start, and the one that sends people to the Rust+ app wondering where their server's gone (more on that below).

Where are Rust server save files?

Everything lives in the identity folder, server/<identity>/ inside the Rust install. The identity is whatever +server.identity is set to on the command line; Facepunch's own example uses server1, and a lot of servers just use main. Your server.cfg sits in its cfg folder too, so a select-all-and-delete takes your config out with the saves (and rebuilding a server.cfg from memory on wipe night is nobody's idea of fun).

A few things in there are worth knowing before you start deleting:

  • Each database has a -wal file beside it. Rust runs its databases in SQLite's WAL mode, and the -wal is often much bigger than the .db itself, because that's where most of the recent data sits. Delete the pair together. A leftover one won't bring old data back (SQLite throws it away when its database is gone), but it's dead weight.
  • The save is more than one file: Rust keeps a couple of older saves beside the current one, numbered .sav.1 and .sav.2. Delete .sav alone and those copies of the old world stay behind, which is why step 5 says "and its numbered copies".
  • Never delete companion.id. It's your server's identity to the Rust+ app, and Facepunch is blunt about it: delete it and a brand new identity is generated, with "no getting it back once it's gone", and players will most likely have to pair again.
  • Old map files pile up. The server writes a new navmesh and occlusion file for every seed and every save version, and never clears out the old ones. On one server we looked at, the leftovers came to a few hundred MB, all of it copied into every backup.
  • The numbers in the file names are versions. A procedural save is named proceduralmap.<size>.<seed>.<version>.sav, and player.states.289.db sitting next to player.blueprints.18.db is normal: blueprints and identities keep their own version and survive force wipes.

If you're moving a world rather than wiping one, our Rust save location guide covers uploading a save to a server instead.

Why a running server undoes your wipe

A walled Rust base with turrets on the roof, under attack in the evening
Delete the files under a running server and this all comes back

This is an easy one to fall into. Somebody deletes the map files while the server's still up, restarts it, and the old world is back exactly as it was. The server holds the whole world in memory and writes it back to disk on a timer (every ten minutes by default) and when it shuts down cleanly, so the next save puts back the world you just deleted.

So the order matters. Stop first, wait for it to be fully down, then delete. That's step 3, and it's why it comes before the backup and the deletes rather than after.

Choosing a seed and world size

A player on a fresh Rust map at dusk, holding a torch in a pine forest
A new seed is what makes a wipe feel like a fresh start

Facepunch's server docs give the seed as any value from 0 to 2147483647 and the world size as 1000 to 6000. Keep the seed and size and you should get the same map back, which is handy if your players have a favourite (a big game update can still move things around). But a new seed is what makes a wipe feel like a wipe. Most servers change it every time, and that's the choice step 1 asks you to make early.

If you rotate seeds, keep a list of ones you've checked rather than rolling blind. A random seed can put half the monuments in the sea or leave you with one giant snow biome, and I'd much rather find that out on a map preview site than an hour after launch with sixty people online. Pair each seed with the size you checked it at, because the same seed at a different size is a different map.

Bigger isn't automatically better either. A 6000 map with twenty players feels empty, and Facepunch's docs point out that a larger map needs more disk space and memory. It also takes longer to generate, and I'd rather players were in on the first night than waiting. Plenty of community servers sit somewhere between 3000 and 4500, and our Rust server settings guide goes into the rest of the world settings.

Wiping Oxide and Carbon plugin data

Your plugins don't know you've wiped. Oxide keeps their data in oxide/data (Carbon in carbon/data), and plenty of it belongs to the wipe: clan memberships, kit cooldowns, backpack contents, shop balances, stats. Leave it, and the fresh map opens with last wipe's plugin clans already formed. Players notice within about five minutes. That's step 8.

Don't empty either folder wholesale. oxide.groups.data and oxide.users.data live in there too, on Carbon as well as Oxide, and they hold every permission group and user permission, so losing them means rebuilding every admin and VIP group by hand. Not sure what a plugin keeps? Its uMod page often names the data file. Check before the wipe, not during it. Our top Rust Oxide plugins list is a decent place to start if you're choosing which ones to run.

How do I change the Rust wipe timer?

Rust has a wipe timer built in. Most people never notice it. It's the countdown on the laptop at the bottom of the Missile Silo, and it isn't decoration: 24 hours before it runs out, the server starts its endgame events, with F-15 flyovers and Bradleys roaming the roads. By default it assumes the first Thursday of the month at 19:00 London time (or every Thursday, or two Thursdays a month, depending on your server's wipe tag).

Wipe on a different day? Change it to match. The wipetimer.wipeDayofWeek, wipetimer.wipeHourofDay and wipetimer.wipeTimezone ConVars cover a regular schedule, and wipetimer.wipecronoverride or wipetimer.wipeUnixTimestampOverride handles anything odder, like a three-day cycle. Otherwise the endgame starts on a day that means nothing on your server.

Rust wipe troubleshooting

The old world came back after the wipe. The server was running when the files were deleted, so it saved the world back. Stop it, delete the files again, then start it.

Players still have their blueprints after a full wipe. player.blueprints.*.db wasn't deleted. Easy miss. A map wipe keeps blueprints on purpose; a full wipe should take them too.

The new map is the same as the old one. Same seed, same map. Set a new server.seed before you start.

You restored a backup and got a brand new map anyway. The save file is keyed to the seed and size in its name, so a server started with a different server.seed ignores it and generates a new world. Set the seed and size back to the ones in the restored .sav name, then start it.

Rust+ stopped working for everyone. A full wipe deletes the Rust+ tokens along with every other database. Players pair the app with the server again from the Rust+ menu in game, the same way they did the first time.

Clans carried over to the new wipe. If they're Rust's own clans, the clans and relationship databases weren't deleted (step 5). If they're from a plugin, that's oxide/data or carbon/data, which the save files don't include.

The disk keeps filling up after every wipe. Old .map, .sav, .navmesh and _occlusion_ files left behind from earlier seeds and earlier save versions. Rust never clears them out by itself, so they ride along in every backup until somebody notices. Delete the ones that don't match the seed, size and version you're running now.

Planning around Facepunch's dates rather than your own? Our Rust wipe schedule for 2026 lists every force wipe for the year. And if you'd rather the wipes just ran themselves, backup first every time, that's built into our Rust server hosting.

K

Written by

Kurkin

LOW.MS Team

Was this article helpful?

Join our Discord to chat with our staff and community!

Join Discord