Gamekeeper vs SaveState

Gamekeeper is a Windows utility for identifying game-save directories and recording gameplay saves. Metadata files help locate save folders when games are added, and local scans support batch importing. Users can create multiple save Spaces for each game and visualized branches for different storylines or career choices. Incremental storage keeps only data changed from the previous save. Quick Save supports hotkeys, process monitoring, real-time saving, and scheduled saving; saving a game also creates a screen preview. Saves can be uploaded to private cloud storage and started on another device. Rclone synchronization supports local, FTP, SFTP, WebDAV, SMB/CIFS, and S3 sources, while automatic recognition covers Steam, GOG Galaxy, Epic Game Store, and XBOX PC. The software is in alpha testing, without beta or stable versions. Downloads require Windows 10/11 64-bit, and Process Tracking requires the.NET 9 runtime. The free plan costs nothing and limits Multi-Space to three per game. Default upload limits are 10MB for images and 100MB for videos.

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.