SaveEditorAHSave hub
All universal editors

Base64-encoded saves

When the file is Base64 text wrapping JSON or binary. Decode, edit, then download a new Base64 file.

All processing runs locally in your browser. Your save file is not uploaded to our servers.

Drop a save file here or browse

Drag and drop or choose a file. After load you will see name, size, and extension.

Steps & tips (Base64)

How to use

  1. Back up the original file. The tool expects the file content to be Base64 text (UTF-8 or Latin-1); whitespace is ignored.
  2. After upload, the inner payload is decoded. If it is JSON, you get the same path-based editor as the JSON tool; if it is binary, you get a hex grid on the decoded bytes.
  3. Edit values, then download. The output file is UTF-8 text containing a new Base64 string representing the updated payload (not necessarily identical padding to the original).
  4. Replace the game file only after verifying size/encoding expectations for that title.

Tips & limits

  • Decoding tries UTF-8 first, then Latin-1 byte mapping — useful when the file is ASCII-only Base64 without a BOM.
  • If decode fails, the content is not valid Base64 for this parser — use the hex tool on the raw file instead.
  • Inner JSON that is not UTF-8 may mis-parse; binary inner content always falls back to hex.
  • Cryptographic signatures or hashes on the outer file are not updated — the game may refuse to load modified saves.