- Top Pick: Valve Steam Deck OLED 512GB
- Runner-up: NETGEAR 16-Port Gigabit Ethernet Unmanaged Switch (GS316)
- Also consider: Synology DiskStation DS224+
Steam Cloud is generous right up to the moment it is not. It covers enabled Steam titles well, but it does nothing for GOG and itch.io installs, emulator saves, or the native Linux ports whose save folders were never enrolled in a developer’s cloud configuration. Play on a desktop and a Steam Deck and those uncovered games strand their progress on whichever machine you used last.
The fix is to stop asking stores to sync your saves and sync the folders yourself. Syncthing is a free, open-source tool that keeps nominated folders identical across your own machines, directly device to device, with no account and no third-party server holding your files. Paired with Ludusavi, which knows where thousands of games keep their saves, it turns save syncing into a ten-minute setup and a few rules you must not break.
As an Amazon Associate, we earn from qualifying purchases.
Quick answer
Install Syncthing on every Linux machine you play on, including the Steam Deck, then share only the save folders Ludusavi identifies for the games Steam Cloud misses. Keep both machines on your home network, enable file versioning, and never let a sync run while the game is open. Your saves then follow you between desktop and Deck automatically.
Where your saves actually live on Linux
Syncing the wrong folder is the most common way this goes wrong, so start with the geography. Native Linux games usually follow the XDG conventions: saves and profiles sit under the data directory in your home folder, most often in a per-game subfolder of the local share directory, while settings live under the config directory. Plenty of games ignore the conventions and write into a hidden folder named after the game or its engine; older titles may use the documents folder or the install directory.
Windows games running through Proton keep their saves inside the game’s prefix, a self-contained fake Windows drive that Steam builds per title. The path runs through the Steam library’s compatdata folder, into a subfolder named by the game’s app ID, then through the prefix’s drive_c and the steamuser profile, where the familiar Windows locations such as Documents and AppData are recreated. A save that a Windows player would find in their documents folder is in there, buried under six levels of directories. Emulators are simpler: RetroArch and the standalone emulators keep saves and save states in their own configurable directories, which makes them the easiest folders of all to sync.
Ludusavi exists to spare you the archaeology. It maintains a community database of save locations for thousands of games across stores, shows the exact paths it finds on your system, and backs them up on demand. Use it as the map even if Syncthing does the carrying: let Ludusavi tell you which folders matter, then point Syncthing at those folders and nothing else.
How Syncthing moves the files
Syncthing has no central server and no accounts. Each installation generates a device identity, and two machines sync only after each has accepted the other’s device ID, so pairing is a deliberate handshake rather than a sign-in. Once paired, you share a folder with a chosen device and both sides keep it identical: add a file on one machine and it appears on the other, delete it and the deletion travels too. That last part deserves emphasis, because it is where the risk lives. Syncthing is a mirror, not a backup. A corrupted or accidental deletion can propagate to every device before you notice, which is why the versioning settings below are not optional decoration.
Discovery and transport offer a privacy choice. On a home network, devices find each other locally and files move directly across your LAN at wire speed. Syncthing can also use public discovery servers and relays so machines find each other over the internet; the traffic stays encrypted end to end, but if your saves never need to leave the house, disabling global discovery and relays keeps the whole system inside your own walls. For a desktop-and-Deck household, LAN-only is the sensible default.
The conflict rules that keep saves alive
When the same file changes on two machines before they sync, Syncthing refuses to guess. It keeps the newer version under the original name and preserves the other as a conflict file with a sync-conflict marker in its name, dated and tagged with the device it came from. Nothing is silently destroyed, but the game will only ever read the file under the original name, so a conflict means one playthrough is parked in a renamed file until you sort it out by hand.
Four rules keep that rare. First, never sync a folder while its game is running on either machine; a save written mid-sync can arrive half-formed, and two live sessions guarantee a conflict. Quit the game, let the folder settle, then let sync finish before launching on the other machine. Second, turn on file versioning for every save folder; Syncthing’s staggered or simple versioning keeps dated copies of replaced files, which is your undo button when a bad sync lands. Third, sync saves, not whole games or whole prefixes; prefixes contain far more than saves and churn constantly. Fourth, give the Deck and the desktop the same folder paths relative to your home directory where you can, and use Syncthing’s ignore patterns for cache and log files so the sync stays small and quiet.
How to choose your setup
The right shape depends on how many machines play and when they are awake. A two-machine household, typically a desktop and a Steam Deck, needs nothing more than Syncthing on both and the save folders shared between them; the only discipline required is leaving both on the same network long enough for syncs to complete. If the machines are rarely on at the same time, add an always-on third node: a small NAS or a spare mini PC that never sleeps, so the desktop syncs to it when the Deck is off and the Deck catches up when it wakes. Choose wired connections for the desktop and the hub where you can, because save folders are small but game libraries of screenshots and replays are not, and keep the Deck’s sync set tight so its storage and battery are spent on games. Whatever the shape, decide in advance which machine wins when you break the rules and play offline on both: whichever save you check first, by the conflict file’s date.
The hardware that makes it painless
Valve Steam Deck OLED 512GB
The second screen in most Linux households and the machine that makes save syncing worth doing. Syncthing runs on the Deck as a Flatpak from Desktop Mode, and once configured it keeps working in the background while you play elsewhere.
Specs:
- Display: 7.4-inch HDR OLED, 1280 by 800, up to 90 Hz
- Storage: 512GB NVMe SSD, microSD expansion slot
- Connectivity: Wi-Fi 6E, Bluetooth 5.3
- Role in this setup: the portable endpoint that receives saves from the desktop
NETGEAR 16-Port Gigabit Ethernet Unmanaged Switch (GS316)
A wired backbone fixes the slow, relay-prone behaviour that gives syncing a bad name. The GS316 is a fit-and-forget unmanaged switch: plug the desktop, the hub, and your router into it and every sync travels at gigabit speed on your own LAN.
Specs:
- Ports: 16 gigabit Ethernet ports, unmanaged
- Model: GS316-300NAS
- Dimensions: 11.3 by 4 by 1.3 inches, 1.96 pounds
- Power: 8.1 watts maximum
- Mounting: desktop or wall mount
Synology DiskStation DS224+
The always-on third node for households whose machines are rarely awake together. A two-bay NAS that never sleeps can hold the shared save folders, run Syncthing as the sync endpoint, and double as the home for a Ludusavi backup archive.
Specs:
- Bays: 2 drive bays for 3.5-inch or 2.5-inch drives
- Processor: quad-core Intel Celeron J4125
- Memory: 2GB DDR4, expandable
- Network: two gigabit Ethernet ports
- Role in this setup: the always-on sync hub both players sync against
Samsung T9 Portable SSD 2TB
For the games and machines you would rather move by hand, a fast portable SSD is the honest fallback: copy the save folder onto it, walk it to the other machine, copy it off. It also earns its place as the target for periodic Ludusavi backup archives, kept away from the sync set so a bad mirror cannot reach it.
Specs:
- Capacity: 2TB, model MU-PG2T0B/AM
- Interface: USB 3.2 Gen 2×2, maker-rated up to 2,000 MB/s on a host that supports that mode
- Dimensions: 3.46 by 2.36 by 0.55 inches, 4.3 ounces
- Drop resistance: maker-tested to 9.8 feet
- Extras: password protection, two USB cables included
SanDisk 1TB Extreme microSDXC
A Deck loaded with native Linux games and emulator libraries fills its internal drive quickly, and synced save folders compete for the same space. A high-capacity microSD keeps the library on the card and the internal drive free for the prefixes and saves that sync best from fast storage.
Specs:
- Capacity: 1TB, model SDSQXAV-1T00-GN6MA
- Format: microSDXC, UHS-I
- App performance: A2 rated
- Role in this setup: bulk game storage that frees the Deck’s SSD for saves and prefixes
Who should skip this
Skip it if your whole library is Steam games with working cloud saves and you only ever play on one machine; there is nothing to fix. Skip it if the routine of closing a game and letting a sync settle sounds like friction you will abandon, because an abandoned sync setup is worse than none: stale folders and unresolved conflict files are how saves actually get lost. And skip the DIY route for any game whose saves you cannot afford to lose unless you also keep a separate Ludusavi backup, since syncing, however carefully configured, is a mirror and not an archive.
FAQ
Does Syncthing work on the Steam Deck without leaving Game Mode forever?
It installs through Desktop Mode as a Flatpak, and once it is set up it can be configured to start automatically, so day-to-day play stays in Game Mode. You only return to Desktop Mode when you want to change which folders are shared or review a conflict file.
What happens if I play the same game offline on two machines?
Both machines will hold a changed save, and when they next meet, Syncthing keeps the newer one live and preserves the other as a dated conflict file. Your older session is not deleted, but the game will not load it until you rename it back manually, so check the folder before launching.
Can Syncthing replace a save backup?
No. Syncing mirrors changes, including deletions and corruption, to every device. Pair it with Ludusavi’s backup feature or periodic copies to a drive outside the sync set, so a mistake on one machine cannot reach every copy you own.
Is it safe to sync a whole Proton prefix?
It is not recommended. A prefix holds registry files, caches, and the game’s full Windows environment, much of which changes every launch and some of which is machine-specific. Sync only the save folder inside the prefix that Ludusavi identifies, and leave the rest of the prefix to each machine.
Final verdict
For Linux players with more than one machine, Syncthing plus Ludusavi closes the gap Steam Cloud leaves: the non-Steam games, the unenrolled native ports, and the emulator libraries. The tooling is free and private by design, and setup takes an evening. What it asks in return is discipline: sync only save folders, enable versioning, never play on two machines at once, and keep a real backup outside the mirror. Follow those rules and your saves follow you from desk to sofa to Deck, which is all anyone wanted from cloud saves.










