File Analysis
GameCube Card Copy Selection Inspector
Explain which validated directory/BAT copy the existing parser selects by update counter.
Game save workbench / Tool directory
Browse SaveEditor.com by job, platform, processing mode, or verified support state. The directory separates working tools from in-development records and does not promote planned tools as available.
01 / Browse by job
These stable category pages are the clean discovery paths. Use filters below for temporary combinations such as platform plus processing mode.
02 / Tool catalog
Every result carries its support state and processing mode. Read each tool page for exact file, platform, and version compatibility.
File Analysis
Explain which validated directory/BAT copy the existing parser selects by update counter.
File Analysis
Prove a high-confidence GameCube Datel SAV Fingerprint match from strict local content/structure checks without trusting filename extension or byte length alone.
File Analysis
Report validated GameCube memory-card geometry and fixed metadata/data block boundaries.
Emulator & Retro Tools
Strictly validate a GameShark GCS single-save wrapper and extract only the exact complete 8 KiB-block payload range after the 0x150-byte wrapper.
Emulator & Retro Tools
Strictly validate a DATELGC_SAVE single-save wrapper and extract only its exact complete 8 KiB-block payload range after the 0xC0-byte wrapper.
File Analysis
Prove a high-confidence GameCube Memory Card Fingerprint match from strict local content/structure checks without trusting filename extension or byte length alone.
File Analysis
Prove a high-confidence GameCube GCI Fingerprint match from strict local content/structure checks without trusting filename extension or byte length alone.
File Analysis
Prove a high-confidence GameCube GCS Fingerprint match from strict local content/structure checks without trusting filename extension or byte length alone.
Emulator & Retro Tools
Diagnose the documented single-mirror GameCube metadata failure and export validated saves as GCI without rewriting the selected source card.
Emulator & Retro Tools
Repair exactly one corrupted GameCube directory/BAT mirror by reproducing the documented copy, update-counter, checksum, and strict-reopen rule.
Emulator & Retro Tools
Generate a deterministic read-only evidence report for GameCube card geometry, header checksums, directory/BAT mirrors, byte ranges, filesystem evidence and the exact Phase 47 recovery decision.
Emulator & Retro Tools
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.
Emulator & Retro Tools
Refresh the inactive valid GameCube directory mirror from the parser-selected active directory copy, incrementing only the rebuilt copy counter and checksum before strict reopen.
Emulator & Retro Tools
Refresh the inactive valid GameCube BAT mirror from the parser-selected active BAT copy, incrementing only the rebuilt copy counter and checksum before strict reopen.
Emulator & Retro Tools
Restore exactly one damaged byte in the fixed GCSAVE wrapper marker only when exact GCS geometry and the existing strict GameCube single-save parser prove the reconstructed file.
Emulator & Retro Tools
Restore exactly one damaged byte in DATELGC_SAVE only when exact Datel SAV geometry and the existing strict parser validate the entire reconstructed single-save wrapper.
Emulator & Retro Tools
Inspect supported raw/Dolphin GameCube memory-card images, validate mirrored filesystem metadata and block allocation, and export validated saves as GCI.
Emulator & Retro Tools
Convert validated GameCube single-save files between Dolphin-compatible GCI, MadCatz GameShark GCS, and Datel MaxDrive/Pro SAV framing while preserving the canonical directory entry and complete save blocks.
03 / Read the status first
Game save formats can change between platforms, game versions, storefronts, or updates. A SaveEditor.com tool page should state the input format it accepts, supported versions where known, its processing mode, limitations, and the date its support was last verified.
Verified means the tool has reached the project's supported state. In development means the record may be useful for documentation or progress visibility, but the interface must not be presented as finished. Planned and deprecated records stay out of the normal directory.