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

Three weeks out from 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 not answered it. That silence has turned into a lot of confident guessing in Discord threads, so here is the grounded version: what the studio has actually committed to, where the real risk to a dedicated server sits (it is not deletion), and the ten minute routine that makes the whole question stop mattering.

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. Everything since has been build-up rather than detail.

• 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.

What is missing from every one of those posts is any mention of a wipe, a save migration, or a required world reset. That is not a small omission. Keen has been specific about server impact before: the Hotfix #42 changelog in June went out of its way to note that dedicated servers did not need an update.

Enshrouded has also never forced a save wipe in nearly two years of Early Access. Update 8, Forging the Path, landed in April 2026 and existing worlds carried straight over.

So the reasonable expectation is that your save loads on October 15. Betting a community server on a reasonable expectation is a different proposition.

The real risk is terrain, not deletion

Here is the part that gets lost when people argue about wipes. Enshrouded keeps an explored, player-modified voxel world in its save. Terrain your server has already generated is baked in. World generation only runs on chunks nobody has visited yet.

So if 1.0 ships new biomes, reworked generation, or new points of interest, those changes land only in the parts of the map your server has never touched. On a world that has been running since Early Access, that can be most of the interesting ground.

The practical symptoms on a long-lived world:

• New locations simply do not appear in regions you explored months ago.
• Visible seams where old generation meets new.
• New dungeons or bosses missing from your map while everyone else posts screenshots of them.

This is the same pattern Valheim, Vintage Story and Minecraft all hit at major version bumps. Nobody wipes you. You quietly receive less of the update than a player who started fresh that morning.

How much of the map 1.0 actually touches is still unknown outside Keen. The highlights video and the release changelog in October are what will settle it.

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 genuinely unpleasant. A single invalid value makes the Enshrouded server exit instantly and write nothing at all. We confirmed 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 anywhere. Because the server clears its previous log on startup, there is no log file to read either.

So if your server refuses to boot on October 15 with no output, suspect the config before you suspect the save. Keep a copy of the working enshrouded_server.json before the patch. If the server dies silently afterwards, let it write a fresh default config and reapply your settings on top, rather than hunting for an error message that was never written.

The ten minute backup routine

Do this on October 14, not on launch day.

1. Stop the server first. Enshrouded writes its save on shutdown. Copying files out of a running server gets you a stale snapshot that the server overwrites minutes later.
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 seeing every new point of interest, and you can always explore outward into fresh terrain for the new content.

Start fresh if your group is specifically coming back for 1.0. You get the complete update: the reworked boss fight, the new generation, all of it in the map rather than only the parts nobody walked through last year.

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

No wipe has been announced, and Enshrouded's own history says one is unlikely. The two things that actually ruin a launch day are a world nobody backed up and a config that kills the boot with no error to read. 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.