JSON Save Editor: Edit Game Saves and Save Codes

JSON content matters more than the extension

A game may store JSON in a .json, .sav, .save or .dat file. Savepoint detects JSON objects and arrays from their content. Those same extensions can also contain completely unrelated binary data, so an unfamiliar .sav file is not automatically editable.

The editor also handles supported JSON wrapped in Base64, URL encoding, Gzip, Zlib or LZ-String. Base64 is an encoding, not a universal save format: decoding it may reveal proprietary data rather than JSON. Encrypted save codes need a dedicated parser.

How to edit a JSON save

You can try the built-in demo before opening your own file. It contains sample gold, health, inventory and progress fields.

1. Back up the original save, then select your file or choose Paste code.
2. Search by a field name such as gold or by its current value.
3. Edit an existing number, string or boolean. Use the Changed filter to review the differences.
4. Download the result. For a game that imports text codes, open the downloaded text and use the game’s own import feature.

{
  "player": { "name": "Alex", "gold": 2450 },
  "progress": { "tutorialCompleted": true }
}

Keep the original data types

The number 2450 and the string "2450" are different values in JSON. Savepoint keeps the field’s original type and validates numeric edits. It does not add or delete keys, resize arrays or infer the correct values for your game.

Integers outside JavaScript’s safe range and non-finite numbers are rejected to avoid silently losing precision. Decimal values use standard JavaScript floating-point numbers. Null values and protected keys beginning with @ cannot be edited.

What changes when you export?

Without edits, downloading returns the original bytes. After an edit, the JSON is serialized again and its detected encoding layers are reapplied. Whitespace, indentation and compressed bytes can change; game-specific checksums and signatures are not recalculated.

Input and output files are limited to 10 MB, decoded content to 20 MB, and the data tree to 200,000 values and 80 levels. An error about incomplete JSON can mean a missing bracket, an incomplete copy or a file that is not JSON at all.