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.
Start with the least destructive explanation
When The Witcher 3: Wild Hunt progress appears missing, first verify the active PC location: Windows: %USERPROFILE%DocumentsThe Witcher 3gamesaves | Linux / Steam Play: Steam Play: <SteamLibrary-folder>/steamapps/compatdata/292030/pfx/. Expected files/folders: *.sav
*.png. Many apparent save failures are actually profile, storefront, path-redirection, or cloud-selection problems rather than damaged game data.
Preserve every surviving copy
Copy the entire gamesaves directory so manual, automatic, checkpoint, and preview files remain together. Before renaming, moving, replacing, or opening candidate backups, copy them outside the live directory. Do not use the only surviving file as the test specimen for repair or editing.
Check launcher and cloud state
Storefront context: 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. Cloud notes: Steam, GOG, Epic, and EA cloud support are documented. The current game also supports cross-save with console versions through the supported account workflow. A sync client can reintroduce an older or newer version after a manual restore, so recovery work should keep local and cloud copies conceptually separate until the wanted progress is confirmed.
Use format and compatibility clues
The gamesaves directory contains .sav records and associated .png preview images. The save payload and screenshot are separate files. 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 file exists but is ignored, compare the complete directory structure, slot/profile naming, game edition, mods/DLC, and any companion metadata. Do not assume an extension change or generic checksum tool can repair a game-specific container.
Game-specific troubleshooting
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. If a known-good backup works, preserve it and create a fresh in-game save before further experiments. If no copy works, prefer read-only inspection and source-backed game-specific tooling over repeated writes.
Verification context: Windows/Steam Play save paths, .sav/.png files, storefront cloud support, and cross-save note were reviewed against current PCGamingWiki coverage.