Which games and engines does Save Editor support?

One of the most common questions is simply: "Will it work with my game?" This is the honest, up-to-date answer — what you can edit right now, what we already recognize and are building support for, and what to do if your format isn't on the list yet.

Editable right now

These formats load straight into the editor — you can search, change values, and download a working save:

• Ren'Py (.save) — the visual-novel engine. One of the most popular formats on the site. See also our guide on Ren'Py signing, which you'll need after editing.
• RPG Maker (.rpgsave and friends) — MV / MZ, plus older VX / XP projects.
• TyranoScript / TyranoBuilder (.sav) — another widely used visual-novel engine.
• Wolf RPG Editor (.sav) — ウディタ, the Japanese engine behind a large catalogue of doujin and commercially localised RPGs. Slots and the System.sav beside them are recognized by what is inside them, so a save opens even when it arrives renamed. Worth knowing before you open one: Wolf stores its variables by number, not by name — the names live in the game's own project files, which are not part of the save, so you will see entries like var7 rather than "HP". Change a value in the game, save again, and compare the two files. Everything you do not touch is written back byte for byte and the checksum is recalculated for you.
  Two kinds of Wolf save do not open. Games that set a protection key encrypt their saves with it, and that key is not in the file — we recognize those and say so, rather than calling them an unknown format, but nobody can edit them from the save alone. Saves from the newest engine builds are held back too: their layout adds fields we cannot place from the few examples we have, and a wrong guess would write a broken save rather than fail to read one.
• Naninovel — Unity-based visual novels, stored as JSON.
• Twine — interactive-fiction stories saved inside HTML.
• Unreal Engine (GVAS .sav) — the standard Unreal save container.
• QSP — Quest Soft Player — text-quest engine, detected automatically by its signature.
• Plain JSON (.json) — and, thanks to universal JSON support, any save that's really JSON under the hood, whatever its extension. A huge number of indie and HTML5 games fall into this bucket.

If your game stores progress as JSON (a lot of web and Unity games do), there's a good chance it just works — even if the engine isn't named above.

Recognized — parser on the way

Sometimes you'll upload a file and get a "we recognize this format, but editing isn't ready yet" message instead of the editor. That's deliberate, and it's good news: it means we detected the format, kept your file for analysis, and added a data point that helps us prioritize what to build next.

Formats currently in this recognized-but-not-ready state include:

• TADS — classic interactive-fiction engine
• ZenGin / Gothic — the Gothic series save format
• Larian LSF — Divinity: Original Sin 2 and Baldur's Gate 3
• Godot (encrypted resources) — needs the game encryption key
• GTA V (PS-style encrypted saves) — needs a key
• Unity binary saves
• A few unlabeled binary containers we're still reverse-engineering

On our radar (not detected yet)

RTON (Plants vs. Zombies 2) and Easy Save 3 (Unity). We know about them; we just need more samples to build reliable detection.

My format isn't listed — what do I do?

Upload it anyway. Two things happen:

1. If it's secretly JSON (or one of the engines above), it'll likely just open.
2. If it's a recognized-but-not-ready format, your upload is logged and the file is retained for analysis — which is exactly how we decide what to build next. The formats people upload most get parsers first.

So uploading an unsupported save isn't a dead end — it's a vote.