Inspect RPG Maker VX RVDATA databases, maps and serialized values online. Browse class tags and shared objects, then download the JSON export and original file.
Processing runs on our servers. Upload one file, then open inspection.game-data.json in the result browser. The Tree view shows the inspection status, metadata, roots and objects. Select a reference to open the same shared object, including cycles, without repeatedly expanding it.
Class tags describe the type recorded by the game. They are names to inspect; no game classes, constructors or loading hooks are run. Bytes are retained as Base64, large integers as decimal strings and map entries as key/value pairs. Raw JSON, the inspection export and the original file remain available to download.
.rvdata is used by RPG Maker VX, and .rvdata2 by VX Ace. Both use Ruby Marshal 4.8. Open records such as Actors.rvdata or Map001.rvdata to inspect class names, instance variables, strings, hashes and arrays. RGSS Table, Color and Tone payloads expose their stored numeric values. Other custom payloads retain their bytes and class tags.
Consecutive Marshal streams can be inspected as separate roots. Renaming a supported Marshal save to .rvdata allows the same read-only inspection. This viewer does not render maps or interpret events as a playable game.
Scripts.rvdata and Scripts.rvdata2 retain their existing Ruby source recovery through the RPG Maker tools. For the other data format, use the RVDATA viewer or RVDATA2 viewer.
This is an inspector, not a save editor. The exported JSON cannot be loaded as an edited save, and signatures are not verified or rewritten. A fully decoded result describes the serialized records, including inert construction instructions; it does not reconstruct a running game.
Results distinguish fully decoded, partly decoded, metadata-only, unsupported and malformed inputs. A partial result is not a complete state tree. Inspection is bounded to 16 MiB of serialized state, 32 MiB save containers, 20,000 objects, 80,000 references, 128 nesting levels and five seconds per parser. Larger exports may require downloading the JSON instead of displaying its tree.
For files inside an extracted game, select a supported data file to start its own inspection. Listing a directory does not deserialize all its saves or databases. Custom formats, encryption and damaged files may prevent inspection; the result notes explain where processing stopped.