GSBS
What it is
GSBS is a game-save synchronization and backup service for Windows, Linux, and macOS, built around a central server and client apps. Its clients look for games across stores and launchers including Steam, Epic, GOG, Ubisoft, EA, Xbox, Heroic, Lutris, Bottles, and Prism, then wait until a detected game closes before syncing. GSBS can translate save locations between Windows and Linux, including Proton paths. It keeps versions of save files, which users can restore from a web dashboard. Optional end-to-end encryption protects saves with client-side AES-256-GCM and Argon2id; without it, save contents remain readable on the server and in backups. Scheduled tar.zst snapshots can include the database, keys, and saves, stored locally or on S3. Alerts can be sent through webhooks, Discord, or ntfy. The service is free under the MIT License, supports multiple users and devices, and recommends Docker Compose for server deployment; a Windows server setup executable is also available.
For and against
For
- Waits for games to close before syncing saves.
- Translates save paths across Windows and Linux.
- Versioned saves can be restored from the web dashboard.
- Scheduled snapshots can be stored locally or on S3.
- Optional client-side end-to-end encryption is available.
Against
- Saves are plaintext unless end-to-end encryption is enabled.
- Installers and binaries are not code-signed or notarized.
- Server deployment recommendation is Docker Compose.
The verdict
GSBS combines cross-platform save syncing with version history, restore, and scheduled backups. Users should account for its plaintext-by-default storage and unsigned installers when choosing how to deploy it.
Who it suits
GSBS suits people managing game saves across multiple Windows, Linux, or macOS devices, including desktop, laptop, and Steam Deck setups. It may also fit users who want to self-host and manage their own backups.
On the record
- API
- The web UI provides an OpenAPI specification at /api/openapi.json.github.com · read 29 Sep 2026
- Audience
- It supports multi-user, multi-device setups, including desktop, laptop, and Steam Deck clients.github.com · read 29 Sep 2026
- Backups
- Scheduled tar.zst snapshots can include the database, keys, and saves, and be stored locally or in S3; the server provides a restore command.github.com · read 29 Sep 2026
- Client platforms
- Clients are available for Windows, Linux including Flatpak and arm64, and macOS.github.com · read 28 Sep 2026
- Cross-platform paths
- GSBS translates save paths across Windows and Linux, including Proton paths.github.com · read 28 Sep 2026
- Deployment
- The maker recommends Docker Compose for the server and also documents pre-built Docker images and Linux or Windows server binaries.github.com · read 29 Sep 2026
- Encryption
- Optional end-to-end encryption uses client-side AES-256-GCM with an Argon2id key derivation, so the server sees ciphertext when enabled.github.com · read 29 Sep 2026
- Game-aware sync
- Clients detect running games and defer syncing until the game is closed.github.com · read 28 Sep 2026
- Game discovery
- The client scans Steam, Epic, GOG, Ubisoft, EA, Xbox, Heroic, Lutris, Bottles, and Prism against a PCGamingWiki manifest.github.com · read 29 Sep 2026
- History and restore
- Save files are versioned and can be restored from the web dashboard.github.com · read 29 Sep 2026
- Integrations
- GSBS can send webhook, Discord, and ntfy notifications, and supports S3 for offsite backups.github.com · read 28 Sep 2026
- License
- The repository identifies GSBS as MIT licensed.github.com · read 29 Sep 2026
- Notifications
- Webhook, Discord, and ntfy alerts cover conflicts, quota, new devices, backups, and stale devices.github.com · read 29 Sep 2026
- Purpose
- GSBS syncs game saves across Windows, Linux, and macOS using a central server and clients installed on each PC.github.com · read 29 Sep 2026
- Restore
- Save files are versioned, and users can restore files from the web dashboard.github.com · read 28 Sep 2026
- Security limitation
- Save contents are plaintext on the server and in its backups unless optional end-to-end encryption is enabled.github.com · read 28 Sep 2026
- Security limits
- Installers and binaries are not code-signed or notarized, and save content is protected only when optional end-to-end encryption is enabled.github.com · read 29 Sep 2026
- Security reporting
- The security policy asks users to report vulnerabilities privately to the maintainer and says reports are aimed to be acknowledged within 72 hours.github.com · read 29 Sep 2026
