Enshrouded Server Backup and Restore: Protect Your World in 1.0

Where Enshrouded dedicated servers save worlds

The default dedicated-server configuration uses saveDirectory: "./savegame", although a provider can change the path. The world is stored server-side while characters are stored on player clients, so an administrator should back up the world separately from any local character saves. A control-panel download or SFTP export is usually the simplest portable copy.

Official documentation: Keen Games reference ↗

How automatic saves and rolling backups differ

Keen’s dedicated-server FAQ describes regular saves, while its older save-management documentation explains rolling copies for the previous storage layout. Enshrouded 1.0 introduces a new format with a simpler folder structure and automatic conversion of older data. Do not assume the legacy index-file rollback method works unchanged on newly converted worlds. Verify the restore process against the version actually running.

Official documentation: Keen Games reference ↗

Create a portable backup before updating

Ask players to disconnect and stop the server cleanly. Export the complete world folder, the current enshrouded_server.json and any related configuration that governs access or gameplay. Store the archive on a different device or storage service, label it with the game version and timestamp, and keep at least one known-good backup from before the update.

Restore a world without losing newer data

Stop the server, download the current save directory as an emergency backup, then restore your chosen archive into the configured save location. Preserve the directory structure and avoid mixing different world versions. Restart, inspect logs, join with a test character and confirm buildings, quests and inventory access before inviting the full group back.

What to look for in a managed hosting backup system

Useful Enshrouded hosting includes scheduled off-server backups, a documented retention period, one-click restoration, file access and a way to download full world archives. Ask whether the advertised backup is stored outside the same machine and whether restoring overwrites the current world. A cheap monthly price is less appealing if recovery depends on an uncertain support ticket.

A practical backup schedule for active communities

For a busy world, combine the game’s normal saving with daily independent snapshots and a longer retention period that spans at least one major update. The exact schedule depends on how much progress players would tolerate losing. Keep one pre-patch archive, one known-good recent archive and a copy outside the provider account. Check that the backup includes the complete world structure and not merely screenshots or configuration files.

How to test a backup safely

A backup is useful only when it can actually be restored. If the host supports a staging server or spare slot, restore a recent archive there and inspect a recognisable base. Otherwise arrange a maintenance window, take a new emergency copy of the current state, restore the archived version and verify it with a trusted player. Avoid testing restoration directly against the only surviving copy of your live world.

Should you use provider backup or manual SFTP downloads?

Ideally use both. Provider snapshots make short-term rollback faster, while a manual full export protects against account closures, provider outages and migration problems. Look for clear retention policies and off-server storage, but remember that features differ by hosting plan. For long-running Enshrouded worlds, the ability to download and restore data is a meaningful purchase criterion.

Related Enshrouded server guides

These guides cover the next practical step, from sizing and installation to keeping your world safe after Enshrouded 1.0.