- Top Pick: Samsung T9 Portable SSD 2TB
- Runner-up: SanDisk Extreme PRO Portable SSD 2TB
- Also consider: Crucial X9 Pro 2TB Portable SSD
Playing the same library on a Windows PC and a Linux machine sounds like it should be one continuous save file, and Steam Cloud is the feature meant to deliver exactly that. Sometimes it does. Sometimes you boot the other operating system and find a character who is hours younger than the one you left, or a settings screen that has forgotten everything, with no error anywhere to explain what happened.
This guide is a behaviour map, not a repair manual. Our separate Linux save-backup guide covers local copies with Ludusavi, and our Steam Cloud error guide covers fixing sync failures. This article sits between them: how Steam Cloud decides which files belong to which operating system, the three mismatch patterns that split one playthrough into two, how to read the conflict prompt, and the routine that keeps a dual-boot setup honest.
As an Amazon Associate, we earn from qualifying purchases.
Quick answer
Steam Cloud follows the paths each developer configured for each operating system, so the same game can keep one save set on Windows and another on Linux without either side seeing the other. Proton games usually roam cleanly because both sides run the Windows build. The safe routine is simple: let every session finish uploading before you switch systems.
How Steam Cloud maps files per operating system
Steam Cloud is not a folder mirror. It is a per-game configuration, written by the developer, that lists which local files get uploaded and which directory each operating system should read them back from. Valve’s Auto-Cloud system works with named roots: a developer points at a standard location such as the Windows documents folder, the Windows application data folders, the Linux home directory, or the Linux XDG data directory, then adds a subdirectory and a file pattern. When you finish a session, the client uploads the files matching the pattern for your current operating system. When you launch on the other system, it downloads into the path mapped for that system.
Three consequences follow. First, the mapping is only as good as the developer’s configuration. If a native Linux port was added later and nobody extended the cloud configuration to the Linux path, the cloud faithfully syncs the Windows saves while the Linux build uses a local directory that was never enrolled.
Second, Proton changes the picture completely. A Windows game running through Proton sees a simulated Windows directory tree inside its prefix, so the save paths are the Windows paths, and the developer’s Windows mapping applies unchanged. That is why Proton titles are usually the best-behaved roamers in a mixed library: from the game’s point of view, both systems are the same environment.
The three mismatch patterns that split progress
The path split
The classic failure for native ports. The Windows build saves into a folder under the user’s documents or application data, and the cloud configuration maps that location. The Linux build saves into a hidden folder under the home directory, and that location was never added to the configuration, or was added with a pattern that does not match the files the port actually writes. Each system keeps its own set, and the two playthroughs drift apart invisibly, while both machines report a successful sync.
The format split
Here the paths are mapped correctly on both sides and the files genuinely roam, but the builds do not agree on what is inside them. Settings files are the most common casualty: a configuration file written by the Windows build carries display and input values the Linux build interprets differently, so your resolution, key bindings, or graphics options reset every time you change machines. The sync works perfectly; it delivers a file the other build only half understands. Treat synced settings as a known cost of roaming in affected games.
The version split
Ports do not always update in step. When the Windows build receives a patch that changes the save format and the Linux build is a version behind, the older build can refuse the newer save, ignore it, or overwrite the cloud copy with an older-format file on exit. A save written by a newer build is a one-way door: if a patch has landed on one system only, finish nothing important on the other until both builds match, and keep a manual copy of the save folder before the first launch after any update.
The conflict prompt, decoded
When both the local files and the cloud files have changed since the last successful sync, Steam stops and asks which set to keep, showing modification times for each. Those timestamps are the whole diagnosis. The side with the most recent time is almost always the session you played last; the other side is usually an older state touched by a launch or an interrupted upload rather than a real session.
Conflicts are manufactured predictably: closing the client or losing the connection before an upload finishes, playing offline on one machine and then online on the other, or launching the game on the second system before the first has uploaded, so the launch download pulls the stale set down and marks it current. The prompt is not an error. It is the client admitting it cannot tell which of two changed states is real, and the timestamps are how you tell it.
Beyond Steam: the per-store reality
Steam is the only store whose cloud system was designed with this cross-platform mapping layer, and even it depends on per-game configuration. Elsewhere, expectations should be lower. GOG’s Galaxy cloud saves are a feature of the Galaxy client, which has no native Linux version; community launchers on Linux provide cloud support for many games, but coverage is per title and should be verified game by game. The Epic Games Store supports cloud saves for enabled titles, reachable on Linux through community launchers, with the same caveat. Saves attached to publisher launchers, such as the EA app or Ubisoft Connect, are the least portable: the cloud copy is tied to that publisher’s client, and a Linux route may or may not read the same location. The summary: Steam Cloud covers most of a Steam library well, everything else is a patchwork, and any game you care about deserves a manual save-folder copy regardless.
The dual-boot save routine
Let the upload finish before you switch. After quitting a game, wait until the client shows the game as synced rather than shutting down or rebooting immediately; on a dual-boot machine, let the sync complete before restarting into the other operating system.
Never open the same game on the second system first. Launch order matters: the system you played on uploads, then the other downloads at launch. Reversing that order promotes stale saves.
Keep one manual vault. Once a week, or before any system change, copy the save folders for the games in progress to an external drive or a home server share. A fast portable SSD makes this a two-minute job; a small NAS makes it automatic. And remember: local saves for games without working cloud sync live inside the Proton prefix, so deleting or rebuilding a prefix takes them with it — snapshot the folder first.
How to choose
Your habits should match your play pattern. If you roam between a Windows desktop and a Linux laptop with mostly Proton games, the defaults are already on your side; your only jobs are the upload pause and the weekly vault copy. If your library leans on native Linux ports, audit the important ones: launch each game once on both systems, confirm the continue screen matches, and put any game that fails on the manual-copy list permanently. If you dual-boot one machine, reboot discipline matters more than any tool.
Who should skip this
Single-system players can skip all of it: if a game never leaves one operating system, none of these mismatch patterns can occur. And if a game’s saves are stored server-side by the game itself, as with most large online titles, your progress follows your account and this topic is moot. This guide is for the overlap: two operating systems, one library, and saves you would be annoyed to lose.
The manual vault: drives worth owning
Samsung T9 Portable SSD 2TB
The fast option for a vault that lives in a bag. Its maker-rated speeds are the highest here, so a full save-folder copy finishes quickly enough that the habit survives.
Specs:
– Capacity: 2TB
– Interface: USB 3.2 Gen 2×2, USB-C
– Maker-rated speeds: up to 2,000 MB/s read and write
– Model: MU-PG2T0B/AM
SanDisk Extreme PRO Portable SSD 2TB
Specs:
– Capacity: 2TB
– Interface: USB-C, USB 3.2 Gen 2×2
– Maker-rated speeds: up to 2,000 MB/s read and write
– Model: SDSSDE81-2T00-G25
– Resistance: IP65 water and dust
Crucial X9 Pro 2TB Portable SSD
Specs:
– Capacity: 2TB
– Interface: USB-C, USB 3.2 Gen 2
– Maker-rated speeds: up to 1,050 MB/s read and write
– Model: CT2000X9PROSSD902
– Resistance: IP55 water and dust
WD Black P40 Game Drive SSD 2TB
Specs:
– Capacity: 2TB
– Interface: USB 3.2 Gen 2×2, USB-C
– Maker-rated speeds: up to 2,000 MB/s
– Model: WDBAWY0020BBK-WESN
– Extras: RGB lighting, two-metre drop rating per the maker
Synology DiskStation DS224+
The stay-at-home vault. A two-bay NAS gives both operating systems one always-on archive for saves, with scheduled backups doing the remembering. Drives are sold separately.
Specs:
– Bays: 2, for 3.5-inch or 2.5-inch SATA drives
– Processor: Intel Celeron J4125 quad-core
– Memory: 2GB DDR4, expandable to 6GB
– Network: two Gigabit Ethernet ports
– File systems: Btrfs and EXT4
FAQ
Why does my game show as synced but my progress is older on Linux?
That is the path split. The cloud syncs the Windows save location correctly, but the Linux build reads a different folder that was never mapped into the game’s cloud configuration, so each system keeps its own progress.
Are Proton games safer for cloud saves than native ports?
Usually, yes. A Proton game uses the same Windows save paths on both systems, so the developer’s Windows cloud mapping applies unchanged. The Proton-specific risk is local: deleting or rebuilding the prefix removes local saves for any game whose cloud sync is not working.
The conflict prompt appeared. Which side do I pick?
Compare the modification times in the dialog and pick the more recent side, which is normally the last session you actually played. The older side is usually a state touched by a launch or an interrupted upload, not real progress.
Can I rely on cloud saves when I reinstall or change Linux distributions?
Only partly. Cloud saves restore what was uploaded, and only into the paths the developer mapped. A manual vault copy taken before the reinstall covers the games whose cloud configuration is incomplete, exactly the set you cannot identify in advance.
Final verdict
Steam Cloud is a per-game mapping exercise, not a safety net, and dual-system players feel that distinction first. Proton titles roam well because both sides share one save location. Native ports roam exactly as well as their developer configured them to, and the path, format, and version splits explain every case where they do not. Read the conflict prompt’s timestamps instead of fearing it, let uploads finish before you switch systems, and keep one manual vault. Do those three things and your progress will be on whichever machine you sit down at.











