Know what each saved item represents
Ordinary in-game saves, cartridge memory and a Memories snapshot are different kinds of progress. Identify which one your game actually uses before copying files or loading an old state. A snapshot represents a particular running session, while the game's own save records what its software chooses to retain. Restoring an earlier session can change the progress you subsequently save.
For openFPGA, the official directory specification places user-created nonvolatile files under Saves, using a structure related to the loaded Assets paths. Core support determines what is written there. Memories are organized separately by core. Keep the exact core release with the backup because state compatibility across releases is a question for that maintainer.
Preserve the whole layout first
- Finish gameplay and power off before removing the card for a computer backup. Check that the card reader is not still writing before disconnecting it.
- Copy the complete card to a dated folder. Retain folder names and the relative structure instead of gathering only files with a familiar extension.
- Keep a second copy on separate storage. Compare file counts and sizes; use hashes when you need to establish that valuable files were copied without change.
- Record Pocket firmware, core author and version, game identifier, important settings and the date of the checkpoint.
- Test a restore on spare storage or disposable progress before relying on it as the only recovery route.
A full card copy captures files present on that card. It is not automatically a dump of an original cartridge's battery-backed memory, nor a backup of every internal device setting. For valuable cartridge progress, identify the documented method and compatible hardware needed to read that cartridge separately.
Organizing games without breaking saves
The Assets and Saves hierarchies are intended to correspond. If you reorganize one, investigate the other before launching and saving again. Keep the old backup intact until the game locates its expected progress. Do not let a blank new save overwrite a missing old one while experimenting with paths.
Use a small catalog with original filename, platform, core and any required companion files. Keep original downloads or personal dumps unchanged and perform conversions on copies. If two versions of a game use the same display name, add enough notes to identify their actual files and the saves created for each.
GB Studio and Memories boundaries
Analogue documents Pocket's GB Studio area for .pocket games and its separate Saves folder. Follow that route for a compatible exported project rather than dropping an arbitrary ROM into the folder. Read the current directory documentation when changing organization.
A core must provide the relevant state behavior for Memories to be useful. Test creating and loading a snapshot at an unimportant checkpoint, then test the game's ordinary saving independently. Maintain both where supported. Do not infer support from the fact that the menu offers the feature elsewhere on the device.
When a card seems faulty
Preserve readable files before repair or formatting. Compare a spare card with a minimal known working installation, and record whether the failure affects one core, all cores or file copying on the computer. Return to firmware and core setup when a version or layout mismatch is likely.
Sources and review
Reviewed October 11, 2026. The linked manufacturer and project documentation establishes supported behavior. The diagnosis checklists and preservation suggestions are original editorial guidance. Menus, services and project support can change; verify the linked instructions before an irreversible change.