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.
Save Editors
Perform one deliberately narrow, documented RimWorld 1.6.x save edit locally: convert an existing commitment/permadeath save to normal reloadable mode while keeping all colony/world/gameplay XML untouched.
Save Editors
Edit the verified PC SlotData money and experience fields locally while keeping the character name, chapter marker, and all unrelated bytes read-only.
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.
Emulator & Retro Tools
Inspect and normalize standard 8 MiB PCSX2-compatible PS2 memory-card images, export eligible save directories as EMS PSU, and inspect/extract validated PSU single-save containers.
Emulator & Retro Tools
Split and rebuild the exact Mupen64Plus-Next RetroArch 290 KiB composite battery-save layout using fixed EEPROM, four Controller Pak, SRAM, and FlashRAM regions.
Emulator & Retro Tools
Convert explicitly typed GBA battery-save bytes between mGBA standalone SAV representation and libretro raw save RAM while preserving an existing mGBA 16-byte RTC record only when it is actually present.
Emulator & Retro Tools
Inspect a local file for conservative emulator/save-format signatures and size conventions, separating high-confidence containers from extension-only candidates.
Emulator & Retro Tools
Inspect a validated original PlayStation MCS single-save container and extract its complete save-block payload without changing the source.
Emulator & Retro Tools
Inspect an EMS PSU single-save archive and extract its validated contained files locally without rewriting the archive.
Emulator & Retro Tools
Normalize complete PS1 memory-card containers to a standard 128 KiB raw card, export individual valid saves as MCS files, and inspect validated MCS single-save containers.
Emulator & Retro Tools
Inspect strict Dolphin-compatible GCI, GCS or SAV single-save framing and extract the complete 8 KiB-block payload without conversion.
Emulator & Retro Tools
Prepare supported PS1 memory-card images for DuckStation by normalizing recognized raw and wrapped card containers to the standard 128 KiB raw-card representation.
Emulator & Retro Tools
Inspect the documented unencrypted Wii backup-header relation in a data.bin candidate while keeping encrypted and signed regions strictly read-only.
Emulator & Retro Tools
Inspect standard PlayStation 2 8 MiB memory-card images locally, including superblock geometry, FAT-backed directory traversal, contained save folders, protection flags, filenames, and file sizes.
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
Normalize supported standard PS2 memory-card images to the 8 MiB data-only representation, export verified save directories as EMS .psu containers, and inspect/extract files from validated EMS PSU saves.
Emulator & Retro Tools
Inspect bounded Xbox 360 CON/PIRS/LIVE XContent header metadata without claiming package trust, filesystem extraction or resigning.
Emulator & Retro Tools
Inspect metadata from a PSP PARAM.SFO file locally, including title/category fields and numeric or UTF-8 entries, without decrypting or rewriting the associated savedata payload.
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.