Steam Cloud Conflict: Which Save to Choose and How to Protect Your Progress

When Steam shows a Cloud conflict, it has found two different copies of your save and cannot tell which one you want. In most cases you should keep the copy you played most recently, but do not click anything until you have checked the dates against your own memory and copied your save folder somewhere safe. Valve says Steam Support generally cannot recover lost saves, so that one-minute backup is your only real safety net.

A conflict window looks like a routine pop-up, which is exactly why it costs people progress. You are in a hurry to play, two boxes appear with two dates, and one click later a 40-hour character has quietly become a 12-hour character. The good news is that the decision is rarely hard once you know what the window is actually telling you. This guide walks through what causes a conflict, how to read the dates, what to do in the awkward situations where neither copy looks right, how to deal with the separate "unable to sync" error, and how to set things up so a bad click can never hurt you again.

Key facts

• A Steam Cloud conflict appears when a game launches and Steam detects that your local files differ from the files stored in the cloud.
• Steam cannot choose for you, because the same file was changed in two places without a sync between them.
• Valve's general advice is to pick the version modified most recently, while checking that the dates match what you actually did.
• Playing in Offline Mode stops syncing until you go back online, and Valve says this is very likely to cause a conflict.
• Steam Support states it cannot recover lost saves or help resolve cloud conflicts.
• Many games do not use Steam Cloud for save files at all, so check the store page and never assume your progress is protected.
• On Windows, cloud-enabled files are kept by default under the userdata folder inside your Steam installation.

What a Steam Cloud conflict actually means

Steam Cloud is a storage service that games can use to keep settings, saved games, stats and other user data on Valve's servers. Developers decide exactly what gets uploaded, so two games can use it in completely different ways. One might sync every save slot, while another only syncs your key bindings.

In normal use the process is invisible. Steam downloads the latest cloud files before you play and uploads anything that changed after you finish. A conflict happens when that routine breaks down. According to Valve, the window is shown at launch when the local files associated with a game differ from the versions stored in the cloud, and the mismatch may have happened on the machine in front of you or on another machine earlier.

The important part is why Steam stops and asks. If a file was only changed in one place, Steam just copies the newer version across and you never hear about it. A conflict means the file was modified in two different locations with no synchronization in between. Steam has no way of knowing which of those two timelines matters to you, so it hands the decision to you.

That also explains why simply pressing the option with the newer date is not always correct. "Newer" only tells you which file was written last. It does not tell you which file contains more progress. A game that autosaves at the main menu can produce a very recent file that holds almost nothing useful.

Common situations that cause a conflict

Most conflicts come from a short list of everyday habits. Finding your own situation in this list usually tells you straight away which copy is the good one.

You played offline. Valve specifically warns about this. Offline Mode prevents syncing until you are back online, so if you played on a laptop during a flight and then played on your desktop before the laptop reconnected, you now have two separate histories.

You played on two machines and one did not finish uploading. Shutting a PC down, closing a laptop lid or losing Wi-Fi right after quitting can interrupt the upload. The cloud keeps the old copy, your next device builds on that old copy, and the first machine still holds the unsynced progress.

The game or your PC crashed. A crash can stop the end-of-session upload from happening, and it can also leave a half-written save behind.

You reinstalled the game or Windows. A fresh install may create new default files on first launch, which then clash with the real progress in the cloud. In this case the local copy is the one to be suspicious of.

You edited or restored a save by hand. Copying in a backup, using a mod manager or running a save editor changes local files outside Steam's view, so the next launch looks like a conflict.

You share a PC with someone. Each Steam account has its own folder, but if a game stores saves in a single shared location, one person's progress can get tangled with another's.

Your clock is wrong. The dates in the window are only as trustworthy as the clocks on the machines that wrote the files. If one PC's date or time zone is off, the "newest" label can mislead you.

How to read the conflict window

