Supported Save Formats and Compatibility Limits

JSON and standard RPG Maker saves

JSON objects and arrays, standard RPG Maker MV .rpgsave files and standard MZ .rmmzsave files support reading and editing. Recognized Base64, URL, Gzip, Zlib and LZ-String layers are reapplied when you export.

The editor changes existing primitive values. RPG Maker database JSON files can add readable labels to recognized MV/MZ paths, including decoded JSON copies and supported encoding wrappers. This mapping does not apply to unrelated JSON structures or Ruby Marshal saves. It preserves protected metadata and does not add inventory records, rebuild game databases or synchronize related stats.

Structured files and archives

Additional codecs recognize MessagePack, CBOR, BSON, XML, Unity PlayerPrefs XML, Property Lists, YAML, TOML, CSV/TSV and INI/CFG/Properties. Several rely on the filename extension to select the parser. Support is for recognized structures; custom variants may still be rejected.

Structured exports rebuild the content. Do not assume comments, whitespace, original binary layout or application-specific conventions survive reconstruction. SQLite export rebuilds tables in a new database; it is not a full-fidelity database editor for views, triggers and indexes.

ZIP archives expose text and recognized JSON or Pickle entries. Binary attachments are kept as opaque data. Recognizing a Ren’Py archive does not guarantee that a particular game will accept an edited file, especially when it uses additional validation.

Binary editing and read-only formats

Godot Variant, .NET NRBF and Python Pickle parsers expose supported scalar values where they can be represented. Opaque data and references are protected. Executable objects and Pickle instructions are not run.

Unreal GVAS and Ruby Marshal / RGSS containers are currently read-only. You can inspect recognized values and download the original, but Savepoint does not export edits for these formats. RPG Maker XP, VX and VX Ace use Ruby Marshal rather than the standard MV/MZ formats.

Unity ES3 binary, Flash SOL, Wolf RPG, encrypted saves and game-specific signed formats need dedicated codecs. A shared .sav or .dat extension does not establish compatibility.

How to check compatibility safely

A successful import confirms that a parser recognized the file. A successful export confirms that the editor wrote a supported container. Neither proves that a game accepts every edited value.

1. Create a backup and note the game version and save slot.
2. Check the detected format and whether the editor offers editing or read-only inspection.
3. Change one known value, download the file and test it in the same game version.
4. Restore the backup if loading fails. Keep the original extension and check for cloud synchronization overwriting your local change.