Save Editing & Transfer

Enshrouded: Save Transfer & Editing

Many players start in co-op (host and play) and later want to move to a 24/7 dedicated server without losing their base. Enshrouded 1.0 (15 October 2026) changed how worlds are stored, so older rename guides no longer apply. Here is how a world moves now.

How to Move an Early Access World to a 1.0 Server

1. Stop the server.
2. Move the server's current world0.ksd and its backup folder out of savegame, somewhere safe. Do not delete them.
3. Copy your world's files into savegame: the hex-named file (for the first world, 3ad85aea), its -index file and its numbered copies (3ad85aea-1 and so on).
4. Start the server. The log shows [savedata2-migration] Found file '3ad85aea'... while it converts, then the world loads as world0.ksd.
5. Join and check your base before you delete anything you set aside.

This is the sequence the servers we run went through on launch day. A world already saved by the 1.0 game goes in the same place: stop the server, keep the current world0.ksd aside, put the new world in as savegame/world0.ksd, start.

Update, 21 October 2026: Hotfix 1.0.0.3 fixed a rare crash during this conversion. The conversion now also moves a Flame Altar that sat outside the voxel grid back into it, but Keen says that base's water cannot be loaded and has to be re-added.

How to Move a 1.0 Local World to a Server, or to a Friend

1. Close the game first, so the file is complete, and switch Steam Cloud off for Enshrouded while you move files. The default folder above holds local saves; a world you keep as a cloud save sits in Steam's userdata folder instead.
2. Copy that world's worldN.ksd file. The number is the slot, not the world's name. If you are not sure which file is which, the free Enshrouded Save Rollback tool lists every world it finds in a folder with its size and the time it was last saved, without uploading anything.
3. On the server: stop it, move the current savegame/world0.ksd and the backup folder aside, put your file in as savegame/world0.ksd, start it.
4. For a friend who hosts from the game rather than a server, send the same file. One launch-day report has this working between two local save folders, with Steam Cloud off on both sides and a backup of every file taken first.

Characters are not in the world file. Levels, skills and inventory stay with each player's own game, so nobody loses a character when a world changes host.

Save Editors

"My save got corrupted, how do I get back to the endgame?"

• Third-party save editors exist, but they were written for the Early Access format. 1.0 stores worlds in a new format, so check that an editor supports 1.0 before you point it at world0.ksd.
• Moving a base between worlds: a community tool called Emberbridge extracts a flame-altar base from one world and imports it into another, in the browser. As of October 2026 its own compatibility note says it reads Early Access worlds only and rejects SV2C, the 1.0 format, so it cannot take a base out of a 1.0 world yet.
• Warning: always copy the whole savegame folder before any edit.

Backups and Rollback

A 1.0 server writes up to ten rolling copies to savegame/backup/ as world0.ksd.backup-0 to world0.ksd.backup-9. The number says nothing about age; the file time does. To restore:

1. Stop the server.
2. Move the current world0.ksd aside.
3. Copy the backup you want into savegame and name it world0.ksd.
4. Start the server.

The free Enshrouded Save Rollback tool lays the ten copies out by save time and hands you the one you pick, already named world0.ksd. The full walk-through, including the Early Access -index method, is in Save Rollback & Backups.

Safe keeping. Host your Enshrouded server with Supercraft and utilize our easy-to-use File Manager to upload your worlds; we handle the permissions automatically.