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.
Where The Witcher 3: Wild Hunt stores PC saves
The researched save-location boundary is Windows: %USERPROFILE%DocumentsThe Witcher 3gamesaves | Linux / Steam Play: Steam Play: <SteamLibrary-folder>/steamapps/compatdata/292030/pfx/. The known file or folder pattern is *.sav
*.png. This is the practical starting point because launcher, profile, and storefront context can change which copy is active even when two folders look similar.
Storefront and profile differences
Documented launchers or 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. When looking for a missing save, identify the executable/storefront you actually launched and the user/profile that created the progress before copying anything between directories.
Cloud synchronization
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 cloud service should be treated as another copy of the save, not as proof that the local folder is disposable. Before a manual restore, let synchronization finish, make an offline backup, and avoid starting the game while files are being replaced.
What the files represent
The gamesaves directory contains .sav records and associated .png preview images. The save payload and screenshot are separate files. The current filename/folder evidence is *.sav
*.png. File-extension context: .sav, .png A location guide does not claim that every file in the directory is safe to edit or that files from another storefront are automatically interchangeable.
If the save is not where expected
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. Also check redirected Documents folders, Steam Play prefixes, account IDs, and launcher-specific containers where applicable. Preserve every candidate copy before testing a restore so troubleshooting does not destroy the only surviving version.
Verification context: Windows/Steam Play save paths, .sav/.png files, storefront cloud support, and cross-save note were reviewed against current PCGamingWiki coverage.