Steam Cloud Save Conflict? Which Option to Pick

You launch a game and Steam throws up a dialog instead of the title screen. Your local save and your cloud save don’t match, and it wants you to pick one. Click the wrong button and you can wipe out hours of progress in a single confirmation.

A Steam cloud save conflict just means your local save file and your cloud save file have diverged. Usually that’s because you played on two different devices without fully closing the game in between. It isn’t dangerous by itself. Steam is simply refusing to guess which version you want, since merging two divergent saves would corrupt both. The dialog is annoying, but picking correctly is straightforward once you know what each option actually does.

What the Dialog Options Actually Mean

Steam’s cloud conflict prompt typically shows two choices, though the exact wording shifts slightly game to game. It might say “Download the Cloud Files” versus “Upload Local Files.” Some titles instead show “Download to this machine” versus “Upload to the STEAM Cloud.” Whatever the labels, one option keeps whatever’s saved on Steam’s servers. The other keeps whatever’s saved on the device in front of you right now.

Neither option is inherently the “safe” one. A Steam cloud save conflict is really just Steam asking a simple question: where did you actually play most recently? Whichever save reflects your most recent session is almost always the one to keep.

How to pick correctly:

1. Think back to where you last actually played this game — this device, or a different one
2. If unsure, check the save file’s last-modified date on your local machine before confirming anything
3. Choose the cloud version if you played more recently somewhere else; choose the local version if this device has your latest progress
4. When genuinely unsure, back up your local save file to another folder first. That way you have a fallback no matter which option you pick

Why This Happens: Two Devices, One Save That Never Actually Closed

The most common trigger for a Steam cloud save conflict isn’t switching computers. It’s leaving a game running or asleep on one device while playing it on another. Steam only uploads a save to the cloud when a game closes properly. If a session never actually ends, the cloud copy stalls out of date.

This is especially common on Steam Deck. Community reports describe exactly this pattern: a game left running or the Deck merely put to sleep, then the same title opened and played on a PC. When the Deck wakes back up, its now-stale local files get treated as current. They overwrite the newer cloud progress instead of the other way around. The fix here isn’t a settings toggle. It’s a habit change: fully quit the game before switching devices, rather than relying on sleep mode to pause it cleanly, since save syncing on sleep isn’t yet handled consistently across every title.

Fix 1: Fully Quit Before Switching Devices

Since the conflict almost always traces back to a session that didn’t properly close, the most reliable fix is prevention rather than cleanup after the fact.

How to fix:

1. Before switching to another PC, laptop, or your Steam Deck, exit the game completely rather than just closing the window or putting the device to sleep
2. Wait for Steam’s cloud icon (visible in your Library under the game, or in Big Picture Mode) to show the upload has finished before shutting down
3. Only then launch the same game on the other device

Fix 2: Check Timestamps Before Confirming the Dialog

If a Steam cloud save conflict has already appeared, don’t click through it without checking which version is actually newer.

How to fix:

1. Note which device you’re on and when you last played this specific game on it
2. If you have file-manager access to the save folder, sort by “date modified” to confirm your local file’s actual last-played time
3. Pick the version — cloud or local — that matches your true most recent session. Don’t just pick whichever option is listed first

Fix 3: Back Up Your Local Save Before Choosing Either Option

When you genuinely can’t tell which save is newer, protect yourself before making an irreversible choice.

How to fix:

1. Locate your local save folder (varies by game; check the game’s Steam Community hub if you’re not sure of the path)
2. Copy the entire save folder to a separate backup location on your desktop
3. Confirm the conflict dialog with your best guess
4. If it turns out wrong, you can manually restore from your backup copy rather than losing the progress entirely

Frequently Asked Questions

Will picking the wrong option in a Steam cloud save conflict delete my save permanently? Not if you backed it up first. Steam overwrites whichever version you didn’t choose, so without a manual backup, that progress is gone. With one, you can restore it yourself.

Does a Steam cloud save conflict mean something is broken? No. It’s a normal safeguard, not an error. An official developer response on Elden Ring’s Steam forum, addressing this exact prompt, described it as Steam correctly detecting that save data wasn’t uploaded under certain conditions — not a bug, but the system working as intended.

Why does this happen more often on Steam Deck? Because sleep mode on Steam Deck doesn’t reliably trigger a cloud upload the way fully quitting a game does. Playing the same title on a second device while the Deck session is only asleep, rather than closed, is the most common Steam Deck-specific cause.

Can I turn off Steam Cloud entirely to avoid this? Yes, per-game, under that game’s Properties menu in your Steam Library. Doing so stops conflict prompts, but it also means no cross-device backup of your progress at all, so most players are better off just quitting games fully instead.

The Bottom Line

A Steam cloud save conflict is Steam refusing to guess between two saves that no longer match, not a sign anything is broken. Pick whichever version reflects your most recent actual play session. Check file timestamps when unsure, and back up your local save first if you can’t tell. The real fix is prevention: fully quit a game before switching devices instead of relying on sleep. That habit causes most of these conflicts on Steam Deck in the first place. If Steam itself won’t open, or your connection drops mid-sync, it’s worth a home Wi-Fi troubleshooting pass too. Cloud saves can’t upload at all without a stable connection. That’s often the real reason a conflict showed up to begin with. </content> </invoke>