The Moment You Realise Something Has Gone Wrong
You close the game after a twenty-hour session, walk away, and come back a week later on a different machine. The loading screen asks you a quiet, devastating question: which save do you want? The cloud version from six days ago, or the local one sitting on this hard drive? You pick the wrong one. Thirty hours, gone.
This is a save conflict. It happens constantly. It's almost never your fault, and most people never understand why it occurs. Understanding the mechanic won't undo your lost playthrough, but it will stop the next one.
Two Clocks That Don't Trust Each Other
Every save file carries a timestamp. When a sync service like Steam Cloud, PlayStation's cloud storage, or Xbox's cloud backup decides which save is the "correct" one, it compares those timestamps and picks the newer one. Simple, right?
Not even slightly.
Timestamps are written by the system clock on whatever device created the save. If your laptop's clock is twelve minutes fast, or if you crossed a timezone boundary, or if a battery replacement quietly reset the system time, your save file's timestamp is a lie. The sync service doesn't know that. It sees a file dated three hours in the future compared to the cloud copy, assumes that's the latest progress, and overwrites the correct save with it. The older-but-actually-newer file is gone.
This is the part most guides skip. It's not about internet speed or storage limits. It's a timestamp arbitration problem, and timestamps are surprisingly easy to corrupt.
The Three Scenarios Where This Gets Lethal
A handful of specific situations turn save conflicts from annoying to catastrophic.
Offline play followed by a sync. Say you take your Steam Deck on a long flight and log thirty-five minutes of progress in a game you'd also been playing at home. The Deck was offline the whole time, so nothing synced. The moment you reconnect to Wi-Fi, Steam Cloud wakes up and compares timestamps. If your home desktop ran the game briefly after your flight departed, an auto-update check that accidentally wrote a new save state, for instance, the desktop's newer timestamp wins. Your Deck progress is overwritten.
Two machines, same account, opened nearly simultaneously. Picture this: Marcus leaves his home PC running a game while he heads to a friend's place and logs into the same account on their PC. Both machines are writing save data. When both try to sync, the service has two conflicting "latest" files. Some services handle this gracefully. Many don't.
A game that saves constantly versus one that saves in chunks. Some games autosave every forty-five seconds. Others write a single save file only when you quit. If a constantly-saving game gets interrupted mid-write, by a power cut, a hard crash, even a force-quit, the partial file can be timestamped as newer than the last good cloud backup. The service dutifully syncs the corrupted file up, then back down to every device.
What People Get Wrong About This
The folk remedy that needs to die: "just always choose the cloud save." People repeat this as though the cloud version is inherently authoritative. It isn't. The cloud holds whatever was last synced, which might be an old save, a corrupted save, or a save from a different device that already stomped your best progress.
The other misunderstanding is assuming the conflict prompt is protective. When Steam or the PS5 asks "which save would you like to use," it feels like a safety net. It really isn't. You're being asked to make a technical decision with almost no useful information. The prompt usually shows a timestamp and sometimes a playtime counter, but it rarely tells you why they differ or which machine wrote which file. You're guessing in the dark.
And here's the wrinkle: some games never show you the prompt at all. They resolve the conflict silently, automatically, using whichever heuristic the developer baked in. You find out you lost progress when your character is standing in a town you left behind weeks ago, like a ghost who doesn't know she's dead.
A Tale of Two Playthroughs
Consider two players, Priya and Dan, who bought the same open-world game on the same day and put in identical hours.
Priya plays exclusively on one machine, always online, always lets the game close naturally before shutting down. Her saves sync cleanly every time. After eighty hours, she has never seen a conflict prompt.
Dan plays on a desktop at home and a laptop when travelling. He sometimes force-quits when he's in a hurry. Once, his laptop's clock was off by forty minutes after a battery replacement. He has seen the conflict prompt four times. Twice he picked correctly. Once he didn't notice the prompt and the default resolved against him. The fourth time he lost four hours of progress before he realised what had happened.
Same game. Same service. Radically different outcomes, based entirely on usage habits and one faulty clock.
How to Actually Protect Yourself
Keep your system clocks synced to internet time. This sounds mundane. It is the single most effective thing you can do. On Windows, it's in Date and Time settings under "Sync now." On a console it's usually automatic, but worth checking after battery replacements or firmware resets.
When you finish a session, let the game close normally and give it thirty seconds before you shut the machine down. Most sync services upload in the background immediately after the game exits. Kill the machine before that upload completes and you leave the cloud stale.
If you play on multiple machines, treat them as strictly sequential. Finish on one, let it sync, confirm the sync completed (Steam shows this in the Library if you look), then start on the other. Never run the same game on two machines in the same window of time.
For games with manual backup options, use them before any major session. Some games let you maintain multiple named save slots. That feature exists for a reason, and ignoring it is a choice you will eventually regret.
Found the conflict prompt staring at you right now? Don't guess fast. Check the playtime counter if the prompt shows one. That number is harder to fake than a timestamp. The save with more logged hours is almost always the one you want.
The cloud is not a backup. It's a mirror. What that distinction costs you, you usually find out the hard way.