Save editors by engine
Games built on the same engine usually save the same way, so a tool for one often works for another.
RPG Maker
RPG Maker MV and MZ games keep each save slot in a compressed JSON file (.rpgsave / .rmmzsave). Our RPG Maker editor opens both.
Ren'Py
Ren'Py visual novels save to pickled Python files (.save). Most changes are made with the developer console or by editing variables, not by editing the file by hand.
Unity
Unity games store saves however the developer chose: plain JSON, Easy Save 3 (.es3), PlayerPrefs in the registry, or custom binary files.
Unreal Engine
Unreal Engine games usually save to .sav files in the GVAS format, a typed property tree that tools like uesave can turn into JSON and back.
GameMaker
GameMaker games often write saves as INI, JSON or Base64-encoded JSON text, which our JSON / Base64 editor can open.
MonoGame / XNA
MonoGame and XNA games are C# programs; saves are usually XML or binary files written with .NET serializers.
Java / libGDX
Java games built with libGDX usually save to text, JSON or Java-serialized files in the user folder.
LÖVE (Lua)
LÖVE games save Lua tables, often compressed, to the LÖVE save folder in AppData.
Own engine
Games on the studio's own engine (REDengine, Frostbite, EA Black Box, PhyreEngine...). Each has a format of its own, so you need a tool written for that game.