Will Enshrouded 1.0 Wipe Your Save? What Server Owners Need to Know

In the run-up to October 15, the loudest question in the Enshrouded community is not what ships with 1.0. It is whether the world you have been building since Early Access survives it.

Keen Games has answered it: no wipe. Community manager Toast confirmed on August 27 that 1.0 brings a new save system and that existing saves migrate to it automatically, so you pick up where you left off. Two things can still ruin launch night on a dedicated server, and a ten minute routine covers both.

What Keen Games has actually committed to

The date has been locked since June 25: Enshrouded leaves Early Access on October 15, 2026 on Steam, and the PS5 version launches the same day. Here is what Keen has said since.

• Saves carry over. Asked whether a current save will work with 1.0, Keen's Community Lead answered yes in June. On August 27 community manager Toast added that 1.0 brings a new save system and migrates existing saves to it automatically.
• The August 27 update focused on improvements to systems already in the game, plus a behind-the-scenes look at performance work aimed at lower and mid-range hardware.
• Press coverage in August confirmed the game's hardest boss fight is being redesigned after community complaints, along with an alternative player model.
• The price rose to 39.99 EUR on September 8, which Keen had flagged in its Early Access FAQ from the start.

Enshrouded also never forced a save wipe in almost 33 months of Early Access. Update 8, Forging the Path, landed in April 2026 and existing worlds carried straight over.

So your save should load on October 15, and that is Keen's word, not a guess. One caution of our own, not Keen's: a save migration usually runs one way, so a world converted by 1.0 probably cannot be opened by the Early Access build again. Keep the pre-1.0 copy.

What 1.0 means for an Early Access world

Keen says existing worlds receive each update, so 1.0 content reaches an Early Access world too. The catch, according to Keen, is that you will not notice changes in areas you never go back to. The skill tree also resets again in 1.0, so every character re-spends their points.

Enshrouded's map is hand-crafted, not procedurally generated, so a long-running world is not locked out of the new content. What Keen has not addressed is how a reworked area behaves where your players have dug or built. The release changelog on October 15 is the first place to look.

The file most likely to break your server on patch day

A wiped world is the fear. A dead config is the likelier reality.

Enshrouded's server settings live in enshrouded_server.json, which is nested JSON rather than the flat key and value file most games use. It carries a gameSettings block, your userGroups and passwords, the slot count, and server tags. Major versions add settings, rename them, and change what counts as a valid value.

The failure mode is unpleasant. On our servers, a single invalid value stops the Enshrouded server before it boots, with nothing useful on screen. We reproduced this on a test server on August 3: one setting changed to a value the game did not accept, six polls later still offline, no error we could find. Keen's documentation says the server names the rejected value in its output, but our startup script clears logs/enshrouded_server.log every time the server starts, so the next restart erases whatever the failed boot wrote.

So if your server refuses to boot on October 15, suspect the config before you suspect the save. Keep a copy of the working enshrouded_server.json before the patch. Paste your file into our free Enshrouded server settings generator to find any value the game would reject before you restart. If the server still dies afterwards, let it write a fresh default config and reapply your settings on top of it.

The ten minute backup routine

Do this on October 14, not on launch day.

1. Stop the server first, and wait until the panel shows it offline. A running server keeps writing to its save, so files copied out of it can be half written or out of date.
2. Download the whole savegame folder. A dedicated server only ever loads slot 1, named 3ad85aea, alongside 3ad85aea-index, 3ad85aea_info and 3ad85aea_info-index. The large file with no extension is the world itself. The step by step version is in our guide on how to upload a world to your Enshrouded server.
3. Copy enshrouded_server.json into the same folder. Ten seconds now, a rebuilt config later.
4. Label it with the date and version, something like pre-1-0-oct-14. Launch week is exactly when an unlabelled backup folder becomes useless.
5. Leave yourself memory headroom. Version launches raise the floor. Budget roughly 0.16 GB per player on top of your base allocation, and 2 to 3 GB for a large, heavily explored world.

Restoring is the same path in reverse: stop the server, upload the files, then delete the -index file so the server rebuilds it against your world.

Fresh world or carry the old one over?

Once the backup exists, this becomes a preference rather than a gamble.

Carry it over if the server is a long-running community with real builds on it. Months of architecture and a shared map are worth more than a clean slate, and Keen says existing worlds get the 1.0 changes too. You just have to travel back to the old areas to see them.

Start fresh if your group is specifically coming back for 1.0. You meet the new content in the order Keen built it: the reworked boss fight, the new biome and the higher level cap. Keen has suggested trying 1.0 with a fresh character for the same reason.

You are not strictly forced to choose. A dedicated server loads slot 1 only, but nothing stops you archiving the Early Access world and dropping it back in later, or running a second server for a month while the group makes up its mind.

The short version

Keen has confirmed there is no wipe: saves migrate to the 1.0 save system automatically. The two things that can still ruin launch day are a world nobody backed up and a config that kills the boot. Ten minutes on October 14 covers both.

If you are spinning up a server for 1.0, a DoomHosting Enshrouded server deploys in minutes on Ryzen 9 hardware, with full FTP access for the backup routine above, DDoS protection for launch week, and support that is awake when October 15 lands.