Cross‑Emulator Save Format Analyzer
Analyze, normalize & convert retro emulator save files locally (no upload required).
1. Add Save Files LOCAL ONLY
Name | Size | Format | System | Integrity | Hashes | Actions |
---|
2. Hash Overview
3. Normalize & Convert
Select a row to open its metadata, preview the first bytes, trim or pad padding bytes, and export extension variants. Complex container formats (.mcr
, .gci
) are identification-only here for safety.
About This Tool
This lightweight browser tool helps retro players, archivists, and collection managers inspect and convert save files between popular emulator ecosystems without uploading anything. It recognizes common battery or memory card save extensions such as .sav, .srm, .raw, .eep, .fla, .dsv, plus PlayStation .mcr and GameCube .gci (ID only). Heuristics rely on file size signatures, extension hints, entropy sampling, and padding analysis to guess likely systems (GB/GBC, GBA, DS, SNES, N64, etc.). Hashes (CRC32, SHA‑1, SHA‑256) are computed client-side for verification and archival integrity. A normalization module lets you trim trailing 0x00 / 0xFF padding or expand a save to the next power of two, then export a variant with the extension your target emulator expects. Because everything runs locally, the process is private, fast, and suitable for offline use after first load.
How to Use
- Drop or select one or more supported save files above.
- Press Analyze to classify format, guess system, and calculate hashes.
- Click a table row to view details and normalization actions.
- Trim or pad if an emulator rejects the original size.
- Export individual variants or bulk export all convertible saves.
Tips
- If two saves differ by only padding, trimming can unify them.
- Match CRC32 or SHA‑1 with database entries to confirm authenticity.
- Always archive originals; conversions are convenience copies.
- Low entropy warnings usually indicate a mostly blank or uninitialized region.
- Bookmark the page; it works offline after first load.
Roadmap ideas: deeper PlayStation card directory parsing, DS auto‑padding hints, optional public preservation hash DB lookups, and diff view between two selected saves. Suggestions welcome.
Read Also: