Rust Server Wipes Explained: Forced, Map and Blueprint Wipes
Rust servers wipe because Facepunch forces them to. The game updates on the first Thursday of each month, the update changes the network protocol, and your old map save can no longer load, so every server gets a fresh map at least monthly. Whether blueprints are wiped too is your decision, and how often you wipe beyond the monthly minimum is up to you.
Below: what the forced wipe actually does, the files behind a map, blueprint and full wipe, how to wipe from the panel, how to change seed and world size, and how to schedule and announce wipes. Details were checked against the Facepunch Rust wiki in November 2026.
- Forced wipe: the first Thursday of each month at 19:00 London time by default. The monthly update makes old map saves unloadable.
- Map wipe = delete the map (
.map) and save (.sav) files. Blueprint wipe = also deleteplayer.blueprints. On ChicagoServers, the Wiper tab does map, blueprint, player data and plugin data wipes for you. - Change Map seed and World size on the Startup tab (they are
server.seedandserver.worldsize) before restarting to get a different map. - Make a backup on the Backups tab before wiping anything.
- Wipe frequency is announced through a server tag (weekly, biweekly or monthly), not a convar.
On this page
What the forced wipe does
Facepunch ships a major update on the first Thursday of the month. Each update bumps the network protocol, and the number at the end of Rust's save and database file names is that protocol version. After the update the server creates new files rather than reusing the old ones, so the previous map save is left behind and a new map generates. Bases and loot are gone.
Facepunch's wiki says forced wipes normally affect only the .sav map file. Blueprints survive unless you delete the blueprint file yourself. Do not rename an old .sav to dodge the wipe; the wiki calls that dangerous and ill-advised.
Map wipe vs blueprint wipe vs full wipe
| Wipe type | What players lose | Files in your server identity folder |
|---|---|---|
| Map wipe | Bases, loot, world state | proceduralmap.*.map and proceduralmap.*.sav (including numbered backup saves) |
| Blueprint wipe | Researched blueprints | player.blueprints.*.db |
| Full wipe | Everything above plus other player data | Map and save files, blueprint files and the remaining player .db files |
The files live in server/<identity>/, where the identity is the name of the server's save folder. File names contain version numbers that change between Rust builds, so match the pattern instead of a literal name. Rotating save backups carry a numeric suffix alongside the current save, and a thorough map wipe removes those too. You do not need to find these files on ChicagoServers; the Wiper tab does it.
Most servers wipe the map monthly and blueprints either every wipe or every few wipes. Weekly and biweekly map wipes are common on community servers. Rust has no setting that decides this for you, so pick a cadence and stick to it.
How to wipe your server step by step
- Announce it
Warn players first. On the Console tab you can type a message such as
say Wipe in 5 minutesand press Send. - Back up first
Open the Backups tab. Under Back up now, choose World and settings (or Whole server) and click Back up now. There is no undo after a wipe, but a backup can be put back from Your backups.
- Wipe from the Wiper tab
Open the Wiper tab and choose what to wipe: the map, blueprints, player data or plugin data. Use plugin data if you run Oxide or Carbon and plugins keep claims, timers or base data that should not carry across a wipe.
- Set the new seed and world size
On the Startup tab change Map seed and World size (see below), click Save startup, then start or Restart the server from the top of the page. It generates a new map on boot, which can take a few minutes.
Hosting with ChicagoServers? The Rust server hosting page lists what is included, such as a one-click Oxide/uMod and Carbon installer, free server backups and SFTP file access.
Changing the seed and world size
A map wipe on its own regenerates a map from whatever seed and size the server is configured with. To get something different, open the Startup tab, change Map seed and World size, click Save startup, and restart. Map and Custom map URL are on the same tab if you want a specific map instead of a procedural one.
server.seed 123456
server.worldsize 3500server.seed(Map seed) accepts values from 0 to 2147483647 according to the Facepunch wiki.server.worldsize(World size) is suggested between 1000 and 6000. Larger maps need more disk space and RAM.- Set these on the Startup tab, not in
server.cfg. They are panel fields and are applied at the next start.
Preview a seed on a map-viewer site before committing to it; the same seed and size always produce the same map for a given Rust build. Rust's map generation changes in some updates, so an old favorite seed can look different after a major patch.
Scheduling and announcing wipes
Facepunch's wiki defines wipe frequency through your server browser tags: monthly, biweekly or weekly. Set tags with the server.tags convar as a comma-separated list. Open the Configs tab, pick Server settings (server.cfg), add the line, click Save, then Restart. For example:
server.tags weekly,vanillaSeparately, Rust has a wipe timer convar group that controls the in-game countdown on the Nuclear Missile Silo monument and when the endgame events start. These do not delete anything. They only keep the in-game timer honest. They also go in Server settings (server.cfg) on the Configs tab. The Facepunch wiki lists them as:
| Convar | Purpose |
|---|---|
wipetimer.wipeDayofWeek | Day of the wipe, 0 to 6 with 0 as Sunday. Default is 4 (Thursday). |
wipetimer.wipeHourofDay | Hour in 24-hour time, decimals allowed. Default is 19. |
wipetimer.wipeTimezone | IANA time zone, default Europe/London. |
eventschedulewipeoffset.event_hours_before_wipe | How many hours before the wipe the endgame events begin. 0 disables them. |
Type PrintWipe on the Console tab to see the frequency, time zone, time until the next wipe and the next ten scheduled dates. The wiki also documents unix timestamp and cron overrides, but notes the cron convar name is spelled inconsistently, so test your server's behavior if it does not take effect.
For announcements, put the wipe schedule in the Description field on the Startup tab and in your Discord, keep the schedule tag accurate, and post a reminder a day ahead. Players plan their week around wipes.
To run the wipe itself on a timer, open the Schedules tab. Under Add a scheduled task, name it and choose When (times are Chicago time). Use Add a step for Send console commands (a warning to players), Wait 5 minutes, then Install a game update, which includes a Rust wipe among its choices. Click Add task. A task can be tested with Run now.
Frequently asked questions
When is the Rust forced wipe?
The first Thursday of each month. Facepunch's wipe timer defaults to 19:00 London time. Check the monthly update announcement if exact timing matters.
Do blueprints wipe on forced wipe?
Facepunch's wiki says forced wipes normally affect only the map save. Blueprints are kept unless you delete the player.blueprints file yourself.
How do I change the map on my Rust server?
Make a backup on the Backups tab, then open the Wiper tab and wipe the map. On the Startup tab set a new Map seed and World size, click Save startup, and restart.
Can I wipe more often than monthly?
Yes. Many servers wipe weekly or biweekly. Use the Wiper tab each time (or a task on the Schedules tab) and keep the weekly, biweekly or monthly tag accurate.