V Rising Save Location & How to Upload Your World

You have been playing V Rising solo or on a friend's private game, and now you want the same world on a LOW.MS dedicated server so everyone can join without the host being online. The save format is identical between a private game and a dedicated server, so the world, your castle, your gear, and the map progress all carry over. You just need to copy the right folder into the right place and point the server at it.

This guide walks you through finding the save on your PC, uploading it through your LOW.MS control panel, and getting the server to load it on the next restart.

Where V Rising Saves Live on Your PC

V Rising keeps saves under your Windows user profile. The exact path depends on how the world was hosted.

Private game hosted from the V Rising client:

%USERPROFILE%\AppData\LocalLow\Stunlock Studios\VRising\Saves\v3\

Local dedicated server you ran yourself:

%USERPROFILE%\AppData\LocalLow\Stunlock Studios\VRisingServer\Saves\v3\

Paste either path into the File Explorer address bar and press Enter. Inside the v3 folder you will see one or more subfolders with long GUID names (something like a4f8c1b2-7e9d-...). Each one is a separate world.

Open the folder for the world you want to move. You should see files like AutoSave_####.save.gz, StartingCompressedSave, ServerGameSettings.json, ServerHostSettings.json, SessionId.json, and StartDate.json. That whole folder is the save.

If you are not sure which GUID folder is the right one, sort by Date Modified and pick the most recent.

Before You Do Anything

Take a backup first. World corruption during a transfer is rare but not impossible, and a backup takes thirty seconds.

1. Log in to https://control.low.ms and open your V Rising service.
2. Run Cloud Backup to snapshot whatever is currently on the server.
3. Zip up the local save folder on your PC as well, just so you have a copy outside the game directory.

While you are here, stop the server from the service page. Trying to overwrite a save file that the game has open will either fail silently or corrupt the save.

Rename your local save folder to something short and memorable before uploading, such as myworld. The GUID name works fine, but a readable name makes the next step easier.

Uploading via File Manager

The File Manager handles small-to-medium saves well. If your world folder is under roughly 200 MB, use this route.

1. In the control panel, open File Manager for your V Rising service.
2. Navigate to Saves/v3/.
3. Drag your renamed save folder (for example myworld) into the browser window, or use the Upload button.
4. Wait for every file inside to finish uploading. Do not refresh mid-transfer.

If the folder already exists on the server from an earlier test, delete it first so you do not end up merging files from two different worlds.

Uploading via SFTP

For larger worlds, or if you prefer a proper client, use SFTP. LOW.MS exposes SFTP on port 8822.

• Host: the IP shown on your service page
• Port: 8822
• Username / password: the FTP credentials on the service page
• Remote path: /Saves/v3/

FileZilla and WinSCP both work. Connect, navigate to Saves/v3/, and drag your save folder across. SFTP handles interruptions better than a browser, so it is the safer option for bigger transfers.

Pointing the Server at Your World

The server decides which world to load from the SaveName value in ServerHostSettings.json. Until that matches your uploaded folder, the server will happily boot a fresh world and ignore the one you just uploaded.

1. In File Manager, open VRisingServer_Data/StreamingAssets/Settings/ServerHostSettings.json.
2. Find the "SaveName" line.
3. Change the value to match the folder name you uploaded. For example: "SaveName": "myworld".
4. Save the file.

If your service uses a startup parameter instead, set -saveName myworld under Service Settings. The same rule applies: the name has to match the folder exactly, including case.

Starting Up

Back on the service page, start the server. Open the Web Console and watch the boot log. You are looking for a line confirming it loaded your save rather than creating a new one. It should mention myworld (or whatever you named the folder) and report the existing session ID.

Once the server is up, connect from the V Rising client and check that your castle, inventory, and map reveal are intact. Walk around your base for a minute before calling it done.

If something looks wrong, stop the server and run Cloud Restore to roll back to the snapshot you took at the start.

A Few Things to Know

• Persistence version matters. The v3 folder is tied to the current save format. If a future V Rising patch moves saves to v4, your old v3 folder will not load until Stunlock ships a converter.
• Mod saves are not portable to vanilla. If your local world used mods that altered world data, a vanilla dedicated server may reject it or load it in a broken state. Match the mod set on both ends.
• Game version matters too. Run Steam Update on the service to bring the server to the same patch level as your client before loading the save.
• Character data is stored inside the world. Uploading the save brings every character on that world with it — you do not migrate players separately.
• Delete stale AutoSave files from the old server folder before uploading if you are replacing an existing world. Leftover .save.gz files from the previous world can confuse the loader.

That is the full round trip. Local world to dedicated LOW.MS server with your progress intact.