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.

File Analysis

RimWorld Cloud Copy Identity Comparator

Compare two user-selected RimWorld save copies after both pass the existing verified parser; report identity and bounded parsed divergence without choosing a winner.

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 Cloud Copy Identity Comparator
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.

Read-only Phase 68 boundary

This Tool analyzes user-selected local copies or exports after existing strict parsers accept the bytes. Cloud/mobile labels describe the role selected by the user and are not proof of origin.

No synchronization authority

SaveEditor does not access accounts, choose a conflict winner, determine which copy is newer, bypass DRM, or guarantee cross-storefront/mobile compatibility.

Output

Only deterministic SHA-256-bound analysis metadata is exported; source save bytes are never embedded.

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

Only the exact save family already accepted by rimworld-pc-xml-permadeath-v1. Phase 68 does not expand source-parser versions or storefront/mobile variants.

Input constraints

Two local user-selected files that satisfy the already-verified rimworld-pc-xml-permadeath-v1 parser. Role labels such as cloud/mobile are user claims, not proven origins. Permanent 16 MiB per-file ceiling.

Known limitations

Read-only local analysis only. No account-cloud access, synchronization, conflict-winner selection, cross-storefront guarantee, mobile-origin proof, DRM bypass, repair, migration or conversion authority.

Output / result

Deterministic SHA-256-bound JSON report. No source or altered save bytes are emitted.

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

Select local copies/exported files manually. SaveEditor validates each selected file with the existing verified parser before comparing hashes, parser versions and the bounded fields named by this Tool.

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

Phase 68 processes selected files only in the browser. It does not log into Steam, Xbox, Apple, Google or any other cloud account and does not upload the selected save bytes.

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

A refusal means a selected file did not satisfy the existing verified source parser. A successful parse does not prove that the file came from the cloud/mobile location claimed by the user or that another storefront/device will accept it.

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-11
Profilerimworld-cloud-copy-identity-comparator

Method notes

Verified by strict existing parser reuse, pair/source immutability, SHA-256 identities, deterministic selected-field comparison, malformed-input negatives, independent fixture comparison and full source/installable parity.

Public references

  1. https://saveeditor.com/games/rimworld/

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 Cloud Copy Identity Comparator 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.