Dolphin distinguishes a GameCube memory card from an individual exported save. This converter handles only the individual-save representations whose complete framing is documented in Dolphin source. The underlying game data is not decoded or rewritten. Conversions are therefore bounded container transforms: validate the source, canonicalize the directory entry, preserve every payload block, and emit only the selected documented wrapper.
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
.gci.gcs.sav
Platforms
Dolphin / GameCube
Supported versions / editions
Dolphin-compatible GameCube single-save containers: native GCI, MadCatz GameShark GCS, and Datel MaxDrive/Pro SAV. Conversion follows Dolphin source framing rules, including SAV directory-entry byte swaps and GCS block-count normalization.
Input constraints
Input must contain exactly one GameCube single-save record with a 64-byte directory entry and one or more complete 8192-byte data blocks. GCS and SAV magic/header layout must validate; GCI and SAV block counts must match file size exactly.
Known limitations
This is not a GameCube memory-card image editor and does not alter FAT/directory structures inside .raw/.gcp card images. It does not decrypt or resign Wii data.bin, convert emulator save states, repair corrupt saves, or infer game-specific payload semantics.
Output / result
A newly framed .gci, .gcs, or .sav single-save file. The canonical 64-byte directory entry and all complete 8 KiB payload blocks are preserved; only the documented outer container representation changes.
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 a validated GameCube single-save file, select the required output wrapper, convert locally, then test the copy in Dolphin or another tool that explicitly supports that wrapper. Keep the source file until compatibility is confirmed.
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 36 reads a selected file only after explicit local file selection. Parsing, inspection, normalization, extraction, and supported conversions run in the browser. The emulator-retro runtime contains no fetch, XMLHttpRequest, WebSocket, or sendBeacon calls. The shared file ceiling is 16 MiB, with stricter format-specific limits where appropriate.
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 validation fails, confirm the file is a single GameCube save rather than a full memory-card image or unrelated .sav file. SaveEditor rejects wrong magic, truncated blocks, zero-block entries, and size/count mismatches instead of guessing.
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-08
Profiledolphin-save-converter
Method notes
Verified against current Dolphin GCMemcard single-save source for GCI/GCS/SAV header sizes, magic values, directory-entry offsets, block-count handling, SAV byte-swap positions, and writer behavior, plus deterministic cross-format fixtures and negative cases.
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 Dolphin Save Converter 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 GCI Backup & Identification Guide
A safety-first GameCube GCI guide for identifying the intended representation, preserving an untouched source copy, and choosing only a verified compatible Tool.
Beginner
Save File Formats
GameCube GCI Integrity & Troubleshooting Guide
A fail-closed GameCube GCI troubleshooting guide for distinguishing representation problems from unsupported semantics and for selecting read-only integrity checks before any repair attempt.
Beginner
Backups & Safety
GameCube GCS Backup & Identification Guide
A safety-first GameCube GCS guide for identifying the intended representation, preserving an untouched source copy, and choosing only a verified compatible Tool.