V RisingGuideA V Rising world is a folder of save files. Zip one world folder, from your own PC or from another host, and upload it with Upload World on your server's…
A V Rising world is a folder of save files. Zip one world folder, from your own PC or from another host, and upload it with Upload World on your server's Backups card (or Upload Existing World while creating the server). The server switches its Save Name to that world and loads it at the next start. Your dashboard settings stay in charge; settings files inside the folder are left out.
Close V Rising.
Press Win+R, paste %USERPROFILE%\AppData\LocalLow\Stunlock Studios\VRising\CloudSaves, and press Enter.
Open the v4 folder. If CloudSaves holds another folder instead, open that one first and v4 is inside. Each world is a folder with a long ID as its name, holding files such as AutoSave_12.save.gz.
To tell worlds apart, sort by date modified: the one you played last is the newest.
The dashboard's upload panel shows the same path under "Where are my save files?".
Right-click the world folder and compress it: Compress to ZIP file on Windows 11, Send to > Compressed (zipped) folder on Windows 10. ZIP, RAR, 7Z and TAR.GZ all work. Zip one world only; the server loads one world at a time.
Moving from another host? Download the world's folder from under Saves/v4 on that host and zip it the same way. If you upload a backup of a server that had Scheduled Wipe on, it may hold the world and a copy named like world1_639265602002092346, which V Rising made when it wiped the world. We import the world the server ran and leave the copy out. To use the older world, upload its folder on its own. If your upload holds two worlds from the same server, the SaveName in that server's ServerHostSettings.json (in its Settings folder) decides which one we import.
You can also upload the newest AutoSave_N.save.gz file on its own: one AutoSave file is a whole world, and the upload box zips it for you. The game then counts the world's start date from its first start on your server.
Open My Servers and stop your V Rising server.
On the Backups card, choose Upload World and drop the zip in.
Wait for the import to finish. A backup of the server's current world is taken first, so the world that was there is one click away if you want it back.
Look at Save Name on the Overview card's Details tab: it now names the uploaded world. Leave it that way.
Start the server.

Setting up a new server instead? Switch on Upload Existing World while creating it and the same steps apply.
The world comes across: everything in the save files.
Settings do not. A private game keeps its rules in settings files next to the saves. The server leaves those out and keeps the settings on its Overview card: if your world was played as PvE, check Game Mode on the Details tab before players join, and set rates and castle limits there too.
Worlds from before V Rising 1.1 (in v1, v2 or v3 folders) cannot load on the current game. If your upload holds one beside your 1.1 world in v4, the old one is left out and your 1.1 world is imported. A world saved by V Rising 1.0 or older cannot run on a 1.1 server even in a v4 folder: we read the save itself and say so before your server's world is replaced.
A save that was cut short. If the newest AutoSave in your upload was cut short, for example copied while the game was saving, we leave it out and import the world from its newest whole save. If none of the saves can be read whole, the server card says so: close V Rising, copy the world folder again and upload that copy before you start the server.
Files the game does not load. Save files such as AutoSave_12 - Copy.save.gz are left out beside the real saves. When a folder holds only such a file, we import it under the game's own name. A file that only ends in .save.gz but holds no V Rising save is never imported. Saves written with compression turned off (AutoSave_N.save) cannot be imported: turn CompressSaveFiles back on and let the game save once.
Admins, bans and mods do not come across. Add admins and bans on the Overview card's Admins tab, and mods on the Mods card. Mod settings in BepInEx/config stay behind too: install the same mods and set them again.
Scheduled Wipe (days): the game times the wipe from the day your world was first started. If it is above 0 on your server and your world's next wipe is already due, the upload resets the world's start date, so the first start does not wipe it. The next wipe then counts from the day the world first starts on your server. If a wipe ever does happen, the game moves the old world aside in save-data/Saves instead of deleting it.
Uploading the whole CloudSaves or v4 folder with several worlds in it. Upload one world folder. Two identical copies of the same world folder (for example world1 and world1 - Copy) are fine: we import one and the server card names the copy we skipped.
Changing Save Name back to the old one. The upload replaced the server's saves, so that does not bring the previous world back. Restore it from Backups instead (the backup taken just before the upload).
Ask in Discord or email support@haptic.gg with the name of the zip you uploaded and a screenshot of your Save Name setting.