The Witcher 3 keeps its Windows saves in one clear Documents directory, making a full-folder backup simple and preferable to selecting individual files. The folder can include many autosaves, checkpoints, manual saves, and preview images, so copying the entire directory preserves history. Modern releases also have cloud and cross-save features; those are useful for migration but they introduce conflict behavior, so a manual offline copy remains the best safety net before testing mods or tools.
Prepare the source PC
On the source system, identify the actual The Witcher 3: Wild Hunt save root: Windows: %USERPROFILE%DocumentsThe Witcher 3gamesaves | Linux / Steam Play: Steam Play: <SteamLibrary-folder>/steamapps/compatdata/292030/pfx/. The expected file/folder pattern is *.sav
*.png. Close the game, let the active launcher finish writing and synchronizing, then make a complete offline copy rather than transferring a file that may still be open.
Preserve storefront and profile identity
Documented storefronts: Steam, GOG Galaxy, Epic Games Launcher, EA app. The local Documents path is shared across common Windows storefronts. REDlauncher can also participate in cross-progression services. A transfer between two PCs is simplest when both systems use the same storefront/account/profile context. If the destination uses a different store or container, treat that as a migration problem rather than an ordinary restore.
Move the complete save boundary
Copy the entire gamesaves directory so manual, automatic, checkpoint, and preview files remain together. Put the copied data on the destination only after confirming the destination save path. If the game creates a new empty save first, keep that new folder as another backup so you can compare structures and revert.
Handle cloud sync deliberately
Steam, GOG, Epic, and EA cloud support are documented. The current game also supports cross-save with console versions through the supported account workflow. Decide whether the local transferred copy or cloud copy should be authoritative before launching the game. If possible, preserve both. After the transferred save loads correctly, make a fresh in-game save and let the launcher synchronize normally.
Check compatibility before blaming the transfer
The gamesaves directory contains .sav records and associated .png preview images. The save payload and screenshot are separate files. Compatibility note: Cross-save is a supported service feature, but a manual PC file copy should still be treated separately from account-backed cross-progression. If the destination does not see the transferred progress, If a restore seems to vanish, compare local and cloud timestamps and check whether the launcher synchronized a newer remote copy. Keep the backup outside the live Documents folder while testing. Verify game edition/version, store, profile IDs, redirected folders, and mod/DLC dependencies before editing the save itself.
Verification context: Windows/Steam Play save paths, .sav/.png files, storefront cloud support, and cross-save note were reviewed against current PCGamingWiki coverage.