SideSave
github.com
What it is
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.
Spec sheet
- Purpose
- SideSave syncs save data for non-Steam games added to Steam as shortcuts between two specific machines, peer-to-peer.Read 7 Oct 2026 · github.com
- 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.Read 7 Oct 2026 · github.com
- Support
- The user guide directs users to the SideSave Discord for help and GitHub Issues for bug reports.Read 7 Oct 2026 · github.com
- Availability
- The fork does not publish releases and instructs users to build it from source.Read 7 Oct 2026 · github.com
- 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.Read 7 Oct 2026 · github.com
- Cloud credentials
- OAuth tokens for backup providers are stored locally and are not sent to the SideSave project.Read 7 Oct 2026 · github.com
- Conflict handling
- When independently changed saves conflict, SideSave asks the user whether to keep the local version, remote version, or both.Read 7 Oct 2026 · github.com
- Data handling
- The relay routes WebSocket frames and says it writes no save data to disk or retains it after a device disconnects.Read 7 Oct 2026 · github.com
- Delta transfer
- SideSave hashes content-defined blocks and transfers only blocks that changed.Read 7 Oct 2026 · github.com
- 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.Read 7 Oct 2026 · github.com
- History
- It stores versioned snapshots with branches and supports restoring saves or individual files from snapshots.Read 7 Oct 2026 · github.com
- History and conflicts
- The sync engine supports snapshot history and branches, and detects conflicts through sync lineage for user resolution.Read 7 Oct 2026 · github.com
- Install options
- The repository documents building a CLI and daemon, a desktop app, a relay server, and a Steam Deck Flatpak and Decky plugin.Read 7 Oct 2026 · github.com
- 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.Read 7 Oct 2026 · github.com
- Optional backup integrations
- Cloud Backup can mirror snapshots to Google Drive, Dropbox, OneDrive, WebDAV, a webhook, or a local/NAS folder.Read 7 Oct 2026 · github.com
- Pairing
- Devices sync only after explicit pairing approval, and users can unpair a device from the Devices screen.Read 7 Oct 2026 · github.com
- 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.Read 7 Oct 2026 · github.com
- Pricing
- The project describes itself as free and open source, and its user guide says it has no subscriptions.Read 7 Oct 2026 · github.com
- 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.Read 7 Oct 2026 · github.com
- Save detection
- It identifies non-Steam shortcuts through Steam’s shortcuts.vdf file and offers their Proton save locations for tracking.Read 7 Oct 2026 · github.com
- 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.Read 7 Oct 2026 · github.com
- Sync
- Tracked saves sync between paired devices over LAN or through an internet relay using changed-block transfers and versioned snapshots.Read 7 Oct 2026 · github.com
Plans and prices
Strong points and limits
Strong points
- Free, open-source project with no subscriptions
- Changed-block transfers reduce repeated save data
- Versioned snapshots support restoring files
- Works over LAN or internet relay
- Optional backups include Google Drive and NAS folders
Limits
- No published releases; building from source is required
- Scope excludes emulator and portable-install saves
- Relay encryption is not end-to-end
Who it suits
It suits Linux and Steam Deck users managing non-Steam shortcut saves across two paired devices. It is also relevant to users wanting local or optional cloud snapshot backups without accounts.
Verdict
SideSave offers detailed peer-to-peer save synchronization with history and conflict choices. Its source-build distribution and defined detection limits matter before setup, especially for users outside supported shortcut workflows.
Where Specifiction places it
- Game Save Managers#12 of 277.9