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

PS2 Allocation Range Inspector

Summarize the bounded standard-card allocation range and classify strict FAT values without changing allocation state.

PS2

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.

PS2 Allocation Range Inspector
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.

Read-only Phase 63 boundary

This Tool exposes one distinct PlayStation structural diagnostic already supported by strict SaveEditor parsers. It never repairs, decrypts, resigns, migrates, converts, inserts, deletes, or rewrites save bytes.

Fail-closed evidence

Output is bound to the selected source by SHA-256. Invalid geometry, malformed tables, broken bounded chains, unsupported wrappers, or out-of-range metadata are refused rather than guessed.

PS2 Allocation Range Inspector

Summarize the bounded standard-card allocation range and classify strict FAT values without changing allocation state.

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

.ps2.mcd.bin.raw

Platforms

PS2

Supported versions / editions

Standard 8 MiB PS2 memory-card filesystem images and EMS PSU archives already supported by the verified Phase 34 parser.

Input constraints

A complete standard 8 MiB PS2 card accepted by the existing filesystem parser, either data-only or complete 528-byte-page representation where applicable.

Known limitations

Read-only structural diagnostics only. No repair, undelete, filesystem write, ECC generation, decryption, resigning, game-specific checksum work, game-field inference, migration, or conversion authority is added by Phase 63.

Output / result

A deterministic browser-local JSON diagnostic report containing source SHA-256 identity and only parsed structural metadata; raw save payload bytes are not embedded in the report.

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 one local file matching the documented representation. SaveEditor validates the relevant PlayStation structure before producing a diagnostic report. A failed structural predicate causes refusal rather than guessed output.

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 63 reads only the explicitly selected local file in the browser under the permanent 16 MiB ceiling. The playstation-ecosystem-v2 runtime contains no fetch, XMLHttpRequest, WebSocket, sendBeacon, FormData upload, telemetry, or server 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

A refusal means this exact diagnostic profile could not prove its required representation or structure. Renaming a file, matching a common size, or supplying a proprietary archive does not bypass validation.

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
Profileps2-allocation-range-inspector

Method notes

Verified against the pre-existing strict PS1, PS2 and PARAM.SFO parsers, deterministic Phase 34/57/61 fixtures, malformed/truncated negative cases, SHA-256-bound output, source immutability, independent reference checks, and full historical regression/source-package parity.

Public references

  1. https://github.com/PCSX2/pcsx2/blob/master/pcsx2/Reference/PS2-MemoryCardFileSystem.htm
  2. https://github.com/ps2dev/mymc/blob/master/ps2mc.py
  3. https://github.com/ps2dev/mymc/blob/master/ps2save.py

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 PS2 Allocation Range Inspector 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.