Drop a save file here

.bin, .sav, .dat, .json… or browse your files

Your file is decoded on this device. Nothing is uploaded.

No save file handy?

A free save decoder that runs entirely in your browser. Drop in a game save (.bin, .sav, .dat or .json) and it works out how the file is packed: MessagePack binary JSON, compressed with GZip or zlib, Base64 or hex encoded, XOR scrambled, or JSON inside a binary wrapper. It then shows everything inside, like gold, gems, levels, items and unlocks, as a searchable list, or the whole save as readable JSON you can export. You can also change values and download a re-packed copy, though games that protect their saves with a checksum will reject edited files (the decoder warns you when it spots one).

  1. Drop the file onto the box above, or click it to browse. The detected format (for example MessagePack or GZip → JSON) is shown at the top.
  2. Find a value with the search box, or use Show to list only numbers, booleans or strings.
  3. Read the whole save in the JSON tab, or press Export JSON to download a readable copy.
  4. Optional, edit it: change values in the list, then Download file. Back up the original first: checksum-protected saves won't load once edited.

How do I see what's inside a .bin save file?

Drop the .bin file onto the Save File Decoder page. It detects how the save is packed (MessagePack, JSON, GZip, Base64, XOR…) and lists every value with its full path, which you can search and filter. The JSON tab shows the whole save as readable JSON.

Can I convert a .bin save file to JSON?

Yes. Once the save is opened, press Export JSON to download a readable .json copy, or use the JSON tab to read the whole file as JSON.

Is my save file uploaded anywhere?

No. The decoder runs entirely in your browser with JavaScript. The file is read and decoded on your own device and never sent to a server.

Which save formats are supported?

MessagePack (binary JSON, common in Unity and C# games), plain JSON in UTF-8 or UTF-16, and saves wrapped in GZip, zlib or Deflate compression, Base64 or hex text, single-byte XOR, or a binary header. Any other file can be inspected byte by byte in the hex view.

Can I edit the save and load it back into the game?

Sometimes. You can change values and press Download file, and the decoder packs the save back the same way. But many games protect their saves with a checksum or encryption, and an edited copy is then rejected as corrupted. The decoder warns you when it finds a checksum field. Always keep a backup of the original save.

  • Format detection: peels off GZip, zlib, raw Deflate, Base64 (incl. URL-safe), hex text and single-byte XOR layers in any order, then reads UTF-8 / UTF-16 text with or without a BOM.
  • MessagePack: binary "JSON" saves (common in Unity / C# games) are decoded into readable values and rebuilt on download, keeping each number's exact binary type (int8…int64, float32/float64).
  • Quick edit: every number, string and true/false value as a flat list with its full path, filterable by type, searchable, and paginated for big saves.
  • JSON mode: the whole document as text, for adding or removing fields, array items or whole sections.
  • Lossless round-trip: a custom JSON parser keeps numbers exactly as written (9931676.0 stays a float, 64-bit IDs keep every digit), along with key order, duplicate keys, escapes and the original indentation.
  • Binary wrappers: JSON stored between a binary header and footer is found automatically, and a length field in front of it (uint16/uint32 or C#'s 7-bit varint) is updated when the JSON grows or shrinks.
  • Hex view: files with an unknown format can still be inspected (and edited) byte by byte.
  • Checksum warning: saves with a top-level hash / checksum / signature fingerprint are flagged, since the game will reject an edited copy.
  • Saves protected by a checksum/signature can be decoded and read, but won't load in the game after editing, because the decoder can't recalculate the game's fingerprint. Encrypted saves (AES, etc.) can only be viewed in hex.
  • Other binary serializers (Unity BinaryFormatter, Protobuf…) aren't decoded into fields yet; use the hex view.
  • Compressed layers are re-compressed by the browser, so the bytes differ from the original even when the content is identical. Games read it the same.
  • Always keep a backup of the original save.