Game Save Management: Backups, Cloud Saves, and Transfers

Never lose a playthrough: where saves live and how to protect them.

Where Your Saves Actually Live

There is no single "saves folder" on PC — every game picks its own spot, and the usual suspects are:

• Documents\My Games\ — the most common location for AAA titles.
• %APPDATA% (Roaming or Local): type it into the Windows address bar. Many indie and older games hide saves here.
• The game's Steam folder: steamapps\common\<game> or steamapps\compatdata for Proton titles.
• Saved Games folder in your user profile — a newer Windows convention some studios use.

On consoles the saves live in system storage and are managed through the system settings, which is simpler but gives you less control. The fastest way to find any PC game's location: search "<game name> save file location" — the PCGamingWiki almost always has the exact path. Bookmark it. You will need it more than once.

The 2-Minute Backup Habit

You do not need backup software. You need a habit. Before any risky moment — installing mods, starting a New Game Plus run, updating the game, or attempting something stupid in a permadeath mode — copy the save folder to a dated backup folder. Name it clearly: skyrim-saves-2026-11-03-before-mods. Keep the last three or four backups and delete older ones; saves are small, but a year of daily backups adds up.

Where to put them? Anywhere except the same drive partition the game uses, ideally. A second drive, a USB stick, or a cloud-synced folder all work. The point is surviving the two disasters that actually happen: the game corrupting its own saves, and the drive dying. A backup on the same dying drive protects against the first, not the second.

Cloud Saves: What They Do and Do Not Promise

Steam Cloud, GOG Cloud, and Epic's cloud saves sync your saves to the platform's servers so they follow you between machines. What they do not do is version your saves — most platforms keep only the latest state. If a save corrupts and then syncs, the corruption syncs too, overwriting your good copy everywhere. Cloud sync is convenience, not backup. Keep your manual backups regardless.

When Cloud Saves Conflict

The classic conflict: you play on your desktop, then on your laptop without letting the desktop finish syncing. Next launch, the platform asks which save to keep — local or cloud. The rule is simple: pick the one with the later timestamp, and check the playtime if it is shown. If you are unsure, back up both first: copy the local save folder aside, then choose. You can always restore the loser afterward. Never mash through this dialog — it is the number one way people "lose" 40 hours.

Per-Game Cloud Quirks Worth Knowing

• Steam: cloud can be toggled per game (Properties → General). Some games sync settings but not saves — check the store page's "Steam Cloud" note.
• Not every save is synced: games with huge saves sometimes exclude them from cloud sync silently. If you switch machines and progress is missing, the save probably never left the first PC.
• Offline play: cloud sync needs a connection at exit. Quitting a game while offline, then playing elsewhere, guarantees a conflict later. Let it sync.

Moving Saves Between Machines

New PC, same 200-hour RPG? Here is the reliable method:

1. On the old machine: let cloud sync finish, then also copy the save folder manually to a USB drive or cloud storage as a fallback.
2. On the new machine: install the game, launch it once (this creates the folder structure), then close it.
3. Copy your saves into the new save folder, overwriting the fresh empty ones. Launch the game and verify your playthrough loads before deleting anything.
4. Check the version: if the new install patched to a newer game version than your save, load it and re-save immediately — most games migrate saves forward silently, but a few need that manual re-save to stabilize.

Cross-platform transfers (PC to Steam Deck, Windows to Linux) usually work for the same game build, but Proton titles store saves under compatdata with numeric IDs — find the game's app ID to locate the right folder. Console-to-PC transfers are the exception: they rarely work unless the developer explicitly supports cross-save, because the save formats differ.

Save Corruption: Recovery Playbook

Symptoms: crashes on load, "save data is corrupted" messages, or a save that loads into a void. Work through this order:

1. Load an older save. Most games keep multiple autosaves and quicksaves. Lose 20 minutes, not 20 hours — check every slot before panicking.
2. Restore your manual backup. This is the moment the 2-minute habit pays for itself.
3. Check the cloud version. If the corruption happened locally after the last successful sync, the cloud copy may predate it. Download it, then immediately back it up locally.
4. Verify game files through Steam/GOG/Epic. Corruption is sometimes in the game data, not the save.
5. Disable mods temporarily. A mod updated overnight can invalidate existing saves. Test the save on a clean, unmodded install before declaring it dead.

If nothing works, the save is gone — and this is the article that tells you how to make sure the next one is not. Set a calendar reminder for a weekly backup of your active playthroughs. Future you will not remember; the reminder will.

Multiple Playthroughs Without Chaos

Running a modded and a vanilla playthrough of the same game? Or sharing a PC? Do not rely on in-game slots alone — they share one folder and one cloud state. Instead, keep profile folders: saves-vanilla and saves-modded, and swap the active one into the game's save location before launching (a mod manager's profile feature does this automatically for supported games). For New Game Plus runs specifically, archive a copy of the completed save before starting NG+ — some games overwrite or convert the original, and "I wanted to go back" is a common regret.