Resolve a Steam Cloud save conflict without choosing blindly

In brief

A Steam Cloud conflict means the available save sets disagree. Steam cannot know which progress you value. Stop before selecting a copy and identify the session that contains your intended save.

Preserving local files first gives you a route back if a timestamp or device label is misleading.

Identify the last good session

Write down the device used, approximate time and progress reached. Compare that with the conflict dialog’s information. If you played offline on a second machine, its local save may be the one you want. If the game has a separate publisher cloud, identify that prompt rather than applying Steam instructions to a different service.

Protect both sides where possible

Use the developer’s actual local save path and copy the files outside the active folder. Keep each device’s set separate. Inspect the account’s available Steam remote-storage downloads if you need a copy of accessible cloud files; availability does not guarantee a historical version. Do not rename files within the live save set to experiment.

Choose once and check the result

After selecting the intended set, open the game and check the expected slot and progress before continuing. Quit normally and allow sync to complete. If the result is wrong, avoid further saves and follow the game’s restore procedure using your protected copy rather than generating more conflicting sessions.

What to do next

1. Cancel or pause the launch and do not start the game on another device.
2. Copy the local save folder from each accessible device, with device names and dates.
3. Compare the last successful session and available save details, then select the intended copy and verify in-game progress.