This browser-local tool works against serialized RPG Maker data and changes only the explicitly selected supported value in a working copy before a new file is generated. Keep the original untouched until the game successfully loads the edited result. Customized save codecs or project object layouts can be incompatible and are rejected rather than guessed.
RPG Maker Tools
RPG Maker Save Validator
Validate that a file decodes with a supported standard RPG Maker MV/MZ codec and contains the expected serialized save-content structure.
01 / Tool workbench
Use the runtime only when it is actually ready.
The application shell fails closed. An input interface is not enabled merely because a WordPress Tool record exists; the declared engine must be registered in the current build.
No output has been built in this session.
02 / Compatibility
Know the supported input before opening a file.
Compatibility fields are intentionally explicit. Missing values stay unclaimed rather than being filled with generic assumptions.
Accepted extensions
Platforms
RPG Maker
Supported versions / editions
Standard RPG Maker MV .rpgsave files using JsonEx plus LZ-String Base64, and standard RPG Maker MZ .rmmzsave files using JsonEx plus zlib/DEFLATE storage. Game plugins can replace or extend serialization, so non-standard save codecs remain unsupported unless separately verified.
Input constraints
Local save input is capped at 4 MiB. Expanded JSON is capped at 16 MiB. The save must decode to an MV/MZ-style save-content object. Ruby Marshal saves from XP/VX/VX Ace and RPG Maker 2000/2003 binary saves are detection-only in Phase 21.
Known limitations
Validation is structural and codec-level only. It does not prove that plugin-defined game logic is internally consistent, nor does it repair saves.
Output / result
A local detection/validation result. No save values are modified and no output save is generated.
03 / Instructions
Use a reversible workflow.
File-oriented workflows start with an untouched original. Tool-specific instructions add only details documented for this utility.
- 01Keep the original
Preserve an untouched copy before creating or transforming binary output.
- 02Confirm scope
Match the file size, format, platform, and version to the support information on this page.
- 03Process locally
Use the runtime only when the page reports that its declared engine is loaded.
- 04Validate output
Compare or test the result before replacing any working source file.
Tool-specific steps
Choose the file and run validation. A standard MV/MZ file must decode and expose the expected save groups; recognized legacy formats are reported as unsupported rather than parsed.
04 / Privacy and processing
The processing mode is part of the product contract.
SaveEditor.com should state local processing only when the implementation truly keeps file contents in the browser. Server or hybrid processing must be disclosed just as clearly.
Declared mode
Browser local
Runtime state
Operational
Tool-specific privacy notes
Phase 33 reads the selected file only after explicit local file selection. Standard MV/MZ processing and bounded XP/VX/VX Ace Ruby Marshal parsing, supported edits, validation, and export run in the browser. The RPG Maker runtime contains no fetch, XMLHttpRequest, WebSocket, or sendBeacon calls. Selected files are capped at 4 MiB; unsupported or ambiguous legacy structures fail closed.
05 / Troubleshooting
When a file is rejected, do not force it.
A rejection can indicate an unsupported size, format, version, platform, or byte sequence. Preserve the original and correct the input instead of bypassing validation.
Re-check the documented input type and browser size limit before retrying.
A generic converter does not imply support for every game-specific container, signing scheme, or serialization format.
Return to the untouched source instead of repeatedly processing a damaged or partially transformed file.
Known Tool issues
A structurally valid save can still be rejected by a particular game because of plugin logic, incompatible versions, or application-level checks.
06 / Verification
Support claims should be traceable.
The verification date, method notes, and public references are kept separate from marketing language so compatibility can be reviewed over time.
Method notes
Verified with exact LZ-String interoperability vectors, MV encode/decode fixtures, MZ zlib cross-compatibility against Node zlib, legacy Ruby-Marshal detection fixtures, save-shape rejection tests, and structured edit round trips. Progression-coupled fields such as level/EXP are intentionally not modified generically.
07 / FAQ
Questions to answer before editing.
These answers are generated from the Tool record and current runtime state rather than generic compatibility promises.
Is RPG Maker Save Validator ready to use?
Does processing stay in the browser?
Should I keep the original file?
What if my input is rejected?
Related tools
Continue with the same tool family.
Only index-ready verified records from the same Tool Family are shown here.
Related guides
Read the guidance connected to this tool.
Only reviewed, index-ready Guides that explicitly reference this Tool are included.
Backups & Safety
RXData / RPG Maker XP Backup & Identification Guide
A safety-first RXData / RPG Maker XP guide for identifying the intended representation, preserving an untouched source copy, and choosing only a verified compatible Tool.
Save File Formats
RXData / RPG Maker XP Integrity & Troubleshooting Guide
A fail-closed RXData / RPG Maker XP troubleshooting guide for distinguishing representation problems from unsupported semantics and for selecting read-only integrity checks before any repair attempt.
Backups & Safety
RPG Maker MZ Save JSON Backup & Identification Guide
A safety-first RPG Maker MZ Save JSON guide for identifying the intended representation, preserving an untouched source copy, and choosing only a verified compatible Tool.