QSave vs SaveState

QSave backs up video game save files to the user’s own Google Drive. It is free and open source, with downloads for Windows and macOS, including separate Apple Silicon and Intel Mac versions. Its game detection database supports more than 19,000 games, and the home page lists Steam, GOG, Epic and Battle.net. QSave searches installed games, and users can search and filter by those stores. Unsupported games can be added by selecting their save folder. Backups can be restored from Google Drive with one click. Cross-platform path remapping is intended to help carry saves between computers, and users can restore cloud-only games or choose a custom restore location. QSave keeps up to five backups per game, skips uploads when save files have not changed, and warns about possible restore or sync conflicts. Individual cloud backup versions can be deleted. The app can run in the system tray and optionally launch at startup. Windows and macOS may show an installation warning because QSave’s code-signing certificates cost money each year; Ko-fi contributions help fund those certificates.

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.