Enshrouded Dedicated Server Backup: Keep World and Character Saves Separate

Inventory the separate save owners

Keen Games' dedicated-server FAQ distinguishes one file per world on the host from character save-games stored on clients. The save-management article describes local saves under `%USERPROFILE%/Saved Games/enshrouded` and dedicated-server saves beside the server executable or in the provider's file manager under the configured saveDirectory. A world backup and a character backup protect different progress; one is not a substitute for the other.

The official support pages disagree on automated world-copy timing: the FAQ mentions a five-minute creation interval, while the later save-management article describes numbered rolling copies created every ten minutes or at shutdown. Do not plan a safe patch or rollback around either interval. Stop the host and make your own dated copy before modifying files.

1. Tell every player to exit the world cleanly. Ask the administrator to stop the dedicated server and wait until its process has ended before copying files.
2. On the host, inspect the current enshrouded_server.json for saveDirectory; the published default is `./savegame`, but a provider or administrator may have changed it.
3. Copy the entire world-save directory, including each world's files and its matching `-index` and metadata files, to a separate dated location. Do not edit the index or choose a rolling slot during a normal backup.
4. Each player separately copies `%USERPROFILE%/Saved Games/enshrouded` or verifies the correct account's Steam Cloud copy. Before replacing local/cloud files, compare modified dates and make a second copy so a sync conflict cannot silently overwrite the only good version.
5. Record client build, server build, backup time and folder locations in a private note. Keep credentials and public IP addresses out of the backup label if it will be shared.
6. Restart only after the copies finish. If restoring, work on a duplicate first and follow the official index/rollback instructions; never experiment on the sole backup.

References: Official Save Game Management · Official Dedicated Server FAQ · Official Dedicated Server Configuration

Use a restore gate before changing the live world

A valid backup is more than a similarly named file. Check that it contains the expected world save, its index/metadata files, and a timestamp from before the patch or incident. Separately confirm that every player has their own character backup. A server provider's snapshot may cover only the world directory; ask what its snapshot excludes.

The later official save-management article says each world has ten numbered rolling copies and describes using the `latest` field in the matching index for rollback. That is a recovery mechanism, not an invitation to edit the live index without a copy. Preserve the original folder and index, test on a duplicate, and stop if the file set does not match the official layout for your installed build.

References: Official Save Game Management · Official Dedicated Server FAQ

Send a reproducible save-management question

If files appear missing, report whether the issue affects the shared world, one player's character, or both; say whether Steam Cloud is enabled and whether the host is a Windows machine or a provider. Include sanitized filenames and timestamps, not account credentials or the full save itself.

GamerWin has not restored a live world or verified a provider backup. Use the official guide for the current supported file procedure and contact the provider for its snapshot/retention behavior. The Steam discussion link is a place to compare player reports, not a substitute for a tested backup.

1. Identify world vs character progress first.
2. Record local, cloud or provider location and the installed build.
3. Compare modification times without overwriting either copy.
4. Keep an untouched copy before any index edit or restore.
5. Remove account IDs, passwords and server addresses from public screenshots.

References: Official Save Game Management · Enshrouded Steam community discussions

Resolve a mismatch without choosing the wrong copy

A world rollback can move shared construction backward while a player's local character remains newer; the official support material describes these as separate save owners. Before restoring, decide which checkpoint should win for each player and communicate that choice. Do not let Steam Cloud automatically overwrite the only local copy while comparing timestamps.

If the host folder is a provider-managed path or the world files do not match the official description, stop before editing `-index`. Ask the provider for its exact snapshot scope and retention schedule, then restore to a duplicate or a provider-supported staging world first.

1. Keep the live world and each client save untouched.
2. Choose a known-good timestamp and label which world and characters it covers.
3. Restore only a duplicate/staging copy first; validate world name and expected progress.
4. Have players confirm their character checkpoint before reconnecting to the restored world.
5. Keep the original backup until the team confirms the restored state.

References: Official Save Game Management · Official Dedicated Server FAQ

Before you play

• Stop the dedicated server before making a manual world copy.
• Back up the complete host world folder and the matching index/metadata files.
• Have each player separately verify or copy their local/cloud character save.
• Do not rely on the conflicting automated-save intervals cited in older official support pages.
• Test rollback on a duplicate and preserve an untouched original.

Frequently asked questions

Sources & revision notes

Editorial revision: November 5, 2026; not a gameplay test date. The reference notes identify source limits and version differences.

1. Official Dedicated Server FAQ (Official)

   Keen Games support article, updated February 21, 2025. It distinguishes server-side world progress from client-side character progress, gives browser filter and Steam Favorites steps, and lists default query port 15637. These legacy support instructions are not a guarantee that every 1.0 host or provider uses unchanged paths/settings.

2. Official Save Game Management (Official)

   Keen Games article updated April 23, 2026. It documents local/Cloud save access and dedicated-server save locations, world index files, and rolling world copies. Its stated rolling-copy cadence differs from the older server FAQ's save interval; this guide flags that discrepancy and advises making an explicit stopped-server copy.

3. Official Dedicated Server Configuration (Official)

   Keen Games support article, last updated February 21, 2025. It identifies the generated Windows server JSON, default save/log directories and allowed 1–16 slot setting. Read the file generated by your installed 1.0 server before applying older examples.

4. Official Recommended Server Specifications (Official)

   Keen Games recommendation dated January 12, 2024: 6-core/3.2-GHz CPU for 4–6 active players, 8-core/3.7-GHz for 16, 16 GB RAM, 30 GB free SSD and 2 Mbps upload per player. This predates full release and is a comparison reference, not a 1.0 benchmark or guarantee.

5. Enshrouded 1.0 release notes (Official)

   Keen Games' October 15, 2026 release changelog provides the 1.0 launch context. It does not certify that older hosting articles or hardware recommendations were revalidated for 1.0.

6. Enshrouded Steam community discussions (Community)

   Player discussion board checked November 5, 2026. Linked for readers to compare reports and ask other players; individual posts are not verified facts or GamerWin tests.