What’s actually slowing this PC down?
Pick the symptom - the matching free tool is one click away.
iTechGuides is reader-supported. When you buy through links on our site, we may earn an affiliate commission. As an Amazon Associate I earn from qualifying purchases. Learn more
Playing with friends? Godlike.Host runs hosted Enshrouded servers from 10 data-center locations, with free DDoS protection.
The safest Enshrouded dedicated-server backup is a complete copy of the server’s configured save directory, made after players leave and the server has stopped cleanly. The default directory is ./savegame, but enshrouded_server.json may point elsewhere. Copy the entire world file set—including numbered rolling copies, _info files and -index files—to a dated location outside the live installation. To restore, stop the server and replace its save contents with that complete set. To roll back a damaged world, preserve a full backup first, then change that world’s -index value from latest to a numbered copy from 0 through 9.
What an Enshrouded server backup actually protects
A dedicated server’s save data represents the shared world: the world state, bases, quests and other progress that players see together. It does not contain each player’s complete character progression. Keen Games states in its Dedicated Server FAQ that “Character progression is stored only on clients.” Every player therefore needs a separate backup of their own client-side character data in addition to the server-world backup.
Do these 3 things before closing this tab:
1Repair Windows errors before they cause bigger problems2Scan for outdated or missing drivers - takes under a minute3Clear out junk files and repair common Windows errorsThe server creates save files every five minutes, according to Keen Games’ FAQ. Each world also has ten numbered rolling copies intended for backup and rollback. Keen’s Save Game Management documentation says a new rolling copy is created every ten minutes or when the server shuts down; the newest copy replaces the oldest once all ten slots are in use. Those automatic copies are useful for recovering from a recent mistake, but they are not a substitute for an independent backup: they remain on the same machine and inside the same save set as the live world.
- Dedicated-server backup: shared world progression and the files needed to load that world.
- Client backup: each player’s character progression, stored on that player’s computer or in their Steam Cloud storage.
- Rolling copies: ten numbered versions of each world, useful when the latest state is damaged or an unwanted change must be reversed.
Where Enshrouded save files are stored
The location depends on whether you are managing a dedicated server or an individual game client. Do not assume the default path is active: read the server configuration before copying anything.
#1 Best Overall
- Easily store and access 5TB of content on the go with the Seagate portable drive, a USB external hard Drive
- Designed to work with Windows or Mac computers, this external hard drive makes backup a snap just drag and drop
- To get set up, connect the portable hard drive to a computer for automatic recognition software required
- This USB drive provides plug and play simplicity with the included 18 inch USB 3.0 cable
- The available storage capacity may vary.
| Data | Location or access method | What it represents |
|---|---|---|
| Dedicated-server world | The directory named by saveDirectory in enshrouded_server.json; the documented default is ./savegame. |
Shared world progression, including the world file set and its rolling copies. |
| Local client saves | %USERPROFILE%/Saved Games/ |
Client-side game data, including a player’s character progression. |
| Steam Cloud data | Accessed through Steam Remote Storage. | Cloud-held client data, subject to the player’s Steam synchronization state. |
A relative path such as ./savegame is interpreted relative to the directory from which the dedicated server is run. If the server was installed, launched or scripted from a different working directory, the physical folder may not be where you first expect. The value in enshrouded_server.json is the authority for your installation.
Before copying: make the backup safe and restorable
File-level copying is safest when no process is writing to the save files. A running server can update the world while a copy is in progress, leaving a backup whose files were captured at different moments. That may make the set unusable or omit the most recent changes. The documented five-minute save interval is useful for understanding when writes occur, but it does not make copying a live directory safe.
- Tell every player to leave the world and wait for them to disconnect.
- Stop the dedicated-server process through its normal shutdown procedure rather than terminating it abruptly.
- Confirm that the process has exited before opening or copying the save directory.
- Keep the live installation untouched until the backup has been checked.
- Use a dated folder outside the server installation for each backup. Include the server version in the folder name or in a companion note.
Keen Games recommends making a copy of all save files before changing them. A second copy on an external hard drive or another independent destination is a practical way to avoid losing both the live data and the backup to one machine failure. Keen does not prescribe a storage brand or capacity; the important properties are that the destination is independent and that the complete save set can be restored.
How to back up an Enshrouded dedicated server
- Announce the maintenance window. Ask players to leave the world. If someone remains connected, their latest actions may not be represented consistently when the server stops.
- Stop the server cleanly. Use the server’s normal shutdown method and wait until the dedicated-server process has exited. Do not begin the copy while the process is still running.
- Read the configured save path. Open
enshrouded_server.jsonin a text editor and findsaveDirectory. Record the exact value. If it is unchanged, the documented default is./savegame; if it contains another path, back up that path instead. - Open the actual save directory. Verify that it contains the world files and the associated numbered copies,
_infofiles and-indexfiles. A backup that contains only one apparent world file is incomplete. - Copy the complete directory. Copy every file and subdirectory in the configured save directory to a new folder outside the live server installation. Preserve filenames, extensions and the directory structure. Do not select only the newest-looking file.
- Name the backup clearly. Include the date and, if you operate more than one server or world, the server or world identifier. Record the dedicated-server version alongside it so that you know which software produced the files.
- Create an independent second copy. Copy the finished backup to an external hard drive or another storage destination that is not the same disk as the live server. This protects the recovery point if the server disk fails or the live folder is accidentally replaced.
- Restart and verify. Start the dedicated server normally. Join or inspect the world and confirm that it loads, the expected bases and quests are present, and the server is reachable before treating the backup as complete.
The backup is not complete until the first copy exists in a separate dated location and the server has successfully loaded after the maintenance. If the server fails to start at that point, stop and preserve both the original save directory and the copied folder rather than repeatedly editing files.
Rank #2
- Easily store and access 1TB to content on the go with the Seagate Portable Drive, a USB external hard drive.Specific uses: Personal
- Designed to work with Windows or Mac computers, this external hard drive makes backup a snap just drag and drop. Reformatting may be required for Mac
- To get set up, connect the portable hard drive to a computer for automatic recognition no software required
- This USB drive provides plug and play simplicity with the included 18 inch USB 3.0 cable
- The available storage capacity may vary.
Choosing a backup approach
The right approach depends on how much data must be protected and how far back recovery may need to go. The following distinctions prevent a common mistake: treating an automatic rolling copy or a cloud-synchronized client file as equivalent to an independent server backup.
| Approach | Scope | Recovery point | Independence | Main risk or limitation |
|---|---|---|---|---|
| Complete stopped-server copy | All files in the configured dedicated-server save directory | The state captured at shutdown and copy time | Independent if stored outside the live installation, preferably on another device | Requires a maintenance stop and enough storage for the complete set |
| Automatic rolling copy | One of ten numbered copies for a particular world | A recent automatic version; a new copy is made every ten minutes or on shutdown | Usually the same machine and save directory as the live world | Older copies are overwritten, and disk or installation loss can remove every copy |
| Single local client copy | One player’s client-side data | Whatever state was present when that client copy was made | Depends on where the player stores it | Does not back up the shared dedicated-server world |
| Steam Remote Storage | Client data synchronized through Steam Cloud | Depends on the synchronized cloud state | Held through Steam rather than solely on the local disk | Does not replace a complete dedicated-server copy or guarantee that every local change has synchronized |
For a world that matters, use both layers: make independent copies of the dedicated-server save directory and have each player preserve their own client-side character data. The two layers protect different kinds of progress and cannot be merged into one server-side file.
The Tool Desk
Outbyte PC Repair FREEClear out junk files and repair common Windows errorsFree Scan →Outbyte Driver Updater FREEScan for outdated or missing drivers - takes under a minuteDriver Scan →How to restore a complete server backup
A full restore replaces the destination world with the state captured in a previous backup. It is appropriate when the current save set is damaged, files were deleted, or you deliberately want to return the server to an earlier dated state.
- Stop the destination server. Ask players to leave, shut down the dedicated-server process cleanly and confirm that it has exited.
- Preserve the current state. Copy the destination server’s current save directory to a separate safety folder before replacing anything. This gives you a way to reverse the restore if the selected backup is not the one you wanted.
- Confirm the destination path. Open the destination
enshrouded_server.jsonand readsaveDirectory. Make sure you are working on the directory used by this server instance, not an old installation or a different server. - Prepare the backup. Select the dated backup that contains the complete world file set. Check that it includes the world files, numbered rolling copies,
_infofiles and-indexfiles. Do not mix files from different backup dates. - Replace the destination contents. Remove or move the destination save contents into the safety folder, then copy the backed-up contents into the configured save directory. Preserve every original filename and accompanying file.
- Start the server. Launch the dedicated server normally and wait for it to load the restored world.
- Verify shared progress. Check the world, bases, quests and other shared progress. Have a player join if possible so you can confirm that the restored state is visible to clients.
- Keep the safety copy until verification is finished. Do not delete the pre-restore copy immediately. Once the restored world is confirmed, retain it according to your own retention policy rather than discarding it during the same maintenance window.
A full server restore changes the shared world state. It does not automatically reconstruct a player’s character progression if that client data was lost separately. Players should restore their own client data only from a known-good client backup and should avoid overwriting it casually while the server state is being checked.
Rank #3
- Easily store and access 4TB of content on the go with the Seagate Portable Drive, a USB external hard drive.Specific uses: Personal
- Designed to work with Windows or Mac computers, this external hard drive makes backup a snap just drag and drop
- To get set up, connect the portable hard drive to a computer for automatic recognition no software required
- This USB drive provides plug and play simplicity with the included 18 inch USB 3.0 cable
- The available storage capacity may vary.
How to roll back a damaged world with the ten rolling copies
Use the rolling copies when the latest world state is damaged or an unwanted change occurred recently. Keen Games documents ten numbered copies for each world. A new copy is produced every ten minutes or when the server shuts down, and the oldest is overwritten after the ten slots are filled.
- Stop the server completely. Players must leave, and the dedicated-server process must no longer be running.
- Make a full safety copy first. Copy every file in the configured save directory—including all numbered copies,
_infofiles and-indexfiles—to a separate dated folder. This is your recovery point if the rollback choice is wrong. - Identify the affected world’s
-indexfile. The index file records which numbered copy is active under thelatestvalue. - Choose a numbered copy. Select a value from
0through9based on the approximate time before the damage or unwanted change. The numbering is the available rollback selector; it is not a promise that every slot represents a precise, user-visible timestamp. - Edit only the active-copy value. In the relevant
-indexfile, changelatestto the selected number. Keep the file’s structure and all other values unchanged. - Save the index file and restart. Start the server and allow it to load the world using the selected rolling copy.
- Inspect the result before making further changes. Check bases, quests, inventory-related world effects and other shared progress. If the result is not suitable, stop the server and use the preserved full backup to restore the pre-edit state before trying a different number.
Do not delete the other numbered files after selecting one, and do not copy only the selected file into a new directory. The index and accompanying files are part of the save set. Editing the index without first making a complete copy removes your easiest route back if the selected copy is also damaged.
Backing up each player’s character progression
Because character progression is stored only on clients, a server operator cannot protect every player’s character by copying the dedicated-server folder. Each player should make their own client-side backup.
- Exit the game normally. Close the client after saving so that the local files are not being written while they are copied.
- Locate the local data. On Windows, inspect
%USERPROFILE%/Saved Games/for the Enshrouded client save data. - Copy the relevant client save data. Preserve the complete applicable folder and its structure in a dated location separate from the live client files.
- Consider Steam Cloud separately. Steam Cloud files are accessed through Steam Remote Storage. Cloud synchronization is an additional location, not a reason to omit a local copy.
- Record the date and context. Note which character and game state the copy represents, especially before restoring a server world or changing client files.
A client backup and a server backup may have different timestamps. If a world is restored to an earlier point, a character saved after that point may no longer match the shared world. Keep the two backup layers clearly labeled so you can choose compatible dates rather than overwriting a character blindly.
Rank #4
- 【Upgraded version】 - The mirror logo strip is combined with the striped non-slip design. The rounded corners of the shell are more suitable for holding. The strips play a heat dissipation function to ensure a stable and fast transmission process.
- 【Ultra-thin and quiet】 - The motherboard adopts JMicron 578 noise-free solution, giving you a quiet working environment. Lightweight and portable size designed to fit in your pocket for easy portability.
- 【Ultra-Fast Data Transfers】 - Pairing this external hard drive with JMicron 578 solution USB 3.0 and USB 2.0 interfaces enables blazing-fast data transfer. It boasts theoretical read speeds of up to 125MB/s and write speeds of up to 103MB/s.
- 【Plug and Play】 - With no software to install, just plug it in and the drive is ready to use.The hard disk chip is wrapped with an aluminum anti-interference layer to increase heat dissipation and protect data.
- 【What You Get】 - 1 x Portable Hard Drive, 1 x USB 3.0 Cable, 1 x User Manual, Gift-type shell packaging ,Three-year manufacturer's warranty and free technical support services.
Verification checklist after a backup or restore
- Path: The copied files came from the
saveDirectoryactually used by the running server. - Completeness: The copy includes the full world file set, numbered rolling copies,
_infofiles and-indexfiles. - Isolation: The dated copy is outside the live installation, with an additional copy on an independent destination when possible.
- Version record: The dedicated-server version and backup date are written down.
- Clean shutdown: The server process had exited before files were copied or edited.
- Load test: The server restarted and loaded the expected world after the backup.
- World check: Bases, quests and shared progress match the selected backup or rollback point.
- Client check: Players understand that their character files require separate protection.
Troubleshooting common backup and restore mistakes
The restored world looks unchanged
Stop the server again and verify saveDirectory in the destination enshrouded_server.json. A server can be pointed at a different folder than the one you replaced. Also check that the complete backup contents, rather than a nested folder accidentally copied one level too deep, occupy the configured directory. Keep the safety copy until the correct path is confirmed.
The server will not load after an index edit
Stop the process and restore the complete save directory from the safety copy made before editing. The rollback procedure requires a value from 0 through 9 in the affected world’s -index file; changing unrelated text or omitting accompanying files can leave the save set inconsistent. Once the pre-edit state loads, make another full copy before testing a different numbered value.
Recent player actions are missing
That is expected when you restore an older dated backup or select an earlier rolling copy. The point of rollback is to return the shared world to an earlier recovery point. Explain the selected date to players before they reconnect and make new changes.
A player’s character is missing progress even though the world is correct
The server backup does not contain character progression. Have that player check their own client backup under %USERPROFILE%/Saved Games/ or their Steam Remote Storage data. Do not infer that a successful world restore also restored client-only data.
Best Value
- High capacity in a small enclosure – The small, lightweight design offers up to 6TB* capacity, making WD Elements portable hard drives the ideal companion for consumers on the go.
- Plug-and-play expandability
- Vast capacities up to 6TB[1] to store your photos, videos, music, important documents and more
- SuperSpeed USB 3.2 Gen 1 (5Gbps)
The backup was copied while the server was running
Treat it as suspect rather than deleting the live files. Stop the server cleanly, make a new complete copy, and retain the earlier copy only as a possible reference. A live copy may capture files at different points in time and is not the controlled recovery point produced by the documented procedure.
The expected rolling copy is no longer available
Only ten numbered copies are retained for each world, and new copies overwrite the oldest. If the needed state has already rotated out, use the most suitable dated independent backup instead. This is why rolling copies should be treated as a short-term rollback mechanism, not long-term archival storage.
A practical maintenance routine
Use the automatic saves and rolling copies for short recovery windows, then create independent dated copies before major changes or on a schedule appropriate to the server’s activity. At minimum, make a complete stopped-server copy before editing configuration, replacing save files, testing a rollback or applying any operation that could alter the world. Keep more than one recovery point when the world is active enough that a single damaged backup might not be noticed immediately.
Label every archive with the server or world name, date, dedicated-server version and whether it is a full copy or a client-character copy. Store the two data classes separately: the server archive is for shared world recovery, while each player’s archive is for that player’s character. Periodically test that an archive can be opened and that its contents include the expected supporting files; a backup that cannot be identified or restored is not useful during an outage.
Quick Recap
Quick recovery decision guide
- You need the latest known-good independent state: restore the most recent complete dated server backup.
- The latest state is damaged but the damage happened recently: stop the server, preserve a full copy, and select an appropriate numbered rolling copy through the world’s
-indexfile. - Only one player’s character is affected: investigate that player’s client data; a server-world restore is unlikely to address a client-only progression problem.
- You cannot find the files: read
saveDirectoryinenshrouded_server.jsoninstead of assuming./savegame. - You are about to edit or replace anything: first copy the entire save set, including the rolling copies and index and information files.
Product prices and availability are accurate as of the date/time indicated and are subject to change. Any price and availability information displayed on Amazon at the time of purchase will apply.
Recommended Free Tools
