Skip to content
Game save workbench
Local-first tools No installation Support status shown
SAVEEDITOR.COM
Browse tools
DEVICE-LOCAL Favorites and recent pages stay in this browser.

File Analysis

Save Schema Knowledge Graph Explorer

Explore machine-readable relationships among SaveEditor's strictly verified save representations, platforms, format hubs, parsers, evidence and existing capability authority without inferring game-specific fields.

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.

Save Schema Knowledge Graph Explorer
BROWSER LOCAL

Checking whether the declared runtime module is loaded. No input has been processed.

Session change summary

No output has been built in this session.

Phase 62 schema boundary

This explorer models representation-level facts already proven by SaveEditor. It links strict formats/wrappers to platforms, parsers, evidence and capability routes, but it does not invent a schema for a game payload merely because the outer representation is recognized.

Existing authority only

Recovery, extraction, migration and forensic edges point only to Tools and engines that already own that authority. The graph itself is read-only and cannot execute or widen those capabilities.

Machine-readable export

The bundled graph can be exported deterministically as JSON. It contains relationship metadata, not raw save bytes or hidden game-field assumptions.

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

No save file input. The explorer reads only the bundled Phase 62 machine-readable graph.

Platforms

No platform assignment is recorded.

Supported versions / editions

SaveEditor Phase 62 schema graph v1, derived from the frozen Phase 61 fingerprint catalog plus existing Phase 47-60 capability contracts.

Input constraints

No upload, file picker, URL import, archive expansion, or save-byte processing. The graph is limited to the twenty strict Phase 61 representations and already-existing authority routes.

Known limitations

Representation-level relationships only. Identifying a format or wrapper does not imply knowledge of game-specific fields, offsets, values, signing keys, encryption, or editability.

Output / result

Interactive graph relationships plus deterministic JSON export of the bundled graph. No save bytes, repaired output, migration output, or inferred game-field schema is produced.

03 / Instructions

Use a reversible workflow.

File-oriented workflows start with an untouched original. Tool-specific instructions add only details documented for this utility.

  1. 01Keep the original

    Preserve an untouched copy before creating or transforming binary output.

  2. 02Confirm scope

    Match the file size, format, platform, and version to the support information on this page.

  3. 03Process locally

    Use the runtime only when the page reports that its declared engine is loaded.

  4. 04Validate output

    Compare or test the result before replacing any working source file.

Tool-specific steps

Choose a representation to inspect its platform, format hub, parser, evidence, wrapper relationships, and existing-only capability routes. Export the deterministic graph JSON if needed.

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

The explorer does not request or read a save file. All graph data ships inside SaveEditor Core and is rendered in the browser. The schema-knowledge-v1 runtime has no fetch, XMLHttpRequest, WebSocket, sendBeacon, FormData upload, telemetry, or server-side save-processing path.

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.

Wrong file or size

Re-check the documented input type and browser size limit before retrying.

Unsupported format

A generic converter does not imply support for every game-specific container, signing scheme, or serialization format.

Source was modified

Return to the untouched source instead of repeatedly processing a damaged or partially transformed file.

Known Tool issues

If graph data is missing or fails its schema/edge validation, the runtime refuses to mount rather than constructing relationships from filenames, extensions, or guessed semantics.

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-11
Profilesave-schema-knowledge-graph-explorer

Method notes

Verified by exact JSON/JavaScript graph parity, unique node IDs, valid edge references, exactly twenty representation nodes, existing-only authority edges, deterministic export, no-network/mutation static checks, catalog idempotence, installable/source parity, and the full historical regression suite.

Public references

  1. https://github.com/ShendoXT/memcardrex
  2. https://github.com/ps2dev/ps2sdk
  3. https://github.com/dolphin-emu/dolphin
  4. https://github.com/TASEmulators/desmume
  5. https://github.com/mupen64plus/mupen64plus-core
  6. https://mc.pp.se/dc/
  7. https://www.rpgmakerweb.com/

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 Save Schema Knowledge Graph Explorer 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.