Save Viewer

Summary: Inspect, edit, restore and delete saves in the Unity Editor.

For the General and Advanced tabs, see the Setup Guide.

Open the Save Viewer

Open Tools › Gley › Save System, then select the Save Viewer tab.

The toolbar shows the active build target and its save backend. The viewer uses that platform’s settings and refreshes whenever you open the tab.

It displays local saves. Selecting Android as the active build target, for example, does not let you inspect saves on an Android device.

If the list is empty, create a save using the Quick Start example, then click Refresh.

What’s listed

Saves are grouped by slot. With the File backend, the list also includes companion files:

FilePurpose
Main saveThe current saved data.
.tmpA temporary file created while writing a save.
.bakThe previous save, kept as a backup.
.brokenA damaged save kept during recovery.

Internal slot metadata files are hidden. Older saves may appear under v2 save location; see Convert a v2 file.

Save Viewer with saves grouped by slot on the left and the selected save’s JSON on the right.
Select a save on the left to inspect its data on the right. Click any screenshot to enlarge it.

Inspect a save

Select an entry to see its formatted JSON. Encrypted saves are decrypted using the project’s current key or one of its Previous keys.

Warnings can identify Unity object references or fields that the saved serializer skips. See Choosing a serializer for help with these.

File details (optional)

Expand File details to see the saved type, data version, serializer, encryption and compression settings.

For troubleshooting, it also shows the format version, key ID, CRC checksum, and encryption and authentication values (IV and MAC), where available. Unreadable files may include a technical reason.

File details showing the saved type, data version, encryption, compression, serializer and key ID.

Scroll inside File details to see the remaining values.

File details scrolled to the format version, CRC checksum, IV and MAC.

Edit a save

Before editing: stop Play mode if you want to prevent the game from overwriting your changes. Editing remains available during Play mode, with a warning banner.

Keep the top-level "value" field and edit the data inside it. Its kind must stay the same: an object must remain an object, an array must remain an array, and so on. Invalid JSON or an invalid save structure shows an explanation and prevents saving.

  1. Select a readable save.
  2. Edit the data inside "value". For example, change coins from 100 to 250.
  3. Click Save changes and confirm, or click Revert to discard your edits.
Save JSON with coins changed from 100 to 250 inside the value field, and Save changes and Revert enabled.
Example: coins changed to 250, with the "value" structure preserved.

Saving keeps the file’s serializer, data version, type, encryption and compression settings. Encrypted saves are rewritten with the current project key, so a valid current key is required.

With the File backend, the previous main save becomes its .bak. PlayerPrefs does not keep backups.

Selecting another entry or clicking Refresh with unsaved edits asks before discarding them.

Files edited outside Save System

An unencrypted, uncompressed file edited outside Save System may still open in the Editor with a checksum warning. A build rejects that file until it is rewritten. If the JSON is valid, Save changes is already enabled: click it to fix the checksum without making another edit.

Large saves

For saves containing more than 10,000 non-whitespace characters, the JSON preview is read-only inside the window.

Read-only large save preview with the Edit in text editor button.

To edit a large save:

  1. Click Edit in text editor.
  2. Edit the temporary JSON file and save it in your text editor.
  3. Return to Unity and click Save from file.
  4. Confirm the change.
External editing session with its message and Open file, Cancel and Save from file buttons.

Open file reopens the temporary file. Cancel discards the external editing session. The temporary file is removed when the session ends.

Depending on the selected entry, Restore as current save, Convert to v3 or Save changes may also be available beside Edit in text editor. These actions restore, convert or rewrite the displayed data without editing it.

Broken or unreadable saves

When a save cannot be read, the viewer explains why:

ProblemWhat to do
Changed outside the gameAn encrypted save failed its authentication check. Restore a readable backup if one is available.
Damaged or emptyThe game cannot read the file. This includes a checksum mismatch in an encrypted or compressed save. Restore a readable backup or delete the entry.
Unknown encryption keyRestore the matching key through Advanced › Manage keys. The message identifies the missing Key ID when available.
Saved by a newer versionUpdate Save System to a version that can read the file.
Not a Save System fileCheck that you selected the intended file.

Restore backup appears for an unreadable main save when its .bak can be read. Click it and confirm to replace the main save with that backup.

Damaged main save with the Restore backup button available.

You can also select a readable companion file and click Restore as current save. The existing main save becomes its backup.

Delete saves

Select an entry and click Delete, then confirm.

Deleting a main v3 save also removes its companion files. Deleting a companion entry removes only that file. Deleting a v2 entry removes the selected v2 file.

Delete all saves (this platform) removes v3 saves and their companions from the current platform’s configured backend. It keeps files that are not Save System files.

It does not remove the separate files shown under v2 save location. Delete those individually if needed.

Toolbar

ControlWhat it does
Open save folderOpens the configured File backend folder. Disabled when the backend has no file folder.
RefreshReloads the list and the selected save’s contents.
Delete all saves (this platform)Removes the current platform’s v3 saves after confirmation.

Convert a v2 file

With the File backend, a separate v2 save location group shows recognized Save System files directly inside Application.persistentDataPath. These can include v2 files and files rewritten by the v2 compatibility API. Hover over the group to see its full path.

This group is omitted when the configured save folder is already persistentDataPath.

Select a readable v2 file, optionally edit its JSON, then click Convert to v3 and confirm.

Selected v2 save with its JSON and the Convert to v3 button.

Conversion:

  • Wraps the v2 JSON in the v3 "value" structure.
  • Uses the current serializer, encryption and compression settings.
  • Sets the data version to 1 and the recorded type to Unknown.
  • Uses the original filename without its extension as the save name.
  • Places root-level files and files from v2 save location in slot 0.

The original v2 file is kept. If a v3 save already exists at the destination, the viewer asks before replacing it; the existing destination becomes its backup.

If the filename is invalid or conversion would overwrite the source file, the viewer explains what to rename or move. Make the change, then click Refresh.

For project migration, see the v2 to v3 Upgrade Guide.

On This Page