JSON Save Editor
- .json
- any JSON-based save
Edit JSON save files online. Works with .json saves and with any save that is JSON underneath, whatever its extension — a huge share of indie, HTML5 and Unity games.
A surprising number of games store progress as plain JSON, whatever the file is called. Upload the save and edit it as a searchable tree instead of hunting through raw text — and if the extension is unfamiliar, upload it anyway: the format is detected from the contents.
How to edit a JSON save
- Upload the save file — .json, or any file you suspect is JSON underneath.
- Search for the value you want to change; searching the current number is the fastest route.
- Edit it in the tree, keeping the original type.
- Download the file and put it back under its original name.
What you can change
- Any numeric value — currency, levels, counters, timers
- Booleans that gate content, such as unlock and completion flags
- Strings, including names and chosen options
- Whole objects and arrays, for saves that store inventory as a list
Where the saves are stored
There is no single location — it depends on the engine. Desktop games often keep saves next to the executable or in the user application-data folder; browser games often keep them in local storage, where you need an in-game export to get a file at all.
What the format actually is
JSON is text, so there is nothing to decode: the structure you see in the editor is exactly the structure the game wrote. That also makes it the most forgiving format to edit, as long as you keep types intact — a number stays a number, a boolean stays true or false.
Related guide: Which games and engines does Save Editor support?
Questions
My save has a different extension — will it open?
Upload it anyway. Detection reads the file contents, not the extension, so a .dat, .sav or extensionless file that is really JSON opens like any other JSON save.
How do I know my game uses JSON?
A lot of them, yes. Web and HTML5 games, Unity games using JSON serialization and most indie engines store progress as JSON, sometimes without compression or obfuscation of any kind.
What happens if the file is not JSON after all?
The upload is logged and the file is kept for analysis, which is how formats get prioritized. Uploading an unsupported save is a vote for its parser, not a dead end.