The window shows you the two sets of files, usually labeled as the copy on this machine and the copy in the Steam Cloud, along with when each was changed. Before you choose, ask yourself three questions.

When did I last genuinely play, and on which device? Valve advises thinking carefully about how the dates and times correspond to your own behavior and progress in the game. If you know you played on your desktop last night and the cloud copy is dated last night, that is a strong signal. If the local copy is dated one minute ago and you have only just launched the game, be suspicious, because something other than real play may have created it.

Where did I make the most progress? If you played for five hours on a laptop and for ten minutes on a desktop, the laptop's copy is probably the one you care about, even if the desktop's copy is newer.

Does one copy look much smaller or suspiciously fresh? Where the window or the folder shows file sizes, a save that is drastically smaller than usual can be a new, nearly empty file. Size is not proof, because many games compress data, but a big difference deserves a second look.

The one-minute backup to make before choosing

This is the step that turns a scary decision into a harmless one. Once you have a copy of your files, choosing the wrong option is an annoyance rather than a disaster.

Leave the conflict window where it is and do not launch the game. Then find your save files. Valve lists these default locations for cloud files:

Inside userdata you will find one or more folders with numeric names. Each number corresponds to a Steam account that has logged in on that machine. Inside that are folders named after each game's App ID, which is the number you can see in the game's store page address. For example, Valve uses Dota 2, whose App ID is 570, as its illustration.

To make the backup:

1. Open the userdata folder and go into your account's numbered folder.
2. Find the folder that matches your game's App ID.
3. Copy the whole folder to your desktop or a USB drive, and rename it with today's date.
4. If you cannot find any meaningful files, look up your game on PCGamingWiki, a community reference that lists where each PC game keeps its saves.
5. Check the other common places, such as Documents, Documents\My Games, Saved Games, and the hidden AppData folder.

Plenty of games keep their real saves outside userdata, even when they use Steam Cloud. This is why looking up the specific game is worth the extra moment. When you copy files, copy rather than move them, because moving them changes the very thing Steam is comparing.

If you are on a second machine, repeat the backup there too. A conflict usually involves two devices, and the copy you might want to rescue could be sitting on the one you are not using.

Making the choice and checking it worked

With the backup done, go back to the window and choose. Pick the copy you decided on, let the game load, and go straight to your save list before doing anything else. Check the character level, the playtime, the last location and the date on your newest save slot.

If everything looks right, play normally and quit from the game's own menu. Give Steam a moment to finish its upload before you shut down. You can watch the status in your library, where the game page shows whether the cloud is up to date.

If it looks wrong, quit without saving anything new. Your next move is to put the correct files back:

1. Close the game and fully exit Steam so nothing is writing to the folder.
2. Copy your backed-up files over the current ones in the same location.
3. Open Steam and launch the game. You will probably see another conflict, which is now expected.
4. Choose the local copy, because the local copy is now your restored good version.

That sequence is the reason the backup matters. Without it, the overwritten copy is simply gone.

What to do when neither copy looks right

Sometimes both options are unappealing: one is old, and the other seems empty or corrupted. Do not panic-click, and try these in order.

Check your other device. Valve points out that if a machine failed to sync, the original progress may still be sitting on it. If you still have access, start Steam on that older machine and see whether it will sync the game. If it does, the progress should appear on your newer machine the next time you launch.

Look for the game's own backup files. Many games keep rolling autosaves or backup slots. Files ending in .bak, or folders named backup, are worth checking. The in-game load screen often lists older autosaves too.

Search the game's Steam community hub. A hub search for the words "save" and "lost" often turns up instructions specific to that game, including its backup file naming. Be careful with any post that asks you to download a tool or a file from an unknown site.

Contact the developer. Valve says developers are the right people for questions about how a particular game stores and transfers its saves.

Accept the limits of Steam Support. Valve is plain about this: because cloud sync is automated, Steam Support has limited ability to address issues, and lost data is not likely to be recoverable. Tickets can explain how the system works, but they will not bring a file back.

