SideSave
github.com
- Free plan
- Linux
- API
- Self-hosted
What SideSave is
SideSave is a free, open-source project for syncing saves from non-Steam games added to Steam as shortcuts between two paired machines. It can transfer tracked saves over a local network or through an internet relay, using changed-block transfers and versioned snapshots. Snapshot history and branches preserve earlier states; when separate edits conflict, SideSave lets users choose the local copy, remote copy, or both. It finds non-Steam shortcuts through Steam’s shortcuts.vdf file and offers their Proton save locations for tracking. Its scan does not cover real Steam Cloud games, emulator saves, repack-wrapper detection, or portable installs. Optional backup destinations include Google Drive, Dropbox, OneDrive, WebDAV, a webhook, or local/NAS storage. 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. The project publishes no releases; users build its tools from source. A Google Drive OAuth credential may expire weekly unless users configure a custom client ID or another provider.
Who it suits
SideSave suits users who manage non-Steam games as Steam shortcuts and are comfortable building software from source. It may also suit those who want paired-device sync, save history, or optional backup destinations.
Good to know, and what to watch
- Syncs over LAN or an internet relay
- Transfers only changed blocks
- Keeps snapshots and supports restoring files
- Offers several optional backup providers
- No accounts or telemetry
- No published releases; users must build from source
- Does not scan emulator saves or Steam Cloud games
- Relay traffic is not end-to-end encrypted
- Built-in Google Drive credentials may expire weekly
Plans
Every plan and priceFree
Free plan
The verdict
SideSave provides paired-device syncing and snapshot-based save recovery for a specific set of Steam shortcuts. Building from source and the relay’s lack of end-to-end encryption are important considerations.
What the maker publishes
- Availability
- The fork does not publish releases and instructs users to build it from source. source
- 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. source
- Cloud credentials
- OAuth tokens for backup providers are stored locally and are not sent to the SideSave project. source
- Conflict handling
- When independently changed saves conflict, SideSave asks the user whether to keep the local version, remote version, or both. source
- Data handling
- The relay routes WebSocket frames and says it writes no save data to disk or retains it after a device disconnects. source
- Delta transfer
- SideSave hashes content-defined blocks and transfers only blocks that changed. source
- 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. source
- History
- It stores versioned snapshots with branches and supports restoring saves or individual files from snapshots. source
- History and conflicts
- The sync engine supports snapshot history and branches, and detects conflicts through sync lineage for user resolution. source
- Install options
- The repository documents building a CLI and daemon, a desktop app, a relay server, and a Steam Deck Flatpak and Decky plugin. source
- 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. source
- Optional backup integrations
- Cloud Backup can mirror snapshots to Google Drive, Dropbox, OneDrive, WebDAV, a webhook, or a local/NAS folder. source
- Pairing
- Devices sync only after explicit pairing approval, and users can unpair a device from the Devices screen. source
- 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. source
- Pricing
- The project describes itself as free and open source, and its user guide says it has no subscriptions. source
- 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. source
- Purpose
- SideSave syncs save data for non-Steam games added to Steam as shortcuts between two specific machines, peer-to-peer. source
- 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. source
- Save detection
- It identifies non-Steam shortcuts through Steam’s shortcuts.vdf file and offers their Proton save locations for tracking. source
- Scope
- SideSave detects non-Steam Steam shortcuts and excludes real Steam Cloud games, emulator saves, repack-wrapper detection, and portable installs from its scan scope. source
- Support
- The user guide directs users to the SideSave Discord for help and GitHub Issues for bug reports. source
- Sync
- Tracked saves sync between paired devices over LAN or through an internet relay using changed-block transfers and versioned snapshots. source
Checked against the maker's pages on 7 Oct 2026.