- Home
- Game Save Managers
- SideSave
SideSave
What it is
SideSave is a free, open-source tool for syncing save data from non-Steam games added to Steam as shortcuts between two paired machines. It can sync over a local network or through an internet relay, transferring changed blocks and keeping versioned snapshots. Snapshot history, branches, and conflict detection let users review save changes; when independently changed versions conflict, users can choose the local version, remote version, or both. The scan identifies non-Steam shortcuts through Steam’s shortcuts.vdf file and offers their Proton save locations for tracking. It excludes Steam Cloud games, emulator saves, repack-wrapper detection, and portable installs. Optional backup destinations include Google Drive, Dropbox, OneDrive, WebDAV, a webhook, or a local or NAS folder. SideSave says it has no accounts or telemetry, and local saves remain in configured folders unless cloud backup is enabled. Relay traffic is encrypted but not end-to-end, so the relay operator can read save data in transit. The fork publishes no releases, so users build it from source; documented options include command-line and desktop tools, a relay, and Steam Deck integrations.
For and against
For
- Free and open source with no subscriptions
- Syncs over LAN or an internet relay
- Keeps versioned snapshots and branches
- Supports manual conflict choices and restores
- Offers optional cloud-backup providers
Against
- No published releases; users build from source
- Relay encryption is not end-to-end
- Google Drive OAuth credentials may expire weekly
- Scheduled backups are not supported
The verdict
SideSave combines peer-to-peer save syncing with snapshot history and manual conflict handling for its defined shortcut-based scope. Users should account for the source-build requirement and the relay’s lack of end-to-end encryption.
Who it suits
SideSave suits users who want to sync tracked non-Steam game saves between two approved machines and manage save history or conflicts. It requires building from source because the fork does not publish releases.
Plans and prices
Free
No accounts or subscriptions stated · build from source; no published releases
Read 7 Oct 2026 · github.com
On the record
- Availability
- The fork does not publish releases and instructs users to build it from source.github.com · read 7 Oct 2026
- Cloud backup integrations
- Optional cloud-backup providers listed in the privacy policy are Google Drive, Dropbox, OneDrive, WebDAV, a webhook, and a local or NAS folder.github.com · read 7 Oct 2026
- Cloud credentials
- OAuth tokens for backup providers are stored locally and are not sent to the SideSave project.github.com · read 7 Oct 2026
- Conflict handling
- When independently changed saves conflict, SideSave asks the user whether to keep the local version, remote version, or both.github.com · read 7 Oct 2026
- Data handling
- The relay routes WebSocket frames and says it writes no save data to disk or retains it after a device disconnects.github.com · read 7 Oct 2026
- Delta transfer
- SideSave hashes content-defined blocks and transfers only blocks that changed.github.com · read 7 Oct 2026
- Google Drive limitation
- The user guide says the built-in Google Drive OAuth credentials may expire weekly and suggests using a custom client ID or another backup provider for always-on cloud sync.github.com · read 7 Oct 2026
- History
- It stores versioned snapshots with branches and supports restoring saves or individual files from snapshots.github.com · read 7 Oct 2026
- History and conflicts
- The sync engine supports snapshot history and branches, and detects conflicts through sync lineage for user resolution.github.com · read 7 Oct 2026
- Install options
- The repository documents building a CLI and daemon, a desktop app, a relay server, and a Steam Deck Flatpak and Decky plugin.github.com · read 7 Oct 2026
- Local data
- The privacy policy says saves and snapshots stay on the user's machine in configured storage folders unless the user opts into cloud backup.github.com · read 7 Oct 2026
- Optional backup integrations
- Cloud Backup can mirror snapshots to Google Drive, Dropbox, OneDrive, WebDAV, a webhook, or a local/NAS folder.github.com · read 7 Oct 2026
- Pairing
- Devices sync only after explicit pairing approval, and users can unpair a device from the Devices screen.github.com · read 7 Oct 2026
- Platforms and installation
- The repository documents building the CLI, desktop app, and relay from source, and describes a Steam Deck Flatpak and Decky Loader plugin; it says the fork publishes no releases.github.com · read 7 Oct 2026
- Pricing
- The project describes itself as free and open source, and its user guide says it has no subscriptions.github.com · read 7 Oct 2026
- Privacy
- SideSave says it has no accounts or telemetry and does not upload saves to third parties unless the user enables Cloud Backup and chooses a provider.github.com · read 7 Oct 2026
- Purpose
- SideSave syncs save data for non-Steam games added to Steam as shortcuts between two specific machines, peer-to-peer.github.com · read 7 Oct 2026
- Relay security
- The privacy policy says relay connections are encrypted but not end-to-end, so the relay operator can read save data passing through the relay.github.com · read 7 Oct 2026