"Steam was unable to sync your files": a different problem

This message looks similar, but it means something else. A conflict means Steam successfully compared two files and found they differ. "Unable to sync" means Steam could not complete the sync at all. It might be a brief hiccup, or something might be wrong with your network.

Valve encourages you to fix the underlying cause before launching the game. If you ignore the warning and choose to play anyway, you can create a real conflict between cloud and local files and lose data. So if the game is not urgent, spend a few minutes on the checks below first.

Valve's own troubleshooting list covers these areas:

Refresh your network hardware. Restart your modem and router. Valve notes that network equipment can drift into a slow or broken state after running for a long time, which can make cloud sync crawl or fail. If you are on Wi-Fi, test with an Ethernet cable.

Test a different connection. Some internet providers, especially cellular networks, cache or compress data to save bandwidth, and that can interfere with Steam. Trying another network, ideally from a different provider, is a quick way to find out whether your connection is the cause. A phone hotspot works for a small save upload, as long as you keep an eye on your data allowance.

Check your firewall. Certain firewalls can stop Steam from reaching its servers. You may need to add Steam as an exception. If you temporarily disable a firewall to test, turn it back on straight away.

Check your antivirus. Valve explains that antivirus software hooks deep into a system and can affect disk and network operations. It suggests that adding exclusions may be necessary, such as excluding the userdata folder and your game installation folders from live monitoring.

Read the log if you are curious. Steam keeps a record of cloud activity in logs\cloud_log.txt inside the Steam folder on Windows. You do not need to understand all of it, but it can show repeated failures, and it is useful to attach if you ask for help in a community forum.

How to tell whether your game even uses Steam Cloud

This surprises a lot of people, and it causes more lost progress than conflicts do. Steam Cloud is optional for developers, and even games that support it might not sync your actual save files.

To check, open the game's store page and look for the Steam Cloud feature listed among the details. Then remember Valve's caveat: the label only tells you the game uses the service in some way. Determining exactly which files are covered may require asking the developer or the community.

The most reliable test is a simple real-world one. Play for a few minutes on one device, quit, wait for the sync, and start the game on a second device. If your progress shows up, your saves are covered. It is far better to find out now than on the day your hard drive fails.

Cross-platform sync adds another layer. Steam supports sharing cloud data between Windows, macOS and Linux, but not every game uses that feature. If you move between a Windows PC and a Steam Deck, confirm that your particular game handles it properly before relying on it.

Should you turn Steam Cloud off?

Usually not, but there are specific moments when turning it off helps.

You can toggle it in two places. For one game, right-click it in your library, choose Properties, and change the Cloud Synchronization setting on the General tab. For everything, open Steam's Settings, go to the Cloud tab and use the toggle for enabling cloud sync for applications that support it.

Keep in mind what happens when you do. Valve explains that with cloud disabled for a game, progress that would normally go to the cloud is only saved locally on the machine where you made it. So you lose your off-site safety copy, and your other devices will not receive your progress.

If you do switch it off temporarily, make a note to switch it back on. A cloud setting you forgot about is how people discover, months later, that nothing has been backed up since spring.

How to stop conflicts from happening again

A few small habits eliminate most conflicts.

Go online before and after every offline session. If you travel with a laptop or a Steam Deck, connect to the internet and let your game sync before you leave. When you get home, connect that device first and let it upload before you start the game anywhere else.

Quit properly. Exit through the game's menu and give Steam a little time. Do not shut down the moment the game window disappears. Laptop users should be particularly careful about closing the lid immediately.

Use one device at a time. Do not leave a game running or suspended on one device while you start it on another. Suspended sessions on handheld devices are a classic source of two competing histories.

Keep your clock accurate. Let your operating system set the date and time automatically on every device you play on. Accurate timestamps make every future decision easier.

Make periodic manual backups of games you care about. Once a month, copy the save folders for your long-running games to an external drive or a separate cloud folder. Cloud sync is not a true backup, because a bad file can sync as faithfully as a good one.

