Hg.SaveHistory vs SideSave
Hg.SaveHistory
github.comSideSave
github.comSide by side
| Figure | Hg.SaveHistory | SideSave |
|---|---|---|
| Price from | — | Free |
| Free plan | — | Yes |
| Free trial | — | — |
| Open source | — | — |
| Windows | Yes | — |
| Linux | — | Yes |
| API | — | Yes |
| Self-hosted | — | Yes |
| Plans published | 0 | 1 |
| Spec score · Game Save Managers | 6.8 (#25) | 7.9 (#12) |
| Purpose | Hg.SaveHistory creates snapshots of game save files or other files. | SideSave syncs save data for non-Steam games added to Steam as shortcuts between two specific machines, peer-to-peer. |
| Support | The README asks users to report issues and says a log file named Hg.SaveHistory.log is located in the application folder. | The user guide directs users to the SideSave Discord for help and GitHub Issues for bug reports. |
Plans
In their own words
Hg.SaveHistory
Hg.SaveHistory has no write-up on Specifiction yet; its figures are above.
SideSave
SideSave is free, open-source software that synchronizes save data for non-Steam games added to Steam as shortcuts. It pairs two approved machines and transfers tracked saves over a local network or an internet relay, sending only changed content blocks. Versioned snapshots and branches preserve history, while lineage-based conflict detection asks whether to keep the local copy, remote copy, or both. Saves can be restored individually or as complete versions. Detection reads Steam’s shortcuts.vdf file and offers Proton save locations for tracking. The scan excludes real Steam Cloud games, emulator saves, repack-wrapper detection, and portable installs. Optional backups can mirror snapshots to Google Drive, Dropbox, OneDrive, WebDAV, a webhook, or local/NAS storage. SideSave has no accounts or telemetry; relay traffic is encrypted but not end-to-end. The project publishes no releases, so users build the CLI, desktop app, relay, or Steam Deck components from source.