You finish a six-hour Valheim build session, shut down your PC, and open the game on your laptop. Steam politely announces a Cloud conflict. One option has the save from five minutes ago. The other has the save you actually want. Pick wrong and your longhouse, tamed wolves, and questionable bridge engineering are gone.
So, can Steam Cloud lose progress? Yes. Steam Cloud is useful, but it is a sync service, not a time machine. It can copy the wrong version, fail to upload a recent change, or preserve a corrupted save because that is the file it was given. If a game only keeps one active save file, Steam Cloud can faithfully spread that disaster to another machine.
That does not make Steam Cloud useless. It means it needs to be understood for what it is: convenient synchronisation, with limits that become painfully obvious after 200 hours of progress.
Can Steam Cloud lose progress during a sync?
It can, particularly when two devices disagree about which save is newest. Steam usually compares timestamps and file states, then attempts to choose the sensible version. Usually is doing a lot of work there.
A sync conflict happens when you play a game on one PC, then launch it elsewhere before the first device has fully uploaded its save. It can also happen after playing offline, using a handheld while travelling, reinstalling Windows, or closing a game while its save is still being written. Steam may ask which version to keep, but its labels are not always as comforting as they should be. “Local files” and “Cloud files” are not the same thing as “good save” and “bad save”.
Even if you choose correctly, some games store progress across several files: a main save, metadata, world data, player data, configuration files, mod lists, or a separate profile folder. If only part of that set syncs properly, the result can range from missing settings to a save that refuses to load.
Steam Cloud also has no magical knowledge of your session. If your game crashes and writes damaged data, the service may upload the damaged version. Congratulations: the corruption is now on both machines.
The ways Steam Cloud progress goes missing
The most common problem is not a dramatic server meltdown. It is ordinary save behaviour colliding with ordinary human behaviour.
An older device overwrites the newer save
Say your desktop has your latest Stardew Valley farm. Your laptop has an older copy from last month. You launch the laptop while offline, play for ten minutes, then reconnect. Now both machines have changed versions, and Steam has to sort out a family argument it was never designed to mediate.
If the older save wins, your newer progress can disappear from the active game folder. It may still exist somewhere temporarily, but Steam Cloud does not promise a browsable archive of every previous state. That distinction matters.
The game does not support all save files
Steam Cloud support is set by each game developer. Some games sync everything you need. Others only sync a slice of the save data, or they use their own cloud system instead. A game can display the Steam Cloud badge and still leave mod files, local worlds, screenshots, settings, or companion data on your machine.
This is especially spicy with modded games. A save may technically sync, but the receiving PC lacks the same mods, load order, dependencies, or configuration. The save opens into a missing-item graveyard, crashes on load, or behaves like a raccoon got access to the database.
Cloud storage limits get in the way
Steam Cloud storage is not infinite, and game-specific quotas vary. Large worlds, frequent saves, replay data, or save folders packed with backups can hit limits. When that happens, sync errors may be obvious, but not always noticed before you move to another device.
Do not assume the small green Cloud status means every file you care about is protected forever. Check the game’s actual save location and what it writes there.
A bad save is synchronised perfectly
A power cut, game crash, forced shutdown, unstable mod, or dodgy drive can corrupt a save. Steam Cloud may then upload it with admirable efficiency. Sync is duplication of the current state, not version history.
That is the central weakness: if yesterday’s working save is replaced by today’s broken one, a normal sync system sees no problem. You do.
What Steam Cloud is good at - and what it is not
Steam Cloud is brilliant for moving supported saves between your own devices with minimal effort. For smaller single-player games, that may be all you need. Finish a run on your desktop, continue it on your Steam Deck, carry on living your best portable-goblin life.
It is less reliable as your only line of defence when the save is valuable, complicated, or shared. Think Factorio factories, Minecraft worlds, Satisfactory production lines, Elden Ring characters, emulator memory cards, and any modded setup held together by careful load order and optimism.
It also does not solve co-op ownership. If one person hosts a world locally, Steam Cloud typically syncs that world to their devices, not automatically to every member of the group. Your mates cannot safely take over just because everyone owns the game. The host remains the host, and the save remains trapped on their machine unless someone manually sends it around.
Manual copying works, until it does not. Someone forgets which folder is current. Someone renames `world_final_FINAL_reallyfinal`. Someone uploads an old copy to the group chat. Then Tuesday night becomes a forensic investigation instead of game night.
How to stop a Steam Cloud conflict becoming a wipe
Start by treating the conflict prompt as a warning light, not a quick nuisance to dismiss. If Steam reports that local and Cloud files differ, do not launch the game immediately. Copy the entire local save folder somewhere safe first. Then you can compare dates, file sizes, and folder contents without gambling the only copy.
Before switching devices, close the game normally and wait for Steam to finish syncing. Check that Steam is online and that no sync error is shown in the library. This sounds painfully basic because it is painfully basic - and it prevents a surprising number of losses.
For games with worlds, mods, or multiple save components, back up the complete folder rather than one obvious file. A lone `.sav` file may depend on adjacent data. Copying only the shiny thing in the folder is how people create a backup that looks real right until restore day.
Keep at least a few dated versions. Not just one backup that gets overwritten every time. Version history gives you choices: the save before the crash, before the mod update, before your friend “tidied” the storage system, or before you accidentally sold the one quest item the game considers sacred.
For a hands-off approach, Checkpoint64 watches supported save folders, keeps every changed version, and lets you restore an earlier state in seconds. Its free plan is actually free, while more storage is a pay-once upgrade - no subscription and no “powered by AI” glued to a file copy button. The useful bit is not merely having another copy. It is being able to go back to the copy from before things went sideways.
Recovering progress after Steam Cloud has overwritten it
First, stop launching the game on every device. Each launch can create another save, sync another state, and make the trail messier. Disable automatic sync for that game temporarily if you can do so without triggering another overwrite, then preserve the save folders from every device involved.
Look for local backups made by the game itself. Some games keep `.bak` files, rolling save slots, recovery folders, or dated snapshots. Check the game’s save directory, not just Steam’s Cloud storage. If you use Windows File History, macOS Time Machine, Linux snapshots, or a backup tool with version history, this is their moment to earn their keep.
If the only intact copy is on a device that has not connected yet, keep it offline until you have copied the save folder somewhere else. Do not let an older or broken Cloud state rush in and overwrite your best evidence.
Recovery is possible more often than people think, but it depends on whether an older version exists somewhere. That is why backups are boring right up until they are the most exciting thing in the room.
Steam Cloud is great for convenience. Let it handle convenience. For saves you would genuinely hate to lose, keep independent, versioned copies as well. Your future self should not have to choose between two mystery timestamps while a 200-hour world hangs in the balance.