GSBS vs SaveState

GSBS is a free game-save synchronization and backup service for Windows, Linux, and macOS. Clients connect through a central server, detect when a supported game is running, and wait to sync until it closes. The client checks game installations across Steam, Epic, GOG, Ubisoft, EA, Xbox, Heroic, Lutris, Bottles, and Prism against a PCGamingWiki manifest. It translates save paths between Windows and Linux, including Proton paths. Save files are versioned and can be restored through the web dashboard. Optional end-to-end encryption uses client-side AES-256-GCM with Argon2id; without that option, saves are plaintext on the server and in backups. Scheduled tar.zst snapshots can include the database, keys, and saves, with storage on local disk or S3. GSBS can send webhook, Discord, and ntfy alerts, including for conflicts, quota, and backups. The project recommends Docker Compose for the server and provides a Windows server setup executable. It is distributed under the MIT License.

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.