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 Item Editor
Edit saved consumable/key-item inventory quantities by RPG Maker database ID in standard MV/MZ saves.
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.
Session change summary
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
.rpgsave.rmmzsave
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
This is a generic serialized-save editor. It does not load the game database, so inventory entries are identified by database ID rather than item names. Plugins may add custom fields or replace save serialization. Phase 21 does not rewrite XP, VX, VX Ace, 2000, or 2003 saves.
Output / result
A new save with the chosen item database ID quantity updated.
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
Open the save, enter a known item database ID and quantity, apply it, then download and test the copy.
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
The save does not provide database item names. Verify IDs before editing; game plugins can also use custom inventory systems.
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.
Last verified2026-08-08
Profilerpg-maker-item-editor
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 Item Editor ready to use?
The Tool record is verified and declares an operational runtime. The page enables its input controls only when the declared engine module is loaded in the current build.
Does processing stay in the browser?
Yes for this declared mode. The loaded runtime processes the explicit input in the browser; Tool-specific privacy notes describe the exact scope and limits.
Should I keep the original file?
Yes. Keep an untouched source file until any generated output has been validated.
What if my input is rejected?
Use the validation message to correct the base, encoding, width, timezone, byte alignment, or size. The runtime does not guess through invalid input.
Related tools
Continue with the same tool family.
Only index-ready verified records from the same Tool Family are shown here.