Enshrouded Save Editor

Enshrouded Save Editor

A free, browser-based Enshrouded save editor for character saves: items, gear, level and skill points. It runs locally in your browser — and it is a beta: saves whose layout the parser doesn’t recognize yet are reported honestly instead of being edited blindly.

Beta

Early version: character saves from Enshrouded 1.0 whose layout is recognized can be edited. World saves show structure only, and some save versions are not adapted yet — failures are reported instead of guessed at.

Expects the .ksd file your character is stored in. See where Enshrouded save files live if you can't find yours.

Export this file?

  • Exporting is experimental. The written file keeps your original file name.
  • Keep a backup of the original .ksd before you replace it — a copy is the only undo that always works.
  • Quit Enshrouded first, and consider pausing Steam Cloud sync for the game so an older cloud copy cannot overwrite your edited file.
  • Honest limit: this editor has never been verified against a real character save in-game. The file is written to the format specification and passes checksum validation, but nobody has confirmed the game accepts it yet.

Processing stays on your machine by default. The only upload is an anonymized sample — and only after a parse fails, and only if you choose it (see the privacy page).

How it works

The whole flow happens locally: this Enshrouded save editor reads the file you pick, changes the values you choose, and hands back a new .ksd. Only an optional, anonymous sample upload after a parse failure ever touches the network.

  1. Find your character save

    Each character is stored as its own .ksd file, in your Steam cloud folder or your local Enshrouded save folder.

  2. Drop it into the editor

    The file is parsed on your machine, in a background worker. World saves show their structure; character saves open for editing when the layout is recognized.

  3. Edit and download

    Change level, skills or items, then export a fresh .ksd. If your save version isn’t adapted yet, the editor says so plainly — and you can optionally send an anonymized sample to help add support.

What you can edit

Two tracks, one file. Everything the editor touches lives in your character save.

Where are your saves

Enshrouded keeps character saves in two places, depending on how you play. Steam copies them into its cloud folder under the game's app ID (1203620); local saves live in your user profile.

  • Steam cloud: C:\Program Files (x86)\Steam\userdata\<SteamID>\1203620\remote\
  • Local (1.0 and later): %USERPROFILE%\Saved Games\keen games\Enshrouded\default
  • Local (0.8 and earlier): %USERPROFILE%\Saved Games\Enshrouded\

Full Enshrouded save file location guide → Whichever folder yours lives in, copy the file somewhere safe before you touch it — is the Enshrouded save editor safe? covers the backup routine.

What the editor can and cannot change

The Enshrouded save editor has a deliberately narrow scope. It changes values that already exist inside a character save; it does not rewrite world state, unlock content, or act as a trainer.

  • Can change: character level and experience; the character name; learned skill ranks and available points; stack counts and item levels in a recognized inventory; knowledge entry counts when that block parses.
  • Cannot change: world saves (worldN.ksd) are read-only structure views; quest progress, map discovery, achievements, and world-bound recipes; server-side state on a dedicated server.
  • Partial layouts: when the inventory is only partly recognized, in-place edits work, but adding or removing records is not supported.

Two limits matter. There is no item database: a stack shows its numeric item ID, not a name or icon. And there is no “add item” flow: the beta edits values in a structure it recognizes rather than inventing new records.

Before you edit: a five-minute checklist

Most broken-save stories start before the Enshrouded save editor opens. Each item below prevents a specific, common failure.

  • Quit Enshrouded completely. The game writes its saves when it exits, so a running instance can overwrite your edited file the moment you close it.
  • Back up the whole save folder, not only the file you plan to change. Copy %USERPROFILE%\Saved Games\keen games\Enshrouded\default (1.0 and later) or the Steam userdata\<SteamID>\1203620\remote folder somewhere the game cannot reach.
  • Decide what to do about Steam Cloud. While Cloud is on, Steam may restore an older copy over your edited file. Pause Cloud sync for Enshrouded, or choose the local file when a conflict appears.
  • Confirm which character file you are editing. Character saves are character0.ksd, character1.ksd, and so on; the number is the slot, not the character’s name.
  • Check the version. This editor targets the 1.0 character layout. Older or unrecognized layouts are refused rather than guessed at.
  • Ask before taking an edited character into someone else’s world. The change is local, but the effect on a co-op session is social.

After you export: putting the file back

Export downloads a new .ksd with the same file name as the original. The editor does not write to your disk directly, so the last step is yours.

  • Keep the downloaded file and the original backup apart until you have verified the result.
  • Replace the original with the exported file, keeping the same name. If you are unsure, rename the original instead of deleting it.
  • Start Enshrouded, load the character, and check the values you changed — level, skill ranks, or a stack count is enough for a first pass.
  • If the game rejects the file or a value looks wrong, restore the backup and stop. Re-exporting over a bad file repeatedly makes it harder to tell which copy is which.

The honest limit from the export dialog still applies: this beta has not been verified against a real character save in-game. The file is written to the format specification and passes checksum validation, but no one has confirmed that the game accepts it yet. Keep the backup until you have seen the character load.

How a .ksd file is put together

A .ksd file is a container, not a flat list of values. It starts with a short header and a table of contents, followed by several data blocks. Blocks may be stored raw or compressed with zstd, and each one carries a checksum.

The Enshrouded save editor unpacks only the blocks that hold the values you are changing, leaves the others byte-for-byte identical, recomputes the affected checksums, and repacks the container. A stale checksum is the most common way a save ends up looking broken: the game reads the block, compares the checksum, and refuses the file. That is why no value can be changed without updating the checksum that covers it.

Parsing runs in a Web Worker in your browser. The file is read on your machine, and normal editing makes no network request. The only upload path is the optional sample after a parse failure, and it stays closed until you tick the consent box and press Send.

Browser editor, desktop tool, or manual edits

There is more than one way to change an Enshrouded character save, and they trade off differently.

  • Manual editing: a hex editor gives complete control and no safety net. You need to understand the container, decompress blocks, and recompute checksums yourself. One wrong offset can make the file unreadable, and nothing tells you which byte was wrong.
  • Desktop save editors: usually install a native application, often Windows-only, and some read data from the game installation to show item names and icons. They can be more capable, but they add an install step and a larger trust surface.
  • This browser editor: no install, no account, and the file stays local by default. The trade-off is deliberate: it edits only layouts it recognizes, shows item IDs instead of names, and refuses uncertain data rather than guessing.

Use a desktop tool when you need a feature this beta lacks. Use this editor for a quick local change with a clear refusal when the format is unsupported. Either way, keep a backup.

FAQ

Is the Enshrouded save editor safe to use?

Privacy-wise, yes: the editor runs entirely in your browser and your .ksd stays on your machine by default. The one exception is up to you — if a save fails to parse, you may choose to send an anonymized sample. It is an unofficial tool with no connection to Keen Games, so keep a backup copy of your save before you change anything, and expect beta-grade rough edges: save versions the parser doesn’t recognize are refused, not guessed.

Where are my Enshrouded save files?

Each character is stored as its own .ksd file. Since the 1.0 update (October 2026), local saves live in %USERPROFILE%\Saved Games\keen games\Enshrouded\default, and Steam copies saves into userdata\<SteamID>\1203620\remote\. The save file location guide lists both paths.

Do I have to quit Enshrouded before editing a save?

Yes. Enshrouded writes its save files when it exits, so a running game can overwrite your edited file the moment you close it. Quit the game completely before you edit, and consider pausing Steam Cloud sync for Enshrouded while you work so an older cloud copy cannot replace your file.

Can I take an edited character into someone else’s world?

Ask the host first. The edit happens in your own save file, but showing up in another player’s world with boosted gear or skills without a heads-up is a good way to spoil their run. If you would rather not bring the edited character to co-op, keeping a second, untouched character for multiplayer is a habit worth having.

Does this editor work with Enshrouded 1.0 saves?

It targets the 1.0 character save layout, which is what the parser has been written and tested against. Layouts from older versions, or any layout that does not match, are refused with a clear error instead of being edited speculatively. World saves can be opened to inspect their block structure, but they are not editable.

Why does the editor say it cannot read my save?

The message names the category. The file may not be a .ksd container at all, it may be truncated, its table of contents may not match a known layout, a block checksum may fail, or a compression format may be unsupported. A checksum failure usually means the file was damaged or modified by another tool, so editing is disabled to protect it. If the structure reads but the character fields do not, that layout is simply not adapted yet — the optional sample channel exists for exactly that case.

Can I add new items, or only change existing ones?

Only change values that already exist in a recognized layout. In a fully recognized inventory you can adjust stack counts and item levels. When the layout is only partly recognized, in-place edits still work, but adding or removing records is not supported. There is no item database and no create-item flow, so the editor cannot invent a record with a name, icon, or stats.

Does the editor work on Mac, Linux, or Steam Deck?

It runs in a modern browser, so editing is not tied to Windows. Finding the save file differs: the paths here are Windows paths, and on Linux or Steam Deck you will look inside the Proton prefix instead. If you can get the .ksd file into your browser, the editor can read it.