Vintage Story Save Management

Vintage Story Save Management

Vintage Story stores all player data inside the VintagestoryData folder. Dedicated servers also use the data/Saves directory and a serverconfig.json pointer.

Dedicated Server Save Location

On a dedicated server, world files are stored in:

data/Saves/

The active world is defined in serverconfig.json using SaveFileLocation:

"SaveFileLocation": "./data/Saves/default.vcdbs"

Manual Backup (Server)

1. Stop the server.
2. Copy the current .vcdbs file from data/Saves.
3. Store it in a dated backup folder.
4. Start the server again.

Restore a Backup

1. Stop the server.
2. Place the backup .vcdbs file into data/Saves.
3. Update SaveFileLocation in serverconfig.json if the filename changed.
4. Start the server and verify the world loads.

Not sure which backup is still intact - or the world says it may be corrupted? Run the .vcdbs files through our Vintage Story save recovery tool: it checks the SQLite structure of the live world and every backup in your browser (nothing is uploaded), ranks them by integrity and save time, and hands back a clean ready-to-drop copy with stale -wal/-shm sidecars removed.

Moving a world onto a server for the first time, rather than restoring one, is the same steps with more ways to go wrong — and step 3 above is the one that bites. If SaveFileLocation does not resolve, the server does not raise an error you would notice; it generates a fresh world and starts it, which looks exactly like the old one being deleted. Our world handoff tool takes your VintagestoryData folder, picks the world, separates the server-side mods from client-only ones, leaves the regenerable caches behind, and writes that SaveFileLocation line from the filename it actually found.

Next Steps

• Server configuration guide
• Food preservation guide
• Prospecting guide

Looking for managed Vintage Story server hosting? Supercraft runs Vintage Story dedicated servers with daily backups, instant setup, and 4 region options.