When a cloud save conflict appears, stop and preserve the available copies before choosing one. Do not repeatedly launch the game, play offline, or force another upload while the local and cloud versions disagree. Record the account, device, game, modification times, and recent progress, then follow the platform's supported conflict or upload and download controls.
Freeze the situation
Take a screenshot of the warning and note the current device, account, time zone, game version, and whether the last session was online or offline. Do not select a version simply because one label says cloud. The correct copy is the one that matches your actual progress, and modification times can be misleading after clock changes, restores, or a session that failed to close normally.
Close the game without creating a new save if the platform allows it. Avoid opening the title on another device because that device may sync another copy. If the platform is reporting a network or sync error, resolve the connection problem before continuing.
Steam's Cloud support guide explains that its conflict window appears when local and cloud files differ and Steam cannot automatically select a version. It recommends comparing dates and times with the player's known behavior and progress. The guide also warns that ignoring a sync error and launching can create a conflict and possible loss of progress.
Identify every candidate copy
List the local save, cloud save, any console copy, and any manual backup. For each, record the displayed time, device, approximate progress, character or slot, and file size when available. Check whether the game supports cloud saves at all and which files the developer includes. Some services sync settings or profiles as well as progress, while individual games can control their own save format.
Look for a supported sync-status screen before touching files. PlayStation's PS5 cloud storage guide provides controls to check sync status and to upload or download saved data. It also distinguishes PS5 automatic synchronization from some PS4 workflows that require a manual download. Platform, subscription, game, and generation can therefore change the correct procedure.
If the older device that contains the expected progress is still available, keep it offline while you make a separate backup using a documented method. Do not modify hidden game files unless the game's developer or platform instructions identify them and you understand the risk. A copied folder that the game cannot restore is not yet a verified backup.
Preserve before selecting
Use an official local export, console copy, or documented file copy when available. Label it with the game, account, device, time, and whether it is believed to be local or cloud-derived. Store it outside the active sync folder so the client cannot overwrite it. If saves are encrypted, account-bound, or server-side, do not assume a normal file copy will be portable.
Steam documents default local cloud-data locations and a cloud activity log, but also notes that developers customize what is stored. Use that information for diagnosis, not as permission to replace active files blindly. If the game provides its own account sync, cross-save, or server profile, consult that developer's support material as well.
Choose using progress evidence
Compare the conflict details with the last known session. Ask which device was used, when the game was closed, whether offline mode was active, what level or checkpoint was reached, and whether the title showed a successful sync afterward. A newer timestamp is a clue, not proof.
Select a copy only after the evidence points to it and the other candidate has been preserved when possible. Use the platform's supported selection, upload, or download interface. Never delete the cloud or console copy as the first troubleshooting step. If the choice is unclear and the progress is valuable, stop and contact the game developer or platform support with the screenshot and timeline.
Verify before normal play
Launch the game on one device and inspect the save slots without immediately overwriting them. Check recent progress, inventory, achievements or milestones, settings, and play time. Exit normally and wait for the service to report a successful sync. Recheck sync status before launching on a second device.
Keep the preserved copy until several normal sessions have synchronized. Document the cause if known, such as offline play, a network interruption, simultaneous play on two devices, an incorrect account, or a device clock problem. Then prevent a repeat by closing games cleanly, letting sync finish, keeping device clocks automatic, and avoiding concurrent sessions.
A resolved conflict has three pieces of evidence: the expected progress opens, the platform reports a successful sync, and a separate recovery copy remains available long enough to confirm stability. Anything less is a reason to pause before more play changes the remaining evidence.
Sources
- Steam Cloud — Valve
- PlayStation Plus cloud storage for PS5 consoles — PlayStation Support
- How to Manage PS5 Console Storage Space — PlayStation Support