Emulator & Retro Tools
Inspect a validated original PlayStation MCS single-save container and extract its complete save-block payload without changing the source.
01 / Tool workbench
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.
Inspect a validated original PlayStation MCS single-save container and extract its complete save-block payload without changing the source.
Strict MCS single-save framing supported by the existing PS1 parser.
Choose an MCS file, inspect its directory metadata and download the complete payload only after validation.
02 / Compatibility
Compatibility fields are intentionally explicit. Missing values stay unclaimed rather than being filled with generic assumptions.
Accepted extensions
Platforms
PS1
Supported versions / editions
Current documented container family only; exact structural checks in the profile are authoritative.
Input constraints
The MCS directory frame and complete 8 KiB save blocks must validate.
Known limitations
Strict MCS single-save framing supported by the existing PS1 parser.
Output / result
Read-only metadata plus exact raw save-block extraction.
03 / Instructions
File-oriented workflows start with an untouched original. Tool-specific instructions add only details documented for this utility.
Preserve an untouched copy before creating or transforming binary output.
Match the file size, format, platform, and version to the support information on this page.
Use the runtime only when the page reports that its declared engine is loaded.
Compare or test the result before replacing any working source file.
Tool-specific steps
Choose an MCS file, inspect its directory metadata and download the complete payload only after validation.
04 / Privacy and processing
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
Runtime state
Tool-specific privacy notes
Phase 46 reads only a user-selected local file and processes it in the browser. The console-v1 runtime contains no fetch, XMLHttpRequest, WebSocket, sendBeacon, form-upload, or server-side save processing. The shared input ceiling is 16 MiB, with stricter per-profile ceilings where applicable.
05 / Troubleshooting
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
Malformed directory/checksum/block framing fails closed.
06 / Verification
The verification date, method notes, and public references are kept separate from marketing language so compatibility can be reviewed over time.
Method notes
Verified by Phase 46 deterministic fixtures, an independent Python differential verifier, strict malformed-input negatives, source/package parity, and fresh-extraction release regression. This does not edit a PS1 card or infer game-specific values from the save payload.
Public references
07 / FAQ
These answers are generated from the Tool record and current runtime state rather than generic compatibility promises.
Related tools
Only index-ready verified records from the same Tool Family are shown here.