To move a V Rising world to a hosted or dedicated server, stop the destination server, back up its existing files, locate the correct local world folder, upload that folder’s contents through FTP or the host’s file browser, and make the server’s configured SaveName match the uploaded world folder. Restart the server and join it to verify the transfer.
Playing with friends? Godlike.Host runs hosted V Rising servers from 10 data-center locations, with free DDoS protection.
The exact directory varies between a Steam client, a managed host and a self-hosted server. Persistence-version folders can also change after breaking save-format changes, so keep the original destination save until the migrated world has loaded successfully.
As an Amazon Associate I earn from qualifying purchases.
The Tool Desk
Outbyte Driver Updater FREEFix the driver behind crashes, sound loss and screen glitchesFind Drivers →Outbyte PC Repair FREEClear out junk files and repair common Windows errorsFree Scan →What you need before moving the world
Plan the migration as a replacement of one complete world, not as a few individual files. A V Rising save can contain several autosave directories and supporting data. Copying only a single file or uploading into the wrong directory can make the server open a blank world even though the transfer appears to have succeeded.
- Access to the Windows computer containing the world.
- FTP credentials or a file browser for the destination server.
- Permission to stop and start the destination server.
- A separate backup location for both the local world and the destination server’s current save.
- The destination server’s configuration file, usually
ServerHostSettings.json, if the world folder name must be changed. - Enough time for every file to finish uploading; do not close the FTP client or browser during an active transfer.
Do not copy files while the destination server is running. The server can write a new autosave during the transfer and leave you with a partial or inconsistent world. Tell players when the maintenance window begins, and keep the source copy untouched until everyone has confirmed that the migrated world is working.
#1 Best Overall
![V Rising Standard - PC Steam [Online Game Code]](https://m.media-amazon.com/images/I/31XsC6wxF5L._SL160_.jpg)
- Awaken as a Vampire. Hunt for blood in nearby settlements to regain your strength and evade the scorching sun to survive.
- Raise your castle and thrive in an ever-changing, open world full of mystery. Gain allies online and conquer the land of the living.
Find the correct V Rising save folder
Steam client: CloudSaves
Nitrado documents the common client location as:
C:Users<username>AppDataLocalLowStunlock StudiosVRisingCloudSaves
Open the folder named for your Steam ID. Inside it, open the persistence-version directory, such as v1, and then the GUID-named world directory. The GUID folder is the world you need to transfer; the Steam-ID directory and the persistence-version directory are parent containers, not the world itself.
Recommended Free Tools
If Windows hides AppData, paste the path into File Explorer’s address bar or use %USERPROFILE% in place of the user name. Do not select the first folder that looks like a save. Drill down until you can see the world’s own AutoSave_x directories and other files.
See Nitrado’s save-location guide for the documented layout.
Alternative client location: Saves
Stunlock Studios’ dedicated-server instructions also list this client path:
%USERPROFILE%AppDataLocalLowStunlock StudiosVRisingSaves
Crashes, No Sound, or Screen Glitches?
Random freezes, missing sound and display glitches usually trace back to one bad driver. Find and replace yours safely.Free scan · under a minutePC Slower Than It Used to Be?
A free scan shows the junk files, broken settings and background clutter dragging Windows down - then fixes them in one click.Free scan · Windows 10 & 11Depending on the game and save format, the persistence directory may be named v1, v3 or another version. Stunlock says the persistence-version number changes whenever there are breaking changes to the persistence or save format. Use the folder that contains the world you actually played, and do not assume that an older version folder is current.
If both CloudSaves and Saves exist, compare their world folders and autosave times rather than merging them. Pick the location that contains the latest complete copy of the world you intend to publish. The official instructions are available in the Stunlock Studios server instructions.
Rank #2
Dedicated-server save location
For a self-hosted dedicated server, saves are normally under:
%USERPROFILE%AppDataLocalLowStunlock StudiosVRisingServerSaves
A start script can set a different persistent-data path. If the server was launched with a custom data directory, use that configured directory rather than the default Windows path. The server’s own save structure still contains a persistence-version folder and a world folder.
The Windows account running the service matters when you are looking for the default location. A service launched under another account can write to that account’s profile, while a custom persistent-data argument can redirect saves somewhere else entirely. Check the launch script or service configuration before concluding that the default folder is empty.
How to identify the right world
Open each candidate world folder and look for its autosave directories. If several worlds or copies exist, compare the AutoSave_x timestamps and select the newest complete save from the world you intend to publish. GPORTAL’s official transfer demonstration also instructs users to choose the newest local save by autosave timestamp before uploading it.
Use recognizable in-game details as a second check. If you know where your castle, character or clan base was located, record those details before the move and compare them after the server starts. Folder names alone are not always descriptive because local worlds can use GUID-style names.
Quick wins for a faster PC:
Repair Windows errors before they cause bigger problemsFix Now →Fix the driver behind crashes, sound loss and screen glitchesFind Drivers →Choose the transfer method and hosting path
A managed provider may offer FTP, a browser-based file manager, or both. FTP is useful for copying a complete folder and seeing transfer status; a file browser can be more convenient when the provider handles credentials inside the control panel. For a self-hosted server, you normally work directly in the configured persistent-data directory.
| Comparison point | Questions to ask |
|---|---|
| File access | Does the host provide FTP, a file browser, or both? Can you upload folders and confirm completion? |
| Backups and rollback | Can you download the current save or restore a provider backup before replacing it? |
| Documentation | Does the provider clearly identify the V Rising save path and persistence-version directory? |
| Configuration control | Can you edit or replace ServerHostSettings.json and set SaveName? |
| Region, support and price | Compare the provider’s current region availability, support response and published price separately; the cited guides do not establish current prices or backup policies. |
Nitrado’s example uses FTP and the remote directory /vrising/nitrado_data/Saves/v1/world1. GPORTAL’s official video demonstrates stopping the server, selecting the newest local autosave and transferring by FTP. These examples show the workflow, but another host can use a different root, world name or persistence version.
Rank #3
- THRILLING ADVENTURE: Dive into the excitement of Forbidden Desert, where players work together to uncover a legendary flying machine; enhances strategic thinking and cooperation.
- CHALLENGING STRATEGY: This game offers a unique gameplay experience with its cooperative mechanics; perfect for enhancing teamwork skills among friends and family.
- FAMILY FUN: Designed for ages 10 and up, it's ideal for family game nights; 45-minute playtime fits perfectly into any gathering.
- VIBRANT DESIGN: Featuring multi-colored components, it captures the imagination; a visually appealing addition to any board game collection.
- EASY TO LEARN: Comes with clear instructions to get players started quickly; ensures a smooth and enjoyable gaming experience for all levels of players.
Upload the save: the safe sequence
1. Back up both sides
- Make a copy of the local world folder, including its persistence-version and GUID/world-folder context. Store it somewhere outside the game’s save directory.
- Stop the destination server from the host control panel or the self-hosted service manager.
- Before replacing anything, download or copy the destination server’s existing save. This is your rollback if the wrong world is selected or the transfer is incomplete.
Nitrado’s documented workflow begins by stopping the server before opening FileZilla or another FTP client. Treat the backup as mandatory even when the destination appears to contain a new, unused world. A separate backup also protects you if the provider’s file browser deletes more than intended.
2. Connect to the destination
For a managed server, open the provider’s FTP details or file browser and connect with the supplied credentials. A hosted panel may expose a browser-based editor instead of FTP; the important requirement is access to the server’s save directory while the server is stopped.
What’s actually slowing this PC down?
Pick the symptom - the matching free tool is one click away.
Nitrado gives this example remote location:
/vrising/nitrado_data/Saves/v1/world1
That path is an example for a Nitrado instance, not a universal path. Other hosts can use a different root, persistence version or world name. For a self-hosted server, browse to the persistent-data directory selected by the server’s launch configuration.
3. Open the destination world directory
Inside the remote Saves directory, open the destination persistence-version folder and then the world folder. If the host created a default world, you will usually see one or more AutoSave_x directories inside it.
Do not upload the entire local CloudSaves, Steam-ID or persistence-version parent. The transfer target is the contents of the selected local world folder. If you upload the parent, you can create a path such as world1GUID-folderAutoSave_x when the server is expecting world1AutoSave_x.
4. Remove or archive the destination autosaves
Nitrado instructs users to delete the remote AutoSave_x folders before uploading the local save. If your host provides a download or rename function, archiving those folders first is a safer rollback option; otherwise, confirm that your separate destination backup is complete before deleting them.
Do these 3 things before closing this tab:
1Repair Windows errors before they cause bigger problems2Fix the driver behind crashes, sound loss and screen glitches3Clear out junk files and repair common Windows errorsDo not delete the destination configuration simply because you are replacing the world. The configuration can contain the server name and other settings you still want to retain. The item that must point to the uploaded world is the SaveName value.
5. Upload the local world contents
- Open the local GUID-named world folder in File Explorer.
- Select the files and folders inside it, including every relevant
AutoSave_xdirectory. - Upload those contents into the remote world directory, not into its parent
Savesdirectory. - Wait for the transfer to finish. Keep the FTP client or browser open until all files report successful completion.
- Check the remote directory after the upload and confirm that the expected autosave folders are present at the same level as they were locally.
Uploading one level too high creates a nested world folder and leaves the server looking in the wrong place. Uploading only one autosave can also omit other files the world needs. The destination should contain the same world-content structure as the local folder.
Rank #4
- Dark Legacy is a 2-player card game with RPG elements that focus on character customization
- 120 playable original art cards
- There are 2 of 6 opposing factions included in this starter set
- Age 14+
6. Make the configured save name match
If you kept the destination world folder’s original name, the existing configuration may already point to it. If you renamed the uploaded folder, edit ServerHostSettings.json and set SaveName to exactly the uploaded world-folder name. Save the configuration before restarting.
Nitrado’s save-location documentation specifically calls out this name match. A mismatch can make the server create or open a different world instead of the files you just uploaded. Do not change a persistence-version directory name to make it look like another version; preserve the version selected by the game and server.
7. Restart and test
- Start the destination server.
- Wait for it to finish loading before joining.
- Connect with the game client and check a few known world details: player location, structures, inventories and progression.
- Ask another player to connect if the world is multiplayer; this can reveal a permission or loading problem that is not visible to the host.
- Only after the world loads correctly should you remove the rollback copy.
Managed host versus self-hosted transfer
| Destination type | Where you work | What to verify |
|---|---|---|
| Managed host with FTP | Provider FTP credentials and an FTP client such as FileZilla | Provider-specific remote save path, persistence version and upload completion |
| Managed host with a file browser | Host control-panel file manager | Server is stopped, the correct world directory is open and the panel saves edits |
| Self-hosted dedicated server | Configured persistent-data directory on the server computer | Launch script path, ServerHostSettings.json and Windows account used by the service |
The technical operation is the same in each case: stop, back up, replace the world contents, align SaveName, restart and test. What changes is the path and the way you access it. The cited documentation establishes the workflow, but it does not establish current hosting prices, regional availability or backup policies for every provider.
Common mistakes and how to fix them
The server starts a blank world
- Check that the uploaded files went inside the configured world folder rather than one directory above or below it.
- Check
ServerHostSettings.json;SaveNamemust match the uploaded folder name exactly, including capitalization where the host treats names as distinct. - Check that you uploaded the contents of the intended GUID folder, not the Steam-ID or persistence-version parent.
- Stop the server again, restore the destination backup if necessary, and repeat the upload with the correct folder level.
The host shows the save folder but no world progress
Compare the local and remote contents. A transfer that stopped midway can leave only some autosaves. Upload again while the server is stopped and wait for every file to report completion. Do not overwrite your only local copy while troubleshooting.
The local path does not contain the expected world
Check both documented client locations: CloudSaves<SteamID><persistence version><world> and Saves<persistence version><world>. Search the persistence-version folders, including v1, v3 or another version created by a save-format change. Use autosave timestamps and the world’s contents to identify the correct folder.
The server refuses to load after an update
Persistence-version changes can represent breaking save-format changes. The official Stunlock instructions warn that the version number changes when the persistence format changes. Keep the original save, confirm that the client and server are on compatible game versions, and test the migrated copy rather than deleting the source. The available documentation does not guarantee compatibility across every future version change or host implementation.
FTP connects but files cannot be changed
- Confirm that the destination server is stopped; some panels make save files read-only while the service is running.
- Verify that the FTP account has write permission for the V Rising save directory.
- Use the provider’s file browser if FTP access is unavailable, or ask the host to confirm the correct remote root.
- Check that you are not connected to a read-only backup directory instead of the active persistent-data path.
The world loads, but recent progress is missing
You may have selected an older autosave or the wrong world folder. Stop the server, restore the backup, identify the newest correct local autosave by timestamp, and transfer the complete world contents again. Keep the old destination copy until the replacement has been verified in-game.
The server keeps creating a new folder
This usually indicates a name or path mismatch. Compare the exact remote world-folder name with SaveName, confirm that the persistence-version folder was not renamed, and verify that the launch configuration points to the directory you edited. Restart only after saving the corrected configuration.
Best Value
Compatibility, naming and rollback rules
- Keep the source save untouched until the server has been joined and checked.
- Preserve the persistence-version directory selected by the game; do not manually rename
v1tov3or the reverse. - Use the server’s configured persistent-data path when a launch script overrides the default
VRisingServerSaveslocation. - Change
SaveNameonly when the uploaded world folder name differs from the configuration. - After game or server updates, make a fresh backup before attempting another migration.
- Retain the destination backup until you have checked loading, structures, inventories and progression in the live server.
A practical migration checklist
- Identify the local world under
CloudSavesorSaves. - Confirm the persistence-version folder and choose the intended GUID/world folder.
- Compare autosave timestamps and select the newest complete copy.
- Copy that world folder to a separate backup location.
- Stop the destination server.
- Back up the destination save.
- Open the provider’s FTP/file-browser path or the self-hosted persistent-data path.
- Open the destination persistence-version and world directory.
- Delete or archive its existing
AutoSave_xfolders. - Upload the contents of the local world folder.
- Set
SaveNameto the uploaded folder name if it changed. - Save the configuration, restart the server and join it.
- Verify the world before removing either backup.
This sequence follows the documented Nitrado procedure, the save paths published by Nitrado and Stunlock Studios, and the autosave-selection and FTP steps shown in GPORTAL’s official demonstration: Nitrado upload instructions, Nitrado save locations, Stunlock Studios instructions and GPORTAL’s official video.
Frequently Asked Questions
Where is the V Rising save file located?
On a Windows client, check C:Users<username>AppDataLocalLowStunlock StudiosVRisingCloudSaves<SteamID><version><world> and %USERPROFILE%AppDataLocalLowStunlock StudiosVRisingSaves<version><world>. The world folder is the GUID-named folder containing the autosaves.
Can I transfer a private world to a dedicated server?
Yes. Stop the dedicated server, back up its current save, upload the contents of the private world folder into the server’s configured world directory, align SaveName if the folder name changed, and restart to test.
Do I upload the whole CloudSaves folder?
No. Upload the contents of the selected GUID-named world folder. The Steam-ID and persistence-version folders are parent containers and should not be nested inside the destination world directory.
How do I move a save to Nitrado?
Stop the Nitrado server, connect with FileZilla or another FTP client, open the provider’s V Rising save path such as /vrising/nitrado_data/Saves/v1/world1, back up the existing save, remove or archive its AutoSave_x folders, and upload the local world contents. Make SaveName match if you renamed the world.
Free tools Windows power users keep installed
One-click scans. No signup required.
How do I move a save to GPORTAL?
Use GPORTAL’s FTP or file-management access while the server is stopped. Select the newest local save by autosave timestamp, transfer the complete world contents into the destination world directory, then restart and verify the world.
What if my save is in v1 but the server uses v3?
Do not rename the version folder manually. Persistence-version numbers can change when the save format has breaking changes. Keep a backup, ensure the client and server versions are compatible, and test the copied world before removing the source.
Why does the server load a blank world after upload?
The usual checks are folder level and naming: confirm that the autosaves are directly inside the configured world directory, verify the exact SaveName, and make sure you uploaded the intended GUID world rather than a parent folder or older copy.
Should I delete the old server save before uploading?
Nitrado’s procedure deletes the remote AutoSave_x folders before upload. First download or archive the destination save so you can roll back if the wrong world or an incomplete transfer is discovered.
What’s actually slowing this PC down?
Pick the symptom - the matching free tool is one click away.
Are current hosting prices included in this procedure?
No. Pricing, regions, support terms and backup policies change by provider and location. Compare those items directly with the host; the file-transfer steps do not establish a current price.
The Bottom Line
Stop the server, preserve backups, identify the correct persistence-version and GUID world folder, and upload its contents into the destination world directory—not its parent. Remove or archive the destination autosaves, set SaveName to the uploaded folder name when necessary, restart, and verify the world in-game before deleting any rollback copy.
Quick Recap
Product prices and availability are accurate as of the date/time indicated and are subject to change. Any price and availability information displayed on Amazon at the time of purchase will apply.
