Backing up a game save is simple only when you know where the data lives, which account owns it, and what a launcher or console will do when two versions conflict. This guide gives you a reusable checklist for protecting saves, transferring progress between devices, and recovering carefully without overwriting newer work.
Overview
A cloud save is convenient, but it is not the same as a complete backup. Cloud synchronization may depend on the game, launcher, account, subscription, device connection, and the most recent successful upload. Some games store progress locally, while others keep important data on a server and provide little or no manual transfer option. Modded games may also use extra profiles, configuration files, or separate save locations.
Before moving or restoring a save, identify three things: the source device, the destination device, and the authoritative copy you want to preserve. Do not begin by launching the game repeatedly on both devices. A new session can create or sync an empty, outdated, or incompatible file.
The safest general process is:
- Stop playing and close the game completely.
- Record the game edition, platform, launcher, account, and approximate time of the newest progress.
- Locate the local save data if the game uses it.
- Copy the original files to a separate backup location without moving or renaming them yet.
- Check cloud-sync status and pause synchronization if you need to compare versions.
- Transfer or restore only after confirming which copy is newer and compatible.
- Launch the game, verify several saves or progression markers, and create a fresh backup.
For branching or choice-heavy games, preserve the entire save folder rather than a single file. A useful route history can be lost if you restore only the most recent slot. Players who track multiple endings may also want to keep a simple text note with the date, platform, character or route, and save-slot purpose. For related progress-planning advice, see our checklist for tracking choices in branching games.
Platform comparison
| Platform or setup | Cloud-save behavior | Local data and backup approach | Account requirement | Conflict and transfer limits |
|---|---|---|---|---|
| PC launcher | Usually controlled by the launcher and the individual game's support for synchronization. | Often stored in a game folder, user profile, Documents, Saved Games, AppData, or a launcher-specific directory. Copy the complete relevant folder. | Typically the same launcher account and, for some games, an additional publisher account. | Conflicts may offer upload, download, or newer-file choices. Some games do not support cross-launcher transfers. |
| Windows game installed through a store app | May use platform-managed synchronization, game-managed data, or both. | Files can be protected or stored in less obvious user-data locations. Prefer the game's documented export or backup option when available. | The store account and the game's linked account may both matter. | Permissions, edition differences, and protected folders can limit manual copying. |
| PlayStation or Xbox console | Cloud behavior is tied to the console account, game support, and the platform's synchronization process. | Manual access to individual save files is limited compared with a PC. Use the platform's supported backup, transfer, or console-to-console migration features. | The same console account is generally needed to access its saved data. | Region, edition, account, and game-version differences can prevent a save from loading. Do not assume a disc, digital, or remastered edition shares progress. |
| Nintendo console | Cloud availability and transfer behavior vary by game and platform feature. | Use the console's supported save-data transfer or backup process where available; manual file access is generally restricted. | The same Nintendo account or console profile may be required. | Some titles or modes can have special transfer restrictions. Check the game's own transfer instructions before deleting local data. |
| Modded PC installation | Cloud synchronization may include saves but not the mods, load order, profiles, or external tools required to open them. | Back up saves, mod lists, profiles, configuration files, and the game's version information separately. | Use the same game and launcher account where required. | A save may fail or behave differently if required mods are missing, reordered, or changed. |
These are working categories, not guarantees for every title. The game's own support page and launcher settings take priority, especially after a major update or edition change.
Checklist by scenario
Before reinstalling Windows or replacing a drive
- Open the game once and note the newest confirmed save slot or character.
- Close the game and launcher completely, including background processes where applicable.
- Search common locations such as Documents, Saved Games, AppData, the game's installation folder, and the launcher user-data directory. Search by the game's title, developer name, or known save-file extension.
- Copy the complete save folder to an external drive or a separate cloud-storage folder.
- Keep at least one untouched copy that will not be affected by automatic synchronization.
- Record the launcher, game edition, mods, and any unusual launch options.
When transferring to another PC
- Install the same game edition and, for a modded playthrough, the same required mod versions where practical.
- Sign in to the correct launcher and linked publisher account.
- Launch the game once, then exit it. This can create the destination folder, but do not allow an empty save to replace your backup.
- Temporarily disable or pause cloud synchronization if the launcher provides that option.
- Copy the backed-up save folder into the destination location, preserving the original folder structure.
- Start the game and verify progression before re-enabling synchronization.
- If asked to choose between local and cloud data, select only after comparing timestamps and save-slot details.
After a corrupted or conflicting save
- Do not keep launching and saving over the affected profile.
- Copy the current folder as-is so you retain evidence of what failed.
- Look for older rotating backups, automatic backup files, alternate slots, or an in-game recovery option.
- Restore one known-good copy to a separate test location when possible.
- Check whether the failure began after a game update, mod change, crash, or device shutdown.
- Once a working save loads, make a new backup before continuing.
If the progress is server-side, a local file restore may not help. In that case, use the game's account-recovery or support process and avoid third-party tools that request account credentials.
What to double-check
File location: There is no universal save path. A game may use more than one folder, and a visible configuration folder may not contain progression. Search the game's support documentation and inspect modified dates rather than guessing from folder names.
File format: Preserve the original folder structure and file extensions. Compressing a folder into ZIP format is useful for storage, but extract it before use unless the game explicitly supports an archive.
Account and edition: A save can be tied to a profile, launcher account, region, platform, or edition. Cross-platform multiplayer does not automatically mean cross-progression; our cross-platform guide explains why those features should be checked separately.
Cloud direction: Cloud sync can upload an empty or old destination save. If a conflict prompt appears, stop and compare timestamps, file sizes, slot names, and in-game progress. Do not choose an option simply because it says “cloud” or “local.”
Mod dependencies: Back up the save and the environment that created it. Keep a mod list, load order, game build, and profile export when the mod manager supports one. A save that depends on removed content may load with missing items or become unstable.
Privacy and security: Save folders can include profile identifiers, screenshots, logs, or custom content. Store backups in a trusted location, use account protection such as two-factor authentication where available, and never share credentials to obtain a save file. See our gaming account security checklist before moving account-linked data.
Common mistakes
- Relying only on cloud saves: A sync service can fail, retain the wrong version, or exclude a game's local configuration. Keep an independent copy.
- Copying while the game is open: Files may be incomplete or locked. Exit the game first.
- Testing the destination before backing up: An automatic empty save can overwrite a good cloud copy. Secure the source before launching.
- Restoring only one file: Companion files, profiles, thumbnails, or metadata may be needed. Copy the whole save directory unless official instructions say otherwise.
- Mixing game editions: Standard, remastered, regional, and subscription versions may use different data structures.
- Ignoring mods after a transfer: Match the mod environment before judging whether a save is damaged.
- Deleting the source too soon: Keep the original until the destination has loaded, played, saved, and been checked across more than one slot.
When to revisit
Return to this checklist before changing hardware, reinstalling an operating system, moving between launchers, enabling a new cloud service, starting a heavily modded playthrough, or handing a device to another household member. Revisit it after a major game update, a launcher redesign, a console migration, or a change in account linking. These events can alter save paths, synchronization rules, supported editions, or transfer limits.
Make the process routine by scheduling a manual backup at sensible milestones: before a major quest decision, after completing a long session, before installing or removing mods, and before joining a limited-time event. For event-related preparation, use the game event checklist alongside this backup process.
Before your next transfer, print or save this short action list:
- Confirm the newest in-game progress.
- Close the game and pause sync if comparison is needed.
- Copy the full save folder or use the platform's supported export tool.
- Keep an untouched backup in a separate location.
- Match account, edition, game version, and mod requirements.
- Compare local and cloud copies before choosing a conflict option.
- Load, verify, save, and back up again on the destination device.
That sequence takes less time than rebuilding lost progress and gives you a repeatable way to protect saves as games, devices, and workflows change.