Enshrouded 1.0 Saves: Compatibility, Backup Locations, and Rollback

Early Access saves work in 1.0

Keen’s launch FAQ says existing Early Access saves can be used after the 1.0 release. The save format is converted to a newer format. Keen also encourages starting over because the world and first hours changed substantially, but that recommendation does not mean an old save is rejected.

Back up before the first 1.0 load. Conversion, a cloud conflict, or a corrupted file is much easier to diagnose when the untouched pre-conversion folder still exists.

Find the correct save

Make a backup that can survive an update

1. Exit Enshrouded. For a dedicated server, stop its process and wait for shutdown to finish.
2. Identify whether the active data is local, Steam Cloud, or a server world. Do not assume all three are identical.
3. Copy the complete relevant folder to a dated location outside the game and server installation folders.
4. Keep file names and the accompanying index and _info metadata files together.
5. Only after verifying the copy exists, launch 1.0 or change cloud settings.

Use rolling world copies carefully

Keen documents ten numbered rolling copies for each world. A new copy is created about every ten minutes or when the game shuts down, and the oldest copy is overwritten. The associated -index file identifies the active copy with its latest value.

Before editing that index to roll back, copy every save file elsewhere. Choose the candidate by modified time and preserve the original index. A rolling copy can help with recent world damage, but it is not a substitute for an offline backup because the rotation eventually overwrites older states.

Move local saves to Steam Cloud without guessing

Keen’s documented process starts with Steam Cloud turned off: back up and clear the App ID 1203620 remote folder, copy the local Saved Games/enshrouded files into it, turn Steam Cloud on, then use the local files when Steam reports a conflict. Read the current support article before doing this—the direction of the copy matters.

Never resolve a cloud conflict by choosing the newest timestamp blindly. Compare the machine, world, and last known play session first, and keep both sides until the desired world loads correctly.

Missing character after 1.0 migration

Hotfix 1.0.0.2 stopped one corrupted-character case from crashing during conversion but could leave the affected character out of the list. Hotfix 1.0.0.3 then improved migration for invalid entries in additional backpack slots; Keen says those characters should now migrate, without the items that caused the process to stop. Update through 1.0.0.3 or later, preserve the affected files before retrying, and attach the relevant before-and-after saves to an official bug report if the character is still missing.