Hoard vs SaveState

Hoard syncs game saves across devices and keeps versioned backups on Linux, macOS, Windows, or a self-hosted setup. It detects when you stop playing and syncs saves automatically. If two machines have diverging saves, the newest takes precedence and the other is backed up locally. Snapshots are retained indefinitely, and users can restore an earlier version. Hoard checks files with SHA-256 and re-hashes them during restoration. It detects libraries including Steam, Epic, GOG, Proton, and Wine, and uses the Ludusavi manifest for thousands of titles; the site says save paths for 71 games have been checked by hand. Save export in the game's original format is available even on the free tier. The Free plan includes 2 GB of cloud storage, a maximum save size of 1–1.5 GB, and three devices. Hoard Pro costs €1.99 per month and includes 100 GB of storage, saves up to 10 GB, and unlimited devices. Hoard can also be self-hosted using the same Rust binary, without an account or quotas.

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.