Steam Cloud Save Conflicts: Pick the Right Copy Without Losing Progress

The dialog appears the moment you launch a game you have not touched in a while: "Your local files and the Steam Cloud files appear to be out of sync. Do you want to upload your local files to the Steam Cloud, or download the Steam Cloud files?" Pick wrong and a 60-hour save can be replaced by one from two weeks ago. The conflict is not a bug — it is Steam telling you it found two different versions of your saves and cannot know which one you meant to keep. This guide shows you how to make that call safely, in a repeatable order: back up first, identify the newer copy second, resolve third.

Why the conflict happens

A save conflict needs two things: a game that uses Steam Cloud, and a copy of the save that changed in a place Steam was not watching. The common triggers:

• Offline play. You launched Steam in offline mode (or your connection dropped) and played for hours. The local save advanced; the cloud copy did not. Next online launch, Steam sees two different histories.
• Two machines. You played on a desktop, then on a laptop, before the first machine finished syncing — or the second machine was offline when it last ran the game.
• Forced shutdown. A crash or power loss mid-save can leave a half-written local file that no longer matches the cloud copy's checksum.
• Manual file fiddling. Copying saves in or out of the save folder yourself (for backups or a "100% save") almost guarantees a conflict on the next launch.

Steam compares timestamps and file checksums between the local userdata folder and the cloud copy it has stored. When they disagree, it refuses to guess and shows the conflict dialog.

Step 1: Find and back up the local save folder

Games that store saves in the Steam Cloud sync location keep them under:

C:\Program Files (x86)\Steam\userdata\<your account number>\<AppID>\remote\

The userdata folder usually contains only one subfolder if just one Steam account has logged in on this PC — that is your account number (Steam ID3). If there are several, you can confirm yours by launching any other cloud-enabled game and checking which folder's modification time just changed, or by entering your profile's ID into any Steam ID lookup page that shows the ID3 format.

The AppID is the number in the game's store page URL — for example, the store URL ending in /app/1245620/ means your saves live under userdata\<account>\1245620\remote\.

Copy the whole remote folder for that AppID to your Desktop or an external drive. That is your local copy, safe.

Note that not every game keeps its saves here. Plenty of titles store saves in Documents\My Games, %APPDATA%, or their own install folder, and only sync them to the cloud from there. You can check where a game actually syncs: in your Steam Library, right-click the game, choose Properties, open the Steam Cloud (or General) page, and click the cloud storage usage figure. Steam opens a browser view showing the exact file paths the game syncs. Back up whatever folder that page lists.

Step 2: Identify which copy is actually newer

The conflict dialog does not show you dates, so do this before choosing an option:

1. Check the local files' modification dates. In the remote folder, sort by date modified. Note the newest timestamp — that is when your local copy was last written, i.e. the last time you played while the save stayed local.
2. Check the cloud copy's timestamp. The Steam Cloud storage page (the same one from Properties) lists each synced file with its last-modified date. Compare it with your local folder.
3. Open the game's own save menu if you can. Many games show in-game timestamps or playtime per save slot, which is far more meaningful than file dates. If the local save menu shows a run from yesterday and the cloud version you remember was from last week, the local copy is the one you want.

In practice the answer is usually obvious once you look: the copy written most recently — locally or in the cloud — is the one containing your latest progress.

Step 3: Resolve the conflict

Now you can answer the dialog with confidence:

• "Upload to the Steam Cloud" (or Upload local files) keeps your local saves and overwrites the cloud copy. Choose this when you played offline or on this machine last and the local dates are newer.
• "Download from the Steam Cloud" keeps the cloud copy and overwrites your local saves. Choose this when you know the other machine has your latest progress and this machine's local files are stale.

Either way, after the game launches, verify from inside the game: open the save/continue menu and confirm the expected run is there, with the right playtime. Only after that check should you consider the matter closed.

If the dialog never appeared but saves still look wrong

Some games default to loading the newest file automatically and only show a conflict dialog when both copies changed. If your progress rolled back without any dialog:

• Check that cloud sync for the game is actually on: Properties → Steam Cloud shows a toggle plus a storage figure like 12.4 MB used of the game's allowance. If it says nothing is synced, the rollback happened locally and the cloud copy may be your only good one — download it.
• Look in the game's own backup slots. Many single-player games keep rotating backups (for example, three rolling copies of each slot). Restoring one from inside the game often recovers more than anything Steam can.
• If you restore files manually into remote, do it with the game closed and Steam fully exited, then set cloud sync off, launch once to confirm the save loads, and turn sync back on. Steam will treat the current local state as authoritative and upload it.

Preventing the next conflict

• Let Steam finish syncing before shutting down. The sync status appears in the bottom bar of the Steam client ("Synchronizing" / "Uploading"). Killing the PC mid-upload is the classic cause.
• One machine at a time for long sessions. If you split play between a desktop and a handheld or laptop, launch the game once online on the old machine before moving — that forces the upload.
• Keep your own backups anyway. Cloud saves are convenient but not a backup strategy: deleting a game can, on some titles, delete its cloud files too. A monthly copy of userdata to an external drive costs nothing. If your disk is filling up with games, the safe disk cleanup walkthrough covers what to move and what never to touch.

Save conflicts look scary because the dialog gives you a binary choice with no information. But the underlying question is always the same — "which copy did I last play?" — and two file timestamps plus two minutes of backups turn it from a gamble into a formality. Related guides: fixing stutter on Windows 11 and cutting input lag. The full list of walkthroughs is on the article index, and the site's policy pages are linked in the about section.

Menu names and dialog wording can change between Steam client updates and game versions; the userdata path structure has been stable for years but individual games vary in where they store saves.