RPG Maker Save Editor

Not through this tool. Your original file is never touched, and before a download is allowed the edited save goes through three checks: it's decoded again with the game's own decoder and must match exactly, its object structure must match the file you loaded, and every change you made is read back out of the new file. If any check fails, the download is blocked and you're told why. Keep a backup anyway, since a value can be valid and still be something the game's story logic didn't expect.

MV games keep saves in www/save/ inside the game folder, named file1.rpgsave, file2.rpgsave and so on. MZ games use a save/ folder directly inside the game folder, next to index.html, with names like file1.rmmzsave. For a Steam game, right-click it in your library and choose Manage, then Browse local files. You'll also see global and config files there: the first is the load screen's index and the second holds options-menu settings, so open a numbered file instead. The tool tells you if you pick one of those by mistake.

Load the game's own database. After opening a save, click Choose data folder and select the game's www/data folder (MV) or data folder (MZ), or drag that folder onto the Show real names bar. The editor reads only the eight files it needs (System.json, Items.json, MapInfos.json and similar) on your device, and labels every switch, variable, item, weapon, armor, skill and map with the name the developer gave it. Search then works by name too, so typing bridge finds the right switch. A few commercial games encrypt their data files; for those, the names option shows a clear error and numbers still work.

RPG Maker stores a character's level and their total EXP separately, and the next time the character gains EXP the engine lowers the level until it matches the EXP again. An editor that changes only the level sets up exactly that. When the game's data folder is loaded, this editor uses that class's own EXP curve (the same formula as the engine's expForLevel) to move EXP with the level, and the level with the EXP, so the edit sticks. Without the data folder, the Party tab warns you when a level edit isn't backed by matching EXP.

Browser builds keep saves inside that site's storage, which no other website can read, so you'll need to export the save first. Open the browser console on the game's page. For an MV game, find the key with Object.keys(localStorage), run copy(localStorage.getItem('the-key')), paste the result into a text file named file1.rpgsave, and open that here. Stray quotes and line breaks from the paste are fine. MZ browser games use IndexedDB: list the keys with localforage.keys(), then fetch the value with localforage.getItem('the-key') and save its characters as raw bytes to file1.rmmzsave. The editor recognizes that raw form and writes its download in the same raw form; to restore it, turn those bytes back into a string (one character per byte) and store it with localforage.setItem under the same key.

No. Decoding, re-encoding and verification all run in a background thread with a live progress bar, and a Cancel button stops the job instantly without losing your edits. Long lists (tens of thousands of switches or variables) draw only the rows on screen. In testing with a save far beyond anything the RPG Maker editor can produce (100,000 switches, 100,000 variables, 50,000 self switches and 45 MB of decoded data), it opened in under a second and the page itself never stalled; the verified download took about 2 to 4 seconds. The Raw JSON text box is the one exception: for saves that big it offers a .json export and import instead of an in-page text box.

The editor itself works in a phone browser. Getting the save file is the hard part: a game packaged as an Android app keeps its data in the app's private storage, which a normal file manager can't reach without root access or a backup tool. If you can copy the save file off the device, it's the same format as the desktop version (LZString for MV, zlib for MZ) and will open here.

Try the backup first; if that fails too, the problem was already there. If only the edited file fails, a structural break is unlikely, because the tool checks for that before download, so look at the values instead: a queued teleport to a map id that doesn't exist, a switch that tells the story it's at a point it isn't, or a number far outside what the game's windows were built to show. The Pending changes list shows every edit with its old value, so undo them one at a time until you find the one the game doesn't like.

No. Some online save editors upload your file to a server and delete it later; this one never sends it anywhere. Decompression, editing and re-encoding happen in your browser's memory, and the same goes for the game data folder. You can check: open your browser's developer tools, watch the Network tab while you use the tool, and you'll see no request carrying your file.

No. That's a genuinely different format, not an older version of this one. XP, VX and VX Ace save with Ruby's Marshal serialization (.rxdata, .rvdata, .rvdata2), while MV and MZ use the JavaScript JsonEx format this tool reads. If you drop one in, the tool recognizes the Marshal header and tells you so. If XP/VX/VX Ace support matters to you, the Contact page is the way to ask for it.

Drop it onto the editor at the top of this page. An .rmmzsave file is an RPG Maker MZ save: game state serialized as JSON, compressed with zlib, and on desktop builds stored as UTF-8 text. Opening it in Notepad shows unreadable characters, and saving from Notepad can damage it, because the text encoding is part of the format. The editor reverses both layers, shows the data as editable fields, and writes it back in the identical layout. The same goes for MV's .rpgsave, which is LZString-compressed base64 text instead.

Technically yes, and it helps to know what that involves. For MV, you'd run the file's text through LZString.decompressFromBase64 (in a browser console with the lz-string library loaded), edit the JSON, and recompress with LZString.compressToBase64. For MZ, you'd inflate the zlib data after turning the UTF-8 text back into bytes, then reverse every step exactly. In both cases the JSON is full of @ class tags and, on MV, @c/@r/@a link markers that must stay intact, and the game gives no warning if they don't. It's doable for a single number; for anything more, a tool that checks its own output is the safer route.

Yes. Plugins often store extra data in the save, such as quest logs, relationship points or custom class objects, and the editor keeps all of it exactly as written, including the class tags plugins rely on to rebuild their objects. The Party, Inventory, Switches and Variables tabs edit the engine's standard data, which plugins build on rather than replace. Plugin-specific values the tabs don't show can be edited in the Raw JSON tab, which checks that every internal link still resolves before it accepts the change.