Enshrouded Save Game: Autosave, Backups and Rollback

Enshrouded Save Game: Autosave, Backups and Rollback

Enshrouded keeps ten rolling copies of every world, so a bad save is rarely the end of a base. How you roll back depends on the format: 1.0 servers use one world0.ksd file and a backup folder, while Early Access worlds used a static hexadecimal ID with the active copy selected through a companion -index file.

Does Enshrouded Autosave?

Yes, and only that: there is no save button and no save command. The game writes the world on its own while you play, and quitting to the main menu through the menu writes it once more, which is why a crash or Alt+F4 can cost the last minutes. A dedicated server also writes the world when it shuts down, and keeps ten rolling copies of it next to the live file. When something goes wrong you roll back to one of those copies, not to a save you made yourself.

1.0 changed the format (15 October 2026). A 1.0 server keeps the live world in one file, world0.ksd, and its ten rolling copies in a backup folder as world0.ksd.backup-0 to -9; there is no -index file any more. On its first 1.0 start the server converted the Early Access world and moved the old hex-named files, including their -index, into a migrated folder, which it no longer reads. This is what the servers we run showed on launch day. To move a world to another server or to a friend, see Save Transfer & Editing.

The 1.0 Save Folder

1.0 Rollback Checklist

1. Stop the server cleanly.
2. Copy the whole savegame folder somewhere safe.
3. In savegame/backup, sort by modified time and pick the newest copy saved before the problem.
4. Move the current savegame/world0.ksd aside, copy the chosen file in its place and name it world0.ksd.
5. Start the server and check the world before inviting everyone back.

The rest of this page describes the Early Access format, which the migrated folder still holds and which a server that never converted still uses.

What the Early Access Save System Looked Like

Known World IDs

World 1: 3ad85aea
World 2: 3bd85c7d
World 3: 38d857c4
World 4: 39d85957
World 5: 36d8549e
World 6: 37d85631
World 7: 34d85178
World 8: 35d8530b
World 9: 32d84e52
World 10: 33d84fe5

Early Access Rollback Checklist

1. Stop the server cleanly.
2. Copy the entire savegame directory somewhere safe before touching anything.
3. Find the world's -index file.
4. Open it in a text editor and locate the latest value.
5. Change that value to an older copy number from 0 to 9.
6. Save the file and start the server.
7. Verify the world date and affected structures before inviting the full group back in.

The fiddly part of that checklist, working out which copy was saved when, is automated by the free Enshrouded Save Rollback tool: point it at your save folder in the browser and it lays the rolling copies out as a timeline with their save times. For a 1.0 folder it hands you the copy you pick, already named world0.ksd, to put in place of the current one; for an Early Access folder it marks the copy the server loads and writes the corrected -index. Nothing is uploaded, and the save files themselves are never touched.

When to Use Rollback Instead of Guesswork

• Base edits vanished after a crash or forced kill.
• The world loads, but recent terrain or structure changes are obviously broken.
• The save exists, but the active copy is newer than the last known good state.

When Rollback Will Not Fix the Problem

Need safer world recovery than manual file surgery on a home PC? Host your Enshrouded server with Supercraft and keep restore points within easy reach.