This two-image workflow runs the exact Phase 49 forensic report independently on Source A and Source B, requires the same supported GameCube card geometry, then compares source hashes, documented system regions, checksum/validity states, bounded changed-byte ranges, strict directory/allocation evidence and the preserved recovery decisions. The ordered A/B pair receives a deterministic pair ID. The Tool does not infer which source is newer, healthier or authoritative and never emits a repaired card.
Emulator & Retro Tools
GameCube Memory Card Forensic Compare
Compare two same-geometry GameCube memory-card images read-only, bind both sources by SHA-256, map structural and byte-range differences, compare validated filesystem evidence and export a deterministic portable evidence bundle.
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
.raw.gcp.bin.mem.mcd
Platforms
GameCube
Supported versions / editions
Raw/Dolphin-compatible GameCube memory-card images already supported by the Phase 49 forensic report, compared only within the same exact geometry.
Input constraints
Both inputs must individually satisfy the Phase 49 GameCube forensic geometry rules, remain within the permanent 16 MiB per-file browser-local ceiling, and use the same exact card geometry. Geometry mismatch fails closed instead of aligning unrelated offsets.
Known limitations
Read-only comparison only. Source A/B order is descriptive, not chronological or preferential. No preferred-source selection, merge, copy-forward, header repair, mirror repair download, chain/orphan synthesis, directory reconstruction, payload interpretation or payload editing is authorized.
Output / result
Deterministic local comparison JSON, bounded changed-byte-range CSV, and a portable deterministic evidence-bundle JSON containing both Phase 49 reports, the comparison, CSV text, and a SHA-256 manifest for each embedded artifact. Neither source image nor repaired bytes are embedded.
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
Choose two original same-geometry GameCube card images. Keep both originals unchanged. Run the comparison, preserve the pair ID and evidence bundle with the source files, and use the structural differences as evidence rather than as an automatic recommendation to overwrite either 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 50 reads only the two explicitly selected local files in the browser. The forensic-compare-v1 runtime contains no fetch, XMLHttpRequest, WebSocket, sendBeacon, form upload, server-side save processing, or telemetry path. Comparison and evidence-bundle exports contain no raw source images, no repaired-save bytes, and never alter or replace either selected source file.
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
If the geometries differ, compare each image separately with the Phase 49 report instead. If either report shows invalid headers, multiple metadata defects or strict parser failures, treat those as evidence only; this Tool intentionally refuses to choose or synthesize a replacement.
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-10
Profilegamecube-memory-card-forensic-compare
Method notes
Verified with deterministic clean/equal/different/corrupt fixture pairs, independent SHA-256 and changed-byte-range calculations, exact parity with both Phase 49 source reports, stable ordered pair identifiers, deterministic JSON/CSV evidence exports, evidence-bundle artifact-manifest hash checks, immutable-source assertions, no preferred-source selection, no repaired-file output, source/installable parity, and fresh-extract release regression.
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 GameCube Memory Card Forensic Compare 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.
Related guides
Read the guidance connected to this tool.
Only reviewed, index-ready Guides that explicitly reference this Tool are included.
Beginner
Backups & Safety
GameCube Memory Card Image Backup & Identification Guide
A safety-first GameCube Memory Card Image guide for identifying the intended representation, preserving an untouched source copy, and choosing only a verified compatible Tool.
Beginner
Save File Formats
GameCube Memory Card Image Integrity & Troubleshooting Guide
A fail-closed GameCube Memory Card Image troubleshooting guide for distinguishing representation problems from unsupported semantics and for selecting read-only integrity checks before any repair attempt.