A Steam Cloud conflict presents a choice before you can get back to playing. The tempting response is to select whichever copy has the latest timestamp. That may be the right choice—but a timestamp alone does not establish which save contains the progress you want.
Start by preserving what you can, not by trying to make the warning disappear. This guide provides a cautious workflow for identifying the files, comparing your play history and checking the result on one device before using another.
Evidence boundary: CoreSecTech checked the official documentation linked below on October 7, 2026. We did not reproduce a Steam Cloud conflict, test a save restoration or measure recovery success. The decision checklist is CoreSecTech’s analysis; game-specific restoration requires the developer’s instructions.
1. Separate a conflict from an “unable to sync” warning
Valve’s Steam Cloud FAQ distinguishes different situations. A conflict means local and cloud files disagree and Steam needs a choice. An unable-to-sync warning means synchronization has not completed; proceeding can put progress at risk.
Record the exact wording and displayed file dates before dismissing a prompt. Do not choose a version merely to see what happens. Avoid starting a new session on another device while you investigate.
| Observation | What to establish | Safest next step |
|---|---|---|
| Steam asks you to choose between versions | Which copy matches your intended progress? | Preserve accessible local saves before choosing. |
| Steam cannot synchronize | Did the previous session finish syncing? | Address the sync failure before playing further. |
| The game loads an unexpected checkpoint | Is the correct account, character or slot selected? | Stop advancing the save; inventory available copies. |
| You cannot identify either version | What evidence is missing? | Hold the decision and seek game-specific help. |
2. Identify the game, account and save location
Write down the game, device, operating system, Steam account and any separate in-game account. Record whether you recently switched machines, played offline, changed a character slot or installed a different game build. These are investigation questions, not proof of a particular cause.
Do not assume that copying Steam’s installation folder captures every save. The Steamworks Cloud documentation explains that developers select the files or use a storage API. Save locations and cross-platform arrangements depend on the game’s implementation.
Find the developer’s support page for your exact game and platform. If the location is unclear, stop before deleting, renaming or replacing files. A forum path for another operating system or another edition is not a verified backup plan.
A documented example: Stardew Valley on Windows
Stardew Valley’s official save troubleshooting guide identifies this Windows location:
%appdata%\StardewValley\SavesUse Windows + R, enter that path and open the folder. This is an example for that game—not a universal Steam path. Its developer also explains that a character save uses multiple related files and recommends a backup before editing them. For preservation, copy the complete relevant folder rather than extracting one file and guessing what else is required.
This guide does not ask you to perform the developer page’s advanced file-editing procedures. Locating and copying files is different from proving that a save is intact or successfully restoring it.
3. Preserve local copies before changing sync behavior
For an unresolved conflict, leave the version choice pending or cancel without selecting a replacement. Work with the game closed. If a session is currently running, use its normal save-and-exit process rather than force-killing it; understand that exiting can trigger synchronization.
On an older device that may hold valuable unsynced progress, do not launch Steam or the game simply to “check the cloud.” First preserve the developer-identified local files while the game and Steam are closed. Steamworks documents uploads after a game exits and downloads before it starts; opening a session is not a neutral inspection step.
- Locate the save folder using the developer’s instructions.
- Copy, do not move, the relevant folder to a separate backup location outside the game’s active save directory and outside folders participating in synchronization.
- Name the copy with the device and date so different devices’ files stay separate.
- Check that the copied folder contains the expected files. Keep the original files untouched.
- Where practical, keep another copy on a separate storage device before attempting restoration.
A completed copy is not a validated recovery. It may contain an older or damaged save. Its purpose is to retain options and avoid destroying the only available local version during diagnosis.
4. Compare progress, not just timestamps
Build a small evidence record before making the choice. Use actual observations; leave unknown entries marked unknown.
| Record for each device | Why it helps |
|---|---|
| Last session you remember playing | Establishes where the desired progress was created. |
| Character, slot and recognizable checkpoint | Distinguishes the intended save from another profile. |
| Offline or online during that session | Identifies a reason to investigate synchronization history. |
| Displayed file dates and time zone | Provides supporting chronology, not proof of progress. |
| Sync result you actually observed | Separates confirmed completion from an assumption. |
| Location of the preserved copy | Confirms that the investigation has not relied on an unmade backup. |
A later modification time tells you that a file was written later. It does not tell you that it contains the character, checkpoint or progress you intended to keep. Equally, your recollection of a session is useful context, not file-level verification.
If the evidence disagrees, do not break the tie by guessing. Preserve both devices’ accessible files and ask the developer how to identify the relevant save. Do not invent a universal rule such as “always choose local” or “always choose cloud.”
5. Choose only when you understand the replacement
| Your evidence | Decision boundary |
|---|---|
| You can identify the desired local progress and have preserved it | Read the prompt’s upload/replacement direction carefully before selecting it. |
| You recognize the cloud version as the intended progress and have preserved the current local files | Confirm which local files the download will replace. |
| Dates disagree with known play history, or the desired progress is unverified | Do not select a replacement yet. |
| No accessible copy contains the expected progress | Treat recovery as unresolved; investigate developer-supported backups. |
Read the actual labels on your prompt rather than following a remembered button position. Selecting a version is a replacement decision, not an automatic merge of two play histories.
After resolving the choice, inspect the save on one device first. Confirm the account, slot and recognizable checkpoint before continuing play. If the result is wrong, stop. Use an exit-without-saving option only if the game offers one; autosaving may already have changed the working copy. Keep the preserved folders unchanged.
Do not paste a backup over active files while the game is running. Restoration can involve several linked files and synchronization choices. Follow the game developer’s recovery procedure, or ask support if the instructions do not address your platform and situation.
6. Verify synchronization before switching devices
Once the intended progress is confirmed, finish the session normally and check synchronization before opening the game elsewhere. Steamworks describes session-boundary syncing and notes that transfers can take longer for larger or more numerous files. Do not substitute an arbitrary five-second wait for observing completion.
Keep these checks separate: the game exited, Steam completed syncing, and the next device loaded the expected progress. One does not establish all three. Avoid alternating between devices while a warning remains unresolved.
You can inspect the game’s cloud setting in its Steam Library properties, under General, and the global setting under Steam Settings → Cloud. Valve documents both controls. Toggling them is not a diagnostic shortcut: disabling synchronization does not create a recovery copy.
7. Escalate with useful evidence—not destructive experiments
If the problem persists, provide support with the game and platform, exact warning, session chronology and steps already taken. Valve identifies cloud_log.txt in Steam’s logs folder as a synchronization log. Read or preserve it; do not delete it as a proposed fix. Redact account identifiers, usernames and personal paths before sharing publicly.
- Do not delete saves, cloud metadata or whole Steam folders to clear a warning.
- Do not disable antivirus or firewall protection broadly for this workflow.
- Do not treat reinstalling the game or verifying installation files as proof that your progress is recoverable.
- Do not overwrite an intact backup during repeated attempts.
Valve explicitly says Steam Support cannot recover lost saves. A cloud-enabled game therefore should not be treated as a guaranteed historical recovery service. Look for the developer’s documented backup mechanism and keep separate copies of important progress.
FAQ
Should I always choose the newer Steam Cloud save?
No. Compare the date with your actual play history and intended checkpoint. If you cannot identify the desired progress, preserve accessible copies and pause the choice.
Is a local backup enough to guarantee recovery?
No. A copied folder may be incomplete, outdated or damaged. Keep it intact, then use the developer’s instructions to determine whether it can be restored.
Should I play on both devices to test which save is correct?
Not as a first test. Further sessions introduce additional writes and complicate the comparison. Establish the intended version on one device before resuming a normal device-switching routine.
Before you resume playing
- The exact warning and affected game are recorded.
- The developer’s save location is identified.
- Accessible local versions are copied to separate, clearly named folders.
- The replacement direction and intended progress are understood.
- One device loads the expected account, slot and checkpoint.
- Synchronization completes before you switch devices.
If you cannot complete the evidence checks, stopping is a valid result. Clearing the prompt matters less than preserving the progress you are trying to protect.