Save Export: Check Your Version First

Revolution Idle Save Export: Check Your Version First

A Revolution Idle save string is not automatically editable JSON. The browser demo, the full game and Dilation Tree loadouts are different objects. Identify what you have before trying to decode, modify or import it. This guide does not claim that a third-party editor supports your build.

Identify the source before touching the export

Record the exact game name, platform, version and the menu that produced the string. Our homepage embeds a Revolution Idle X browser demo; that does not prove its export is compatible with the full Steam or mobile game. A string produced by the Dilation Tree loadout menu only describes a tree allocation.

What you have	What to check	What it does not prove
Export from an in-game save menu	Same build's documented import control	Cross-version or cross-platform compatibility
Full game's linked account	Account identity and current progress	That a browser demo string can be imported
Dilation Tree loadout	Branch levels and DTP budget	A backup of the entire game
Unknown copied string	Original app and menu	Any supported decoding or editing format

If you cannot establish where the string came from, keep it unchanged. Do not guess a decoder based on its appearance or rename it as a JSON file and assume the result is valid.

Preserve an untouched copy

If your version actually offers export, save the exact text in a plain text file before any experiment. Keep the original separate from a working copy. Record the version and time in the filename or a nearby note. Verify that copying did not replace characters, add formatting or omit the end of the string.

A backup needs a known restore path. Confirm that the same version provides an import control and instructions. Do not overwrite your only live save merely to test whether an unknown string works. If the game offers no separate test profile or safe restore procedure, stop the experiment at the backup stage.

Why generic Base64 steps are unreliable

Many incremental games use encoded or compressed exports, but that general pattern does not establish Revolution Idle's format. A successful decode would not establish the schema, integrity rules, account synchronization behavior or a valid re-encoding procedure. This site has not validated a round trip for your current game build.

Do not decode an unknown export, change currency values and import it without a documented, tested restore procedure for that exact build. No editable field names or universal editor compatibility are claimed here. An editor should identify the precise versions it supports and supply a reproducible restore test before it becomes a recommendation.

If your goal is moving devices

Use the save and account checklist. The full game's Options reference, checked on 2026-10-13, documents account linking, Save & exit and Clear save. It does not establish a universal save-string import procedure.

Save and close the source device, record its visible progress, and check account identity before attempting the destination. Do not assume that logging in on two devices means the newer progress has synchronized. If the destination shows an empty or older state, pause there and investigate before progressing on it or clearing the source.

If import fails

Keep the original export and capture the exact error, platform and version. Check whether the destination is the same game edition. Do not repeatedly mutate the original string, wipe local storage or clear the active save as a troubleshooting shortcut.

For tree build strings, return to the Dilation Tree guide. For progression experiments, adjust documented automation settings instead of depending on an unsupported save edit.

Failure checks and source limits

Situation	Next check	Stop condition
Export source is unknown	Exact game, platform, version and producing menu	Keep the original unchanged until its identity is established
Export exists but restore is undocumented	Same-version import instructions and a separate safe test path	Do not overwrite the only active save
Destination shows older or empty progress	Account identity and recorded source progress	Pause destination play and preserve the source
Editor accepts text but does not name your build	Supported versions and reproducible restore test	Do not treat decoding as proven compatibility
A tree code is being used as a full backup	Dilation Tree loadout scope and DTP budget	Return to tree instructions instead of clearing a save

Use the Wiki hub for the surrounding progression stage. The Options source was checked on 2026-10-13; the demo identity is also present in this site's configured embed. No full-save export/import round trip or cross-platform account recovery test has been performed for your build.

This article adapts the linked Revolution Idle Wiki Options information and adds version checks, backup precautions and local navigation. Source-derived text adaptations are shared under CC BY-SA 4.0.