Back up before major changes. Before reinstalling Windows, moving to a new PC, installing a big mod or changing a game's beta branch, take a fresh copy of your saves.

If you are also moving your games to a new drive, read our guide on moving Steam games to another drive before you start, so your files and your saves stay matched up.

Moving to a new PC without losing saves

A new computer is the moment a lot of conflict stories begin. Here is the order that keeps things simple.

1. On the old PC, launch and quit each important game once while online, so the latest progress is uploaded.
2. Copy your save folders to external storage as insurance, including any in Documents or AppData.
3. On the new PC, install Steam and your games, but do not create new saves first.
4. Launch each game. It should download your cloud files. If a conflict appears on the first launch, the cloud copy is almost always the correct one, because the local files have just been created.
5. For games without cloud support, copy your saved files into the same location on the new machine.

Valve warns that if a game does not use the cloud and you no longer have access to the old machine, those saves cannot be recovered. So do not wipe or sell the old PC until you have launched every game you care about on the new one and confirmed your progress.

Protecting the account behind your saves

Your cloud saves are only as safe as the Steam account they belong to. Secure the account with Steam Guard and keep your recovery details current, because someone who gets into your account can change more than your games. If you ever get locked out, our Steam account recovery guide lists the proof of ownership Valve asks for.

It is also worth knowing that adding money to your Steam Wallet is a good way to keep your card details off a shared family PC. If you would rather not pay at all, you can earn points on XPReward by completing offers and work toward a Steam gift card in the Reward Store. It takes real time, and the first $25 card costs 3,600 points, so treat it as a slow way to fund your next game rather than a quick one.

Frequently asked questions

Which one should I choose on a Steam Cloud conflict?

Usually the version modified most recently, because it should hold your latest session. Check that the date matches when you actually played, though. A very recent local file on a fresh install may be an empty default rather than real progress.

Can Steam Support recover a save I overwrote?

Valve says this is unlikely. Cloud sync is automated, so Steam Support has limited ability to help, and it states that it cannot recover lost saves or resolve cloud conflicts for you. A copy on another device or your own backup is your best hope.

Why do I keep getting a Steam Cloud conflict?

Repeated conflicts usually mean a session is not uploading before you switch devices. Common causes are playing in Offline Mode, shutting down straight after quitting, leaving a game suspended on a handheld, or a network, firewall or antivirus problem blocking the sync.

What does "Steam was unable to sync your files" mean?

It means Steam could not finish talking to the cloud, which is different from a conflict. Try restarting your router, using a wired connection or another network, and checking your firewall and antivirus. Valve warns that playing anyway can create a conflict and lose data.

Does turning off Steam Cloud delete my cloud saves?

Valve's documentation describes that when cloud is turned off, new progress only stays on the machine where you made it. It does not describe the toggle as a way to delete anything. Treat it as stopping new syncs, and keep your own copy of important saves regardless.

Where are Steam Cloud saves stored on my PC?

By default on Windows they are in C:\Program Files (x86)\Steam\userdata, then your account number, then the game's App ID. Many games keep saves elsewhere as well, such as Documents or AppData, so look up your specific game.

Does every Steam game use Steam Cloud?

No. It is optional for developers, and many games do not use it for saves. Look for Steam Cloud on the store page, then test it by continuing a save on a second device, since the label alone does not confirm what is covered.

Is it safe to delete files in the userdata folder?

Avoid deleting anything there unless a guide for your specific game tells you to, and always copy the folder first. It also holds settings for each account, and deleting the wrong folder can remove local data you still need.

Sources

• Steam Support: Steam Cloud, for conflict behavior, sync errors, file locations and troubleshooting.
• Steamworks Documentation: Steam Cloud, for how games sync files around each session.
• PCGamingWiki, a community reference for per-game save locations.

Steam Cloud facts checked on 8 November 2026.