How to Back Up, Restore and Move a V Rising Server World
Where a V Rising server keeps its world, how to take a backup you can actually restore, how to roll back to an older autosave, how AutoSaveSmartKeep keeps older restore points, and how to move a single-player world to a dedicated server.
Saves/v4/<SaveName>/: numbered AutoSave_ files and a few small session files.
Settings/: host and game settings, plus adminlist.txt and banlist.txt.
The server loads the newest autosave, so remove the newer ones and restart.
Before every patch, and before the first start after one. Stunlock recommends both.
Where a V Rising server keeps your world
Everything that belongs to your server lives under one folder, the persistent data path. On a self-hosted Windows server it defaults to %USERPROFILE%\AppData\LocalLow\Stunlock Studios\VRisingServer\, and the -persistentDataPath launch option moves it anywhere you like. On a rented server, your host’s file manager shows the same two folders inside it.
| Path inside the data folder | What it holds | Back it up? |
|---|---|---|
Saves/v4/<SaveName>/ | The world: numbered autosaves such as AutoSave_0.save.gz, plus small files with the session’s settings, ID and start date | Yes, the whole folder |
Settings/ | ServerHostSettings.json, ServerGameSettings.json, adminlist.txt, banlist.txt | Yes |
| Server install folder | The game files themselves | No, Steam reinstalls them |
Two names in that path matter. <SaveName> is the SaveName setting, which decides which world the server boots, so one server can hold several worlds side by side. And v4 is the persistence version. Stunlock changes that number whenever an update breaks the save format, which is one more reason to keep a copy from before every patch.
Autosaves are not a backup
V Rising writes a new autosave every AutoSaveInterval seconds and keeps the number set by AutoSaveCount. Stunlock’s own instructions use 120 seconds and 20 saves as their example. That gives you restore points for the last stretch of play, which is perfect for undoing a bad raid or an admin mistake.
It does not protect you from the problems Stunlock lists as the reasons to keep backups: a hardware failure, losing or closing down the server, or a bug that corrupts the save. The autosaves live on the same disk, in the same folder, as the world they would replace.
| Problem | Autosaves on the server | Host’s scheduled backups | Your own off-server copy |
|---|---|---|---|
| Bad raid or admin mistake | Yes | Yes | Yes |
| Save broken by a patch | Partly | Partly | Yes |
| Hardware failure | No | Partly | Yes |
| Server lost or closed down | No | No | Yes |
How to take a backup you can restore
- Warn your players and shut the server down cleanly. A copy taken while the server is writing can catch a save half-finished.
- Copy the whole
Saves/v4/<SaveName>folder, not just the newest file. - Copy the
Settingsfolder with it, so admins, bans and your rules come back too. - Put the copy somewhere other than the server: your own PC or cloud storage.
- Start the server again.
Do this before you apply a game update, and again before the first start on the new version. Stunlock recommends both, because an update is the moment a save is most likely to break. If your host offers scheduled backups, check that they copy the save folder, and download one now and then so a copy exists outside the host. Our game server backups explainer covers how often to schedule them.
Rolling the world back
When the server starts, it loads the newest autosave in the world folder. Rolling back is a matter of making the save you want the newest one.
- Stop the server.
- Copy the whole world folder somewhere safe first, so you can undo the rollback.
- Move every autosave newer than the point you want out of the folder.
- To go further back than your autosaves reach, put the save files from your backup into the folder instead.
- Start the server and log in to check before you let players back in.
Keep older restore points with AutoSaveSmartKeep
Twenty autosaves two minutes apart only reach back 40 minutes. If a griefer struck last night, they are all from after it. AutoSaveSmartKeep fixes that by keeping a spread of saves across time instead of only the newest ones.
The value is a list of A:B:C entries. A is a window in minutes back from now, B is how many of the newest saves in that window to keep, and C is how many of the oldest. Each window starts where the previous one ended. Stunlock’s example value works out like this:
| Entry | Window | What it keeps |
|---|---|---|
10:1:1 | Last 10 minutes | The newest and the oldest save |
30:0:1 to 2880:0:1 | Nine windows: 30 minutes, 1, 2, 3, 4, 6, 12, 24 and 48 hours | The oldest save in each |
52560000:99:0 | Everything older, up to about 100 years | The 99 newest |
The catch is the order the two settings apply in. At every autosave the server applies AutoSaveSmartKeep first, then deletes the oldest saves until no more than AutoSaveCount are left. With AutoSaveCount at 20, the long tail gets cut, so raise it if you want saves from days ago. To use AutoSaveCount on its own, leave AutoSaveSmartKeep empty.
Scheduled wipes are covered too. If you set ResetDaysInterval above 0, the server starts a fresh world on that schedule and backs up the previous save when it does.
Moving a single-player or hosted world to a dedicated server
A world you started from the game client can move to a dedicated server running the same game version. The client keeps those worlds under %USERPROFILE%\AppData\LocalLow\Stunlock Studios\VRising\CloudSaves\<SteamID>\v4\ or ...\VRising\Saves\v4\, each in a folder with a random name.
- In the game, open Load Game, pick the world and choose Go to Directory. That opens the right folder.
- Copy the folder somewhere safe before you change anything.
- Rename the folder to something simple, such as
clanworld. You can drop the older autosaves, because only the newest one is loaded, and removeServerHostSettings.jsonif your server already has its name and password set. - Upload it to
Saves/v4/on the server. - Set
SaveNameto the folder name, or start the server with-saveName clanworld. - Leave
GameSettingsPresetempty, so a preset does not replace the settings that came with your world.
Afterwards, delete the local copy from the Load Game menu while the game is running, so it does not show up twice. If you delete the files by hand while the game is closed, cloud sync puts them back next time you launch.
Moving to a new host
A host move is a backup and a restore on two machines. Stop the old server, download the world folder and Settings, upload both to the same places on the new server, and set SaveName to match. Both servers must run the same game version, so do it on a day without a patch. If you are still choosing where to go, our V Rising RAM guide covers plan sizes.
This guide covers the PC server. PlayStation 5 servers run their own server build with their own instructions.
Many V Rising hosts run scheduled backups and let you restore from the panel. Compare UK hosts, and what each one includes, in our roundup.
Compare the best V Rising server hostsV Rising backup and restore FAQ
Where are V Rising server save files?
In Saves/v4/<SaveName>/ inside the server’s persistent data path. On Windows that defaults to %USERPROFILE%\AppData\LocalLow\Stunlock Studios\VRisingServer\, and -persistentDataPath changes it.
How do I restore an older V Rising autosave?
Stop the server, copy the world folder for safety, then move every autosave newer than the one you want out of the folder. The server loads the newest autosave left when it starts.
How often does a V Rising server save?
Every AutoSaveInterval seconds, keeping AutoSaveCount saves. Stunlock’s instructions use 120 seconds and 20 saves as their example. Your host may use different values.
Can I move my single-player V Rising world to a server?
Yes. Copy the world folder from the client’s v4 save folder into Saves/v4/ on the server, rename it, and set SaveName or -saveName to that folder name.
Do I need to back up before a V Rising update?
Yes. Stunlock recommends a backup before patching and before the first start after a patch, since updates are when saves are most likely to break.
More V Rising server guides
Compare hosts, size your server and tune its settings.
V Rising updates and host panels change. Where your server or your host’s panel works differently from what is described here, follow what you see on your server.
