OpenSave vs SaveState

OpenSave syncs game saves among a user's devices, including emulator saves and games outside Steam Cloud. It can identify games using an offline, community-maintained index of more than 20,000 titles, or track a folder or file selected by the user. Devices can find each other over the same Wi-Fi or pair over the internet with a room code, without an account or port forwarding. OpenSave keeps versioned snapshots and supports rollback and branches; when it finds conflicting saves, it asks the user how to resolve them. Optional snapshot backups can go to Google Drive, Dropbox, OneDrive, WebDAV, or a NAS folder. On a LAN, devices communicate directly. Internet syncing uses an encrypted connection to a stateless relay, but the encryption ends there and the relay could read forwarded data. Users can self-host the relay and manage its daemon and CLI through a local REST/WebSocket API. It is free and MIT-licensed, with Windows, Linux, Steam Deck, and macOS options. On a stock Steam Deck, the Linux tarball will not start; the site recommends the Flatpak.

SaveState is a graphical app for backing up and restoring video game saves, including games without cloud saves. It creates compressed ZIP backups, offers one-click backup and restore, and can rotate older backups automatically. Users can drop a game launcher shortcut onto the app to detect a game and search for its save folder. The desktop app supports Steam, Epic, GOG, Battle.net, Ubisoft, EA App, Playnite, and Heroic, as well as save discovery for emulators including RetroArch, Dolphin, ares, DuckStation, PPSSPP, and PCSX2. SaveState is free and GPLv3-licensed. Local backups need no account or configured provider; optional synchronization supports Google Drive, WebDAV, FTP/FTPS, SMB or network folders, and Git. Desktop releases are offered for Windows and Linux. Release notes describe Dolphin directory discovery for macOS locations. A separate Android app is in pre-release alpha and supports emulator detection, save scanning, ZIP backup and restore, and profile management. Some emulator saves in protected Android/data paths require a rooted device and superuser access through Root mode. The project describes preflight validation, staged extraction, atomic installation, and attempted rollback if replacement fails.