RimWorld makes the file format comparatively transparent—.rws saves are XML—but that does not make them context-free. A colony serializes references to the game version, DLC, mods, world objects, pawns, maps, and many definitions supplied by the active content set. SaveEditor therefore treats a proper backup as the .rws file plus environment notes. This is especially important before removing a mod or upgrading a heavily modded colony, because an XML parser succeeding does not prove that RimWorld can reconstruct every referenced definition.
Identify the exact save you intend to edit
The researched RimWorld PC save location is Windows: %USERPROFILE%AppDataLocalLowLudeon StudiosRimWorld by Ludeon StudiosSaves. Known file/folder pattern: *.rws; manual names plus Autosave-* records.. Storefront context: Steam, GOG, Epic Games Launcher. The save file is human-readable XML, but it is highly version/mod dependent. Editing XML without understanding cross-references can create a loadable-looking file that fails later. Do not edit a similarly named file from a different profile, edition, or cloud cache.
Make an untouched backup first
Back up the entire Saves folder and also record the RimWorld version, DLC set, and mod list/load order that produced an important colony. Keep that copy outside the live save directory and do not overwrite it with later experiments. Cloud context: Steam Cloud is commonly used; the official/community wiki documents platform-specific save directories. If a launcher can synchronize the save, prevent it from silently replacing either the original or edited copy while testing.
Understand the format boundary
RimWorld saves are XML-based .rws files and embed world/colony state plus references to active DLC/mod content. The game can show the save-data location from its settings UI. File-extension context: .rws Compatibility note: A .rws file can be structurally valid XML yet incompatible with a different mod set or game version. Missing definitions are a compatibility problem, not automatically file corruption. These facts help identify the save but do not automatically reveal every field, checksum, encryption rule, or version-specific structure inside it.
Use only a Tool whose claim matches the file
Generic viewers and diff tools can inspect bytes without claiming game-specific semantics. A game-specific editor should be used only when its Tool page explicitly lists RimWorld, a matching supported version/container, and a Verified operational runtime. A planned URL or Game Hub is not evidence that an editor exists.
Test the edited copy safely
Write to a new output file when the Tool supports it, keep the original backup, restore the edited copy into the correct profile/storefront location, and launch the game only after the file operation finishes. If the game rejects it, If a colony fails after an update or mod change, restore the save and matching mod environment together. Use the in-game “Show” save-data-location action when uncertain about the active folder. Return to the untouched backup before trying another change.
Verification context: Reviewed against the current RimWorld Wiki Save file documentation and current PC save-location conventions.