Save states are one of emulation’s most convenient features, but they are also easy to misunderstand. A state is closer to freezing the whole virtual machine at one moment than writing a normal save file the original game understands.
Save states capture emulator state
A state can include memory, processor state and emulator-specific information. That is why it can resume at a precise moment even when the original game had no save feature.
In-game saves are often more portable
A normal battery or memory-card save follows the original game’s logic and may be easier to move between compatible emulators. Save-state files can depend on emulator version and settings.

Do not keep only one state
If a system supports multiple slots, rotate two or three for longer games. One bad or accidental state should not erase hours of progress.
Back up before firmware changes
Updating or replacing a system image can change folder paths or emulator versions. Copy important save and state folders before an update if the device exposes them safely.
Test restoration before trusting a backup
A backup is only useful if you can restore it. After copying saves, verify at least one non-critical game on the target setup before assuming everything migrated correctly.
Compare setup styles in our Retro Gaming Guides, or check the live G11 Pro product page for current storage, price and verified box contents.
