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.
For this PC reference, the documented storage 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. The gamesaves directory contains .sav records and associated .png preview images. The save payload and screenshot are separate files.
Backup guidance: Copy the entire gamesaves directory so manual, automatic, checkpoint, and preview files remain together. Steam, GOG, Epic, and EA cloud support are documented. The current game also supports cross-save with console versions through the supported account workflow. Launcher and cloud context matters because The local Documents path is shared across common Windows storefronts. REDlauncher can also participate in cross-progression services.
Compatibility and recovery should stay conservative. 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 expected progress is not visible, 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. SaveEditor.com only labels a game-specific editor as available when a separate linked Tool has a verified operational runtime; this reference page by itself is not an editor claim.