Skip to content
Game save workbench
Local-first tools No installation Support status shown
SAVEEDITOR.COM
Browse tools
DEVICE-LOCAL Favorites and recent pages stay in this browser.

Save Editors

RimWorld Save Editor

Perform one deliberately narrow, documented RimWorld 1.6.x save edit locally: convert an existing commitment/permadeath save to normal reloadable mode while keeping all colony/world/gameplay XML untouched.

RimWorld PC

01 / Tool workbench

Use the runtime only when it is actually ready.

The application shell fails closed. An input interface is not enabled merely because a WordPress Tool record exists; the declared engine must be registered in the current build.

RimWorld Save Editor
BROWSER LOCAL

Checking whether the declared runtime module is loaded. No input has been processed.

Session change summary

No output has been built in this session.

What this game-specific editor changes

Perform one deliberately narrow, documented RimWorld 1.6.x save edit locally: convert an existing commitment/permadeath save to normal reloadable mode while keeping all colony/world/gameplay XML untouched.

Verified save contract

The selected file must be valid UTF-8 RimWorld XML with a savegame root, a 1.6.x gameVersion value, and a recognized permadeathMode boolean. Files are limited to 16 MiB.

Supported save family

RimWorld PC 1.6.x XML saves containing permadeathMode metadata.

Deliberate limitations

The editor can turn True into False and removes the associated permadeathModeUniqueName element when present. It intentionally cannot enable commitment mode, fabricate unique-name metadata, edit pawns/items/research, repair mod incompatibilities, or rewrite arbitrary XML paths.

Safe workflow

Back up the .rws file, select it locally, confirm the game version and current commitment/permadeath state, choose Disabled/false only when converting a permadeath save, and download the edited copy. Keep the original save until the converted copy loads correctly with the same game/DLC/mod configuration.

Why SaveEditor fails closed

The Tool must match its exact bundled game profile before the workbench will launch. The original selected bytes are preserved, edits occur on an in-memory copy, and the generated output must pass the same profile/version validation after writing.

Verification basis

Verified with 1.6.4633 and 1.6.4518 XML fixtures, version/root/boolean fingerprinting, one-way conversion enforcement, exact removal of permadeathModeUniqueName, wrong-extension/old-version rejection, original-byte preservation, and post-write reopen validation. The RimWorld Wiki documents XML save files and the manual permadeath-to-normal conversion procedure.

02 / Compatibility

Know the supported input before opening a file.

Compatibility fields are intentionally explicit. Missing values stay unclaimed rather than being filled with generic assumptions.

Accepted extensions

.rws

Platforms

PC

Supported versions / editions

RimWorld PC 1.6.x XML saves containing permadeathMode metadata.

Input constraints

The selected file must be valid UTF-8 RimWorld XML with a savegame root, a 1.6.x gameVersion value, and a recognized permadeathMode boolean. Files are limited to 16 MiB.

Known limitations

The editor can turn True into False and removes the associated permadeathModeUniqueName element when present. It intentionally cannot enable commitment mode, fabricate unique-name metadata, edit pawns/items/research, repair mod incompatibilities, or rewrite arbitrary XML paths.

Output / result

A separate .rws copy with permadeathMode set to False and the documented unique-name metadata removed when converting from permadeath. Normal saves can be inspected without changing them.

03 / Instructions

Use a reversible workflow.

File-oriented workflows start with an untouched original. Tool-specific instructions add only details documented for this utility.

  1. 01Keep the original

    Preserve an untouched copy before creating or transforming binary output.

  2. 02Confirm scope

    Match the file size, format, platform, and version to the support information on this page.

  3. 03Process locally

    Use the runtime only when the page reports that its declared engine is loaded.

  4. 04Validate output

    Compare or test the result before replacing any working source file.

Tool-specific steps

Back up the .rws file, select it locally, confirm the game version and current commitment/permadeath state, choose Disabled/false only when converting a permadeath save, and download the edited copy. Keep the original save until the converted copy loads correctly with the same game/DLC/mod configuration.

04 / Privacy and processing

The processing mode is part of the product contract.

SaveEditor.com should state local processing only when the implementation truly keeps file contents in the browser. Server or hybrid processing must be disclosed just as clearly.

Declared mode

Browser local

Runtime state

Operational

Tool-specific privacy notes

The selected save is read only after explicit file selection and processed entirely in the browser. Phase 26 profile scripts contain no fetch, XMLHttpRequest, WebSocket, or sendBeacon calls. The original bytes remain untouched; successful edits generate a separate downloadable copy after profile/version validation and post-write revalidation.

05 / Troubleshooting

When a file is rejected, do not force it.

A rejection can indicate an unsupported size, format, version, platform, or byte sequence. Preserve the original and correct the input instead of bypassing validation.

Wrong file or size

Re-check the documented input type and browser size limit before retrying.

Unsupported format

A generic converter does not imply support for every game-specific container, signing scheme, or serialization format.

Source was modified

Return to the untouched source instead of repeatedly processing a damaged or partially transformed file.

Known Tool issues

If the file is rejected, confirm it is a RimWorld 1.6.x .rws save and not another XML file. This Tool does not solve missing-mod or cross-version compatibility problems. Enabling commitment mode is blocked because the required unique-name metadata is not generated generically.

06 / Verification

Support claims should be traceable.

The verification date, method notes, and public references are kept separate from marketing language so compatibility can be reviewed over time.

Last verified2026-08-08
Profilerimworld-pc-xml-permadeath-v1

Method notes

Verified with 1.6.4633 and 1.6.4518 XML fixtures, version/root/boolean fingerprinting, one-way conversion enforcement, exact removal of permadeathModeUniqueName, wrong-extension/old-version rejection, original-byte preservation, and post-write reopen validation. The RimWorld Wiki documents XML save files and the manual permadeath-to-normal conversion procedure.

Public references

  1. https://rimworldwiki.com/wiki/Save_file
  2. https://rimworldwiki.com/wiki/Permadeath_save_conversion_guide
  3. https://rimworldwiki.com/wiki/Version_history

07 / FAQ

Questions to answer before editing.

These answers are generated from the Tool record and current runtime state rather than generic compatibility promises.

Is RimWorld Save Editor ready to use?
The Tool record is verified and declares an operational runtime. The page enables its input controls only when the declared engine module is loaded in the current build.
Does processing stay in the browser?
Yes for this declared mode. The loaded runtime processes the explicit input in the browser; Tool-specific privacy notes describe the exact scope and limits.
Should I keep the original file?
Yes. Keep an untouched source file until any generated output has been validated.
What if my version is not listed?
Treat unlisted versions as unverified. Do not assume two releases use identical save layouts, checksums, signing, or serialization.

Related tools

Continue with the same tool family.

Only index-ready verified records from the same Tool Family are shown here.