Identify the game's actual save mechanism
The 32X name on a game does not imply that the expansion contains a universal memory-card system. Inspect the game's own manual and save menu. A cartridge title may store progress using its cartridge hardware, provide passwords, or offer no persistent progress at all. A CD 32X title belongs to a different storage path involving CD backup memory. The Sega 32X instruction manual distinguishes cartridge operation and CD game saving; use the title's instructions for the specific save behavior.
Make a small inventory before any cartridge repair: game title, regional edition, revision if known, visible save slots, settings and a progress description. Photograph the in-game load screen. This is a baseline for comparison, not an exported backup. If the game offers passwords, record them exactly and verify one on a new session before relying on it.
Preserve original cartridge data
Use a documented dumper or backup utility that supports the exact cartridge's storage type. ROM dumping and save extraction are different operations. A successful game dump does not prove that a utility read its save chip. Retain the first extracted file, its size, checksum, tool version and settings. If a second read differs unexpectedly, investigate the connection or storage support before writing anything back.
Restore a working copy to spare compatible storage or a controlled emulator configuration, where supported, then verify actual progress in the game. Keep the original untouched. Consult the existing Genesis game and save backup article for related tools, but verify that a tool explicitly supports your 32X game's mapper and save hardware. Do not replace a retention component before extracting valuable data if extraction is still possible.
Modern cartridges require their own checks
The MegaSD manual documents cartridge save storage on microSD. The Mega EverDrive Pro manual lists EEPROM support and explains its game-data directories. Follow the installed cartridge's actual procedure to commit a save and end the session. Copy the relevant files to a computer only after normal shutdown and safe card removal. Keep firmware and configuration notes with each archive.
Game-native saves and save states are different. Krikzz documents that the in-game menu does not work with a 32X attached; a feature described for ordinary Genesis play should not be assumed for 32X games. Avoid building a preservation plan around an unsupported quick-save function. Likewise, a ROM hack may change a save layout, so keep its patch version separate from the original game's backup.
Handle CD saves as a separate system
For a physical CD 32X game, use the Sega CD backup RAM guide. Record whether the data resides internally or on a backup cartridge. Do not format a memory manager merely because a new game requests free space; copy and verify existing entries first. For any saving fault, make a disposable test save, shut down normally, restart and note precisely what disappeared. This differentiates unsupported game behavior, an uncommitted flash-cartridge save and a hardware retention problem.