Verified facts
What is confirmed
| Battery save | Created through the game's original save behavior |
|---|---|
| Save state | Snapshot of emulator runtime state |
| Version sensitivity | Save states can depend on core and app version |
| Automatic cross-device sync | Not claimed as verified |
| Backup | User responsibility |
Facts last verified
Steps
How to proceed
- Use the game's own saveCreate a battery save when the title supports it.
- Create save states deliberatelyUse states for convenient checkpoints, not as the only long-term backup.
- Label and testConfirm that a state loads before relying on it.
- Back up important dataUse your preferred operating-system backup workflow.
- Re-test after updatesCore or app changes can affect save-state compatibility.
Boundaries
What SpatialEMU does not provide
- Games, ROMs, BIOS files, firmware, and third-party download catalogs are not included.
- Users must provide files they have the right to use.
- Cross-device save synchronization is not currently claimed as a verified feature.
- SpatialEMU does not currently claim a built-in recording feature.
- Intel Macs are not supported.
- The Windows installer is currently unsigned.
- Android is in development and is not available for download.
FAQ
Common questions
Which save type is more portable?
Battery saves are generally closer to original game behavior, but portability still depends on the emulator and file format.
Do saves sync across devices?
SpatialEMU does not currently claim verified automatic cross-device save synchronization.
Can an update break a save state?
Save states may be sensitive to core and app-version changes, so keep separate backups.