Enshrouded Save Backup and Restore Guide: Local, Cloud and Servers

Table of Contents (6)

Enshrouded save backup and restore: the safe answer

For Enshrouded on PC, a backup means copying the complete active save folder somewhere separate while the game or server is closed. A restore means first copying the current save as a safety net, then replacing the active files with that older complete copy. Mixing individual files from different dates is where a recoverable problem becomes a broken world. Enshrouded’s official save-management guide covers the local and Steam Cloud locations.

This guide targets the documented PC Early Access build, version 0.9.1.2 (Hotfix 42), released on June 29, 2026. Enshrouded’s 1.0 release is planned for PC and PlayStation 5 on October 15, 2026, but there is no developer guarantee that current Early Access saves will be fully compatible with 1.0. Keep a dated archive before any major update. Console save locations and PC-to-console transfers are also unconfirmed. Current version and 1.0 status

Which Enshrouded save folder should you back up?

Save type	Active location	What to copy	Critical warning
Local single-player or client-hosted world	%USERPROFILE%/Saved Games/enshrouded with Steam Cloud disabled	The entire enshrouded folder	Quit Enshrouded fully before copying or replacing files.
Steam Cloud world	C:\Program Files (x86)\Steam\userdata\<YourSteamUserID>\1203620\remote	The full contents of the remote folder	A Steam conflict can replace either the cloud or local copy.
Dedicated server world	The saveDirectory set in enshrouded_server.json; default is ./savegame	The complete configured savegame directory	Stop the server process cleanly and ensure players are disconnected first.

Back up a local or Steam Cloud world

Steam decides which client folder Enshrouded uses through Steam Library → Enshrouded → Properties → General → “Keep game saves in the Steam Cloud.” With that option off, use the local Saved Games\enshrouded folder. With it on, use Steam’s AppID 1203620 remote folder. The safe rule is simple: back up the folder that is active for the configuration being used. Official local and Cloud save instructions

1. Exit Enshrouded completely. Do not copy files while it is saving or still running.
2. Open the active save location from the table above.
3. Copy the whole folder, or all contents of Steam’s remote folder, to a separate dated destination such as Enshrouded_2026-09-10_before-update.
4. Keep at least one copy on another drive or a separate cloud-storage destination. A backup sitting beside the live save does nothing for a failed SSD or an accidental folder deletion.

Do not cherry-pick the file with the shortest name and call it done. Enshrouded worlds can include a base world file, numbered segments, index data, character data, and automatic backup files. A complete folder copy preserves the set that belongs together. This is especially worth doing before a game update, server update, mod change, or world transfer. Server backup and migration guidance

Restore a local world without losing the newer save

Restoration is deliberately more cautious than backup. The old copy may fix a damaged build or undo an unwanted change, but it also rolls the world back to the date of that backup. Player progress saved with the same world set can roll back with it.

1. Close Enshrouded completely.
2. Open the active local save folder: %USERPROFILE%/Saved Games/enshrouded when Steam Cloud is disabled.
3. Copy the current folder to a new dated location before changing anything. This is the escape hatch if the older backup is not the one needed.
4. Copy the contents of the chosen backup into the active enshrouded folder, replacing the current files where required.
5. Launch Enshrouded and verify that the intended world and its expected state load correctly.

The same sequence applies to a dedicated server, except the game client is replaced by the server process: disconnect players, stop the server, make a second backup of the live saveDirectory, copy the older complete save set into that directory, then restart the server. The server’s actual location is controlled by saveDirectory in enshrouded_server.json; ./savegame is only the default. Official dedicated-server configuration reference

Steam Cloud restores need an extra layer of caution

Steam Cloud is useful until its local and cloud copies disagree. At that point, Steam’s conflict prompt can push one version over the other. Before resolving a conflict, copy both the Cloud remote folder and the local Enshrouded save folder to separate dated backups. Do this before choosing Cloud or Local in Steam’s prompt.

To deliberately upload a chosen local save to Steam Cloud, Enshrouded’s official procedure is to close the game, back up the existing remote files, clear that Cloud directory, copy the desired local save files into remote, enable Steam Cloud if necessary, and start the game. When Steam reports that the cloud is out of sync, choose the option that uses the prepared local files so Steam adopts them. Clearing the Cloud folder without a separate copy is a needless gamble. Official Steam Cloud upload and conflict workflow

Using an automatic .backup file for a rollback

Enshrouded can retain automatic backup files alongside the active world files. These are useful for a narrow rollback, but they are not a substitute for a full dated backup. Backup filename patterns can vary, so identify the matching active world file and its corresponding backup before renaming anything.

1. Close Enshrouded, or fully stop the dedicated server.
2. Make a complete copy of the active save directory before touching the automatic backup.
3. Move the current matching world file to a separate safety location.
4. Rename the corresponding backup file by removing its backup suffix so it matches the original active filename.
5. Start the game or server and confirm the world has rolled back to the expected state.

This method restores the state held by that automatic backup and can reverse recent world and player changes. If the file relationship is unclear, restore a known-good full folder backup instead of experimenting with partial file sets. Dedicated-server rollback reference