Free tools Windows power users keep installed
One-click scans. No signup required.
Back up an Enshrouded dedicated server by stopping it cleanly, locating the configured saveDirectory, and copying the entire save set to a dated location outside the live installation. The documented default is ./savegame. A complete copy contains the world files, numbered rolling copies, accompanying _info files, and each world’s -index file. To restore, stop the destination server and replace its save contents with that complete set. To roll back a damaged world, preserve a full backup first, then change the world’s -index value from latest to a numbered copy from 0 through 9.
Playing with friends? Godlike.Host runs hosted Enshrouded servers from 10 data-center locations, with free DDoS protection.
The dedicated server preserves shared world progression—bases, quests, discoveries, and other world state. It does not store player character progression: Keen Games states that character progression is stored only on clients. Each player therefore needs a separate client-side backup for their own character data.
As an Amazon Associate I earn from qualifying purchases.
What an Enshrouded server backup actually protects
Enshrouded separates shared world data from individual character data. The dedicated server owns the world save, so a server archive is the right protection for the things everyone in the world sees and changes together. That includes the current world state, shared building progress, quests, and other server-side progression.
Character progression is different. Keen Games’ Dedicated Server FAQ says, “Character progression is stored only on clients.” A server backup cannot restore a player’s personal character if that client-side data is lost. Every player should preserve their own client save data in addition to the administrator’s server archive.
#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.
How often saves are written
Keen Games says save-game files are created every five minutes. That interval describes normal save creation; it is not a substitute for an administrator-controlled backup. A crash, accidental deletion, bad configuration change, or failed update can still make the latest live files unusable, so create dated copies before maintenance or file editing.
Where the files live
A dedicated server writes its world to the directory named by saveDirectory in enshrouded_server.json. The documented default is ./savegame. Do not assume that default is active: a host, administrator, or previous migration may have changed it.
Quick wins for a faster PC:
Scan for outdated or missing drivers - takes under a minuteDriver Scan →Repair Windows errors before they cause bigger problemsFix Now →Local, non-dedicated saves are stored under %USERPROFILE%/Saved Games/. Steam Cloud saves are accessed through Steam Remote Storage rather than the dedicated server’s save directory. These are separate storage locations and should be handled as separate backup jobs.
Choose the right backup scope
Before copying anything, decide which data you need to protect. The following distinction prevents a common mistake: taking a small local or cloud copy when the goal is to protect a complete dedicated-server world, or assuming that a server archive includes a player’s character.
| Backup source | What it covers | Where recovery data is found | Best use |
|---|---|---|---|
| Dedicated-server save set | Shared world progression | The configured saveDirectory, default ./savegame |
Protecting and restoring a multiplayer world |
| Local save | A local world and its local progression | %USERPROFILE%/Saved Games/ |
Protecting a single player’s local save |
| Steam Cloud save | The world data synchronized to Steam Cloud | Steam Remote Storage | Recovering a cloud-synchronized save |
| Client character data | One player’s character progression | That player’s client storage | Protecting personal progression separately from the server world |
For a dedicated server, copy the complete directory rather than selecting one file. The world’s supporting files determine which copy is active and provide the rolling recovery points.
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.
Before you make a backup
A backup made while the server is writing can capture an inconsistent mixture of files. Use a short maintenance window and follow this order:
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 →- Tell players to leave the world. Ask everyone to disconnect so no one is changing the world while you shut it down.
- Stop the dedicated-server process cleanly. Use the normal shutdown method for the process you launched, then confirm that it has exited. Do not start copying while the server is still running.
- Open
enshrouded_server.json. Record the exact value ofsaveDirectory. If the property is absent or still at its documented default, the live directory is./savegamerelative to the server installation. - Record identification details. Write down the server version and the backup date. This gives you a reference when deciding which archive to restore after an update or configuration change.
Keep the server stopped until the copy has completed. If you discover that the configured directory is somewhere other than the location you expected, use the configured path; copying an unused folder creates a reassuring but useless archive.
Step-by-step: back up a dedicated server
- Create a dated destination outside the live installation. Use a folder name that identifies the world, server version, and date, such as
Enshrouded-World-2026-10-15-vX. The exact naming convention is up to you; the important properties are that it is dated, identifiable, and not inside the directory the server uses as its live save location. - Copy the entire configured save directory. Include every world file, all numbered rolling copies, every accompanying
_infofile, and every world-indexfile. Preserve filenames and the directory structure. Do not copy only the newest-looking file. - Make an independent second copy. Keep another copy on an external hard drive or another destination that is independent of the server machine. This follows Keen Games’ recommendation to copy all save files before making changes; Keen does not prescribe a particular storage brand or capacity.
- Keep the original live files untouched. The dated archive is your recovery source. Do not edit its index or delete files while you are still deciding whether the backup is valid.
- Restart the server and verify the world. Start the dedicated server normally, join the world, and confirm that the expected world, bases, quests, and shared progress load. A successful copy operation is not enough if the wrong directory was archived.
What must be in the archive
- The complete world file set.
- The numbered rolling copies maintained for each world.
- Each matching
_infofile. - Each matching
-indexfile, including the value that identifies the active copy.
Missing one of these supporting files can make a restore ambiguous or prevent the server from selecting the intended world state. Treat the save directory as one unit.
How to organize backups for practical recovery
A useful routine separates the live server from the recovery copies. Keep the most recent clean archive readily available for ordinary mistakes, and retain older dated archives for cases where damage is discovered later. The server’s own rolling copies provide short-term rollback points, while your dated archives protect against deleting or overwriting the complete save set.
Use independent storage
If every copy is on the same disk as the server installation, a disk failure or accidental deletion can remove both the live world and its backup. An external drive or another independent destination gives you a separate failure boundary. Maintain the original archive until you have started the server from a restored copy and verified the result.
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.
Record enough context to identify a restore point
At minimum, label each archive with the date and server version. If you operate more than one world, include the world identity as well. This avoids restoring a valid save set to the wrong destination and makes it possible to relate a problem to a particular update or maintenance session.
Restore a complete world from a backup
Use a full restore when the live save set is missing, corrupted, or you intentionally want to return the world to the state captured in a dated archive. A restore replaces the destination’s current files, so preserve the current state first in case you need to reverse the operation.
- Stop the destination server. Confirm that the dedicated-server process has exited before touching its files.
- Make a safety copy of the current destination. Copy the destination’s current
savegamefolder, or the folder named by its configuredsaveDirectory, to a separate location. Keep this copy until the restored world has been checked. - Confirm the destination path. Open the destination server’s
enshrouded_server.jsonand verify the activesaveDirectory. The destination may not use the documented default. - Clear or move the destination save contents. Move the existing contents aside rather than permanently deleting them while the restore is being tested.
- Copy the complete backed-up world set into the destination. Preserve every filename and include the world files, numbered copies,
_infofiles, and-indexfiles. Do not mix files from different dates or worlds. - Start the server. Allow it to load the restored set normally.
- Verify shared progress in the game. Check the world identity, bases, quests, and other shared progress. Have a player connect if possible so you can confirm that the restored world is the intended one.
- Retain the safety copy until verification is complete. Delete or archive it only after you are satisfied that the restore succeeded.
If the restored world is not the expected one
Stop before making more changes. Recheck the destination saveDirectory, confirm that the copied files came from one dated archive, and verify that the accompanying -index file was included. If necessary, restore the safety copy you made in step two and reassess the source archive.
Roll back a damaged world with the rolling copies
Each world save has ten numbered rolling copies for backup and rollback. Keen Games documents that a new rolling copy is created every ten minutes or when the server shuts down, and the oldest copy is overwritten as the set cycles. The world’s accompanying -index file records which copy is active under the key latest.
Rollback is an index edit, not a replacement of the entire world directory. Because an incorrect edit can make recovery harder, create a full copy of all save files before changing anything.
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.
- Stop the server cleanly. Ensure no process is writing to the save directory.
- Copy the complete save set to a safe, dated location. Include the current
-index, all world files, numbered copies, and_infofiles. - Open the relevant world’s
-indexfile in a plain-text editor. Locate thelatestvalue. - Replace
latestwith the number of the copy you want to activate. Valid rolling-copy values are0through9. Choose a copy from before the damage or unwanted change. - Save the index without changing filenames or unrelated entries.
- Start the server and inspect the world. Confirm the world, bases, quests, and shared progress before allowing normal play to resume.
- Keep the pre-edit full backup. If the selected copy is not suitable, stop the server and use the preserved files to try another numbered value or return to the original state.
Choosing a rolling copy
The numbered copies represent recent recovery points, not permanent historical archives. Because the set is continuously overwritten, select the copy based on when the damage occurred and preserve a full dated archive before experimenting. If the unwanted change is older than the available rolling copies, use a dated full backup instead.
Server world data versus character data
A successful world restore does not necessarily return a player’s character to an earlier state. The server stores the shared world; character progression remains on each client. A player who needs protection for skills, inventory, equipment, or other personal progression must preserve the relevant client-side data separately from the server administrator’s world archive.
Do these 3 things before closing this tab:
1Fix the driver behind crashes, sound loss and screen glitches2Clear out junk files and repair common Windows errors3Scan for outdated or missing drivers - takes under a minuteFor local worlds, the relevant save location is under %USERPROFILE%/Saved Games/. For Steam Cloud data, use Steam Remote Storage. Coordinate with every player before a major rollback so they understand that the world may move backward while their client-side character data is handled separately.
Backup and restore checklist
Before copying
- Players have left the world.
- The dedicated-server process is stopped and confirmed exited.
enshrouded_server.jsonhas been checked.- The actual
saveDirectoryis recorded. - The server version and date are written down.
During the copy
- The entire save directory is copied outside the live installation.
- World files, numbered copies,
_infofiles, and-indexfiles are present. - The archive is dated and clearly identified.
- An independent second copy is created.
After restarting
- The expected world loads.
- Bases and shared progress are present.
- Quests and other world state are checked.
- The recovery archive is retained until verification is complete.
Common mistakes and their fixes
Copying the default folder without checking the configuration
Symptom: The archive exists, but restoring it does not change the live world. Fix: Check enshrouded_server.json and copy the directory named by saveDirectory. The documented default is only a starting point.
Copying while the server is running
Symptom: A restore behaves unpredictably or does not represent one consistent point in time. Fix: Ask players to leave, stop the process cleanly, confirm it has exited, and repeat the copy.
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)
Saving only one apparent world file
Symptom: The server cannot select the intended state after files are replaced. Fix: Restore the complete set, including numbered copies, _info files, and the -index file.
Recommended Free Tools
Expecting a server archive to restore a character
Symptom: The shared world is correct, but a player’s personal progression is not the version they expected. Fix: Restore the player’s client-side data separately; character progression is not stored on the dedicated server.
Editing the index without a safety copy
Symptom: A rollback attempt leaves no easy way to return to the previous state. Fix: Stop the server and make a complete copy of all save files before changing latest.
Which recovery method should you use?
| Situation | Use | Reason |
|---|---|---|
| You want routine protection before maintenance | Dated full save-set archive | It preserves the complete world file set outside the live installation. |
| A recent change damaged the world | One of the numbered rolling copies | The -index file can select a recent copy numbered 0 through 9. |
| The live directory was deleted or replaced | Full restore from a dated archive | A complete archive restores the world files and their supporting metadata together. |
| A player lost personal progression | That player’s client-side backup | Character progression is stored on clients, not on the dedicated server. |
| You need a local or cloud world | Local save or Steam Remote Storage | Those worlds are stored separately from the dedicated-server saveDirectory. |
Final operating routine
For a reliable Enshrouded server, make the clean shutdown and full-directory copy routine part of every maintenance window. Verify the configured path instead of assuming ./savegame, preserve all supporting files, keep an independent copy, and test that the world loads after restarting. Use the rolling-copy index only after preserving a full backup, and remind players that their characters require separate client-side protection.
Quick Recap
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.
What’s actually slowing this PC down?
Pick the symptom - the matching free tool is one click away.
