iTechGuides is reader-supported. When you buy through links on our site, we may earn an affiliate commission. As an Amazon Associate I earn from qualifying purchases. Learn more
Use local manual saves as permanent checkpoints and alternate branches, and use Cross Progression only to continue your latest save types on another platform. Before changing devices, update the game, confirm the edition, connect the same CD PROJEKT RED account on both platforms, and verify the cloud icon beside a newly created save. Never delete older saves because you assume every platform has the same slot limit or retention rules.
The two-save strategy that prevents most losses
The Witcher 3 has two different ways to keep progress, and they solve different problems:
| # | Preview | Product | Price | |
|---|---|---|---|---|
| 1 |
![NAMCO - CD Projekt Red - The Witcher 3 Wild Hunt - Complete Edition, Playstation 5 [English Edition]](https://m.media-amazon.com/images/I/51dWUfwFl5L._SL160_.jpg)
|
NAMCO - CD Projekt Red - The Witcher 3 Wild Hunt - Complete Edition, Playstation 5 [English Edition] | $36.93 | Buy on Amazon |
| 2 |
|
Witcher 3: Wild Hunt Complete Edition - Xbox One | $27.99 | Buy on Amazon |
- Local saves: manual saves, autosaves and checkpoints stored by the game on your current platform. These are the right tools for preserving a quest decision, difficult fight, romance branch or other milestone you may want to revisit.
- Cross Progression: the built-in account-based feature for continuing on another platform. CD PROJEKT RED Support says, “Cross progression provides the latest save for every save type.” That means it is a current-state sync, not an archive of every older save you have made.
A safe routine is therefore: make and retain local manual saves for important branches, then create a fresh save specifically for a platform move and wait until its cloud icon appears. On the destination, sign in with the same CD PROJEKT RED account and load that uploaded save. Keep the original local saves until you have confirmed that the transferred game opens correctly.
Recommended Free Tools
What Cross Progression actually transfers
It keeps the latest save in each save type
Cross Progression does not present a browsable historical backup of every manual save or every earlier decision. Its documented scope is the latest save for each save type. In practical terms, the service can expose the current latest manual save, autosave or checkpoint associated with your account, but it should not be treated as a vault for an entire local save list.
#1 Best Overall
- 1205504
- High-quality material
- Durable
- robustness
If you have several local versions of the same branch, create the exact one you want to move immediately before changing platforms. Then verify that this new entry has the cloud icon. An account connection by itself does not prove that an older local save has been uploaded.
Local saves remain useful even when you use the cloud
Use local manual saves for decisions that you may want to undo, such as starting a major quest, choosing between two dialogue outcomes or entering a point of no return. Give each meaningful branch a recognizable name, for example “Novigrad-before-choice” or “Skellige-main-quest-2.” The name is for your own organization; the important protection is keeping the file and not overwriting it with a later branch.
| Goal | Best method | What it protects |
|---|---|---|
| Keep an alternate quest outcome | Local manual save made before the decision | A branch you can revisit on the same platform |
| Preserve a major milestone | Local manual save with a descriptive name | A known checkpoint independent of autosave rollover |
| Continue on another platform | Cross Progression after a new save shows the cloud icon | The latest save of each supported save type |
| Keep a complete historical archive | Not established by the official Cross Progression documentation | Do not assume every older local save is retained online |
Prepare both platforms before moving a save
1. Update the game
Install the latest patch available for the platform you are leaving and the platform you are joining. CD PROJEKT RED’s Cross Progression instructions specifically tell players to check that the game is current. An outdated installation can make a save appear missing when the real issue is a version or feature mismatch.
2. Confirm the product edition
Check whether each installation is the base game, the Game of the Year (GOTY) edition or the Complete Edition. On consoles, CD PROJEKT RED says saves are not compatible between the base version and the GOTY/Complete Edition because the console treats them as separate products. A local save from one of those products will not simply appear in the other product’s local Load Game list.
If you are moving from a base console installation, the publisher identifies Cross Progression as the route for continuing that progress rather than copying the local save directly. Still verify the destination edition and patch before you begin; Cross Progression is not a reason to skip compatibility checks.
3. Check your account
You need a CD PROJEKT RED account. Decide which account will own the transfer before you connect anything. The destination must use the same account; a different account can make a correctly uploaded save look absent.
4. Check mods before creating the transfer save
For a modded save, CD PROJEKT RED advises enabling the same compatible mod set on both platforms. A missing or incompatible mod can prevent the save from loading correctly. If you cannot reproduce the mod setup on the destination, create a separate unmodded save only after you understand what content or scripts the modded game has changed.
The Tool Desk
Outbyte PC Repair FREEClear out junk files and repair common Windows errorsFree Scan →Outbyte Driver Updater FREEScan for outdated or missing drivers - takes under a minuteDriver Scan →On consoles, achievements and trophies are disabled on modded saves. That consequence applies even when the save itself can be loaded, so decide whether achievement progress matters before using a modded transfer.
How to upload a save with Cross Progression
- Open the game’s Load Game area. Look for the on-screen Cross Progression command.
- Connect the game to your CD PROJEKT RED account. Complete the sign-in or linking flow shown by the game.
- Check the setting if needed. Cross Progression is enabled by default after the account is connected. You can review or toggle it under Options → Gameplay → Cross Progression.
- Return to your local save list. Choose the branch or checkpoint you actually intend to move, rather than relying on an older save that happened to be present when you linked the account.
- Create a fresh save. Make a manual save with a clear name at the desired point. This gives you a known upload candidate and a local fallback.
- Wait for the cloud icon. Confirm that the cloud icon appears beside that save’s name. Do not shut down, change platforms or delete the local file while the upload is unconfirmed.
The cloud icon is your practical confirmation that the selected save has been sent through Cross Progression. Merely seeing your account connected, or seeing an older save in the list, is not equivalent confirmation.
How to load the save on another platform
- Install and update the game on the destination platform, and verify its edition before launching the transfer.
- Open My Rewards. Connect the destination game to the same CD PROJEKT RED account used for the upload.
- Open Load Game. Look for the uploaded save in the list. The game should expose the latest save for each save type associated with that account, not every historical local entry.
- Load the intended file and test it. Move around, open the map and inventory, and confirm that the expected quest state and character level are present before you make new progress.
- Keep the original platform untouched for now. Do not delete the source saves until you have confirmed that the destination file is the correct branch and that it continues to save normally.
If the file opens successfully, make another manual save on the destination and wait for its cloud icon before treating the move as complete. That gives you a new confirmed point from which to return to the other platform later.
A practical system for managing many local saves
Use manual saves for decisions, not every minute
Autosaves are convenient but can change as you travel, fight or advance a quest. Reserve manual saves for moments you would genuinely want to revisit: before a major dialogue choice, before a contract or boss encounter, before starting a long quest chain, and after completing a milestone you would hate to repeat.
Name saves by location and decision
A useful naming pattern is region – quest – purpose, such as Velen – Family Matters – before choice. Put the decisive moment in the name, not just a date or a generic word such as “save.” This makes the correct branch easier to identify when the list contains many entries.
Keep a small set of permanent checkpoints
Protect a few saves that represent major chapters or alternate outcomes. You do not need to preserve every routine travel save. Because the official material reviewed does not publish a universal manual-save slot limit or retention behavior for every platform, inspect your own list and remove only files you have deliberately judged disposable.
Rank #2
- If you buy this game, you will receive a free next-gen update on December 14th!
- Play as a highly trained monster slayer for hire.
- Built for endless adventure, the massive open world of The Witcher sets new standards in terms of size, depth and complexity.
- The Witcher 3: Wild Hunt Game of the Year edition brings together the base game and all the additional content released to date.
Separate transfer saves from experiments
When preparing to switch devices, create a clearly named transfer save after all decisions are finished. Do not use an experimental mod, a temporary branch or an autosave as the only copy you intend to move. The transfer save should be a local manual save with a visible cloud icon before you leave the source platform.
Edition mismatches: why a save can appear to be missing
The most important edition distinction is on consoles. The base game and the GOTY/Complete Edition are treated as separate products, and their local saves are not compatible according to CD PROJEKT RED. A save may therefore be healthy yet absent when you open the other product’s Load Game menu.
Outdated Drivers Are Slowing You Down
One free scan finds every outdated or missing driver and matches the right update for your exact hardware.Free scan · exact hardware matchPC Slower Than It Used to Be?
A free scan shows the junk files, broken settings and background clutter dragging Windows down - then fixes them in one click.Free scan · Windows 10 & 11Use this order when moving between editions:
- Identify the exact edition that created the source save.
- Identify the exact edition installed on the destination.
- Update both installations.
- Use the publisher’s Cross Progression procedure rather than assuming a direct local-save handoff will work.
- Keep the source installation and its local saves until the destination has loaded and verified the correct progress.
Do not “fix” an edition mismatch by deleting source files or repeatedly overwriting destination saves. Deletion cannot convert a save from one console product into the other.
Mods and transferred saves
Match the mod environment
A save that depends on modified quests, scripts, items or world data may fail to load when the destination lacks those same compatible mods. Before transferring, record the enabled mod set and reproduce it on the receiving platform where the platform supports mods. Keep versions compatible with the game patch on both ends.
Know the console achievement consequence
CD PROJEKT RED states that console achievements and trophies are disabled on modded saves. If you want achievement progress, use an appropriate unmodded save rather than assuming that transferring the file will restore eligibility.
Use a separate unmodded branch when necessary
If the destination cannot run the required mods, do not overwrite your only copy while testing. Keep the modded local branch, then make and upload a separate save that is safe for the destination. Whether that unmodded branch is viable depends on what the mods changed; a save created after extensive mod use may still depend on mod content.
Do these 3 things before closing this tab:
1Fix the driver behind crashes, sound loss and screen glitches2Clear out junk files and repair common Windows errors3Scan for outdated or missing drivers - takes under a minuteTroubleshooting when a save is not visible
The cloud icon never appears
- Confirm that the game is connected to the intended CD PROJEKT RED account.
- Check that Cross Progression is enabled under Options → Gameplay → Cross Progression.
- Return to Load Game and create a new manual save, then wait rather than assuming an older file uploaded.
- Make sure the game is fully updated and connected before switching away.
- Keep the local file; do not delete it while upload status is uncertain.
The destination shows the account but not the expected branch
- Verify that the destination uses the same CD PROJEKT RED account, not merely the same console or PC profile.
- Remember that Cross Progression exposes the latest save for each save type, not an unlimited historical list. The branch you expected may not be the latest one.
- Check the source save’s cloud icon and its name.
- Confirm both editions and patches.
- If the source save is modded, match the mod set or test a compatible unmodded branch.
The file appears but will not load
- Check for a base-versus-GOTY/Complete mismatch on consoles.
- Check that the destination has the same compatible mods enabled.
- Confirm that both installations are current.
- Return to the source platform and preserve the original local save before trying another conversion, overwrite or branch.
The loaded game has the wrong progress
Stop making new saves on the destination until you identify the branch. Compare the displayed save name and timestamp with the source list, then locate the intended manual save. If it never had a cloud icon, it was not confirmed as the uploaded file; create a fresh transfer save from the correct local branch.
Switch and older cloud-integration guidance
Some older instructions for Switch refer to Steam or GOG cloud integration. The official Switch support information identifies Cross Progression introduced in update 4.04 as the feature Switch users need when moving from that earlier arrangement. For a current transfer, follow the in-game Cross Progression and account-linking procedure described above instead of treating the older integration as the present workflow.
What is not documented as a universal rule
The official material reviewed does not state one manual-save slot limit or one retention policy that applies to every platform and edition. It also does not establish that every old local save remains available indefinitely after newer saves are created. Community claims about a single universal number should therefore not drive deletion decisions.
The conservative response is simple: inspect the save list on your own platform, preserve meaningful checkpoints, and delete only files you can identify as disposable. Before a major update, edition change or platform move, keep at least one untouched local checkpoint in addition to the cloud-confirmed transfer save.
Free tools Windows power users keep installed
One-click scans. No signup required.
A repeatable pre-switch checklist
- Game patched to the latest version available on both platforms.
- Source and destination editions identified as base, GOTY or Complete.
- Same CD PROJEKT RED account available on both platforms.
- Cross Progression enabled under Options → Gameplay → Cross Progression.
- Fresh manual transfer save created from the intended branch.
- Cloud icon visible beside that save’s name.
- Mod set matched, or an appropriately unmodded branch prepared.
- Original local saves retained until the destination file is opened and verified.
The safest long-term routine
At the end of a meaningful play session, make a named local manual save. Before a major choice, make another checkpoint rather than relying on an autosave. When you want to play elsewhere, create one final transfer save, wait for its cloud icon, and then sign in to the same account through My Rewards on the destination. After loading, verify the quest state and create a new destination save before deleting anything on the source platform.
This division of labor keeps local saves responsible for history and alternate choices while Cross Progression handles current continuation. It also gives you a clear recovery path when an edition, account, patch or mod mismatch makes a transferred file appear missing.
Quick Recap
Product prices and availability are accurate as of the date/time indicated and are subject to change. Any price and availability information displayed on Amazon at the time of purchase will apply.
