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.
Identify the exact save you intend to edit
The researched The Witcher 3: Wild Hunt PC save location is Windows: %USERPROFILE%DocumentsThe Witcher 3gamesaves | Linux / Steam Play: Steam Play: <SteamLibrary-folder>/steamapps/compatdata/292030/pfx/. Known file/folder pattern: *.sav
*.png. 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. Do not edit a similarly named file from a different profile, edition, or cloud cache.
Make an untouched backup first
Copy the entire gamesaves directory so manual, automatic, checkpoint, and preview files remain together. Keep that copy outside the live save directory and do not overwrite it with later experiments. Cloud context: Steam, GOG, Epic, and EA cloud support are documented. The current game also supports cross-save with console versions through the supported account workflow. If a launcher can synchronize the save, prevent it from silently replacing either the original or edited copy while testing.
Understand the format boundary
The gamesaves directory contains .sav records and associated .png preview images. The save payload and screenshot are separate files. File-extension context: .sav, .png 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. These facts help identify the save but do not automatically reveal every field, checksum, encryption rule, or version-specific structure inside it.
Use only a Tool whose claim matches the file
Generic viewers and diff tools can inspect bytes without claiming game-specific semantics. A game-specific editor should be used only when its Tool page explicitly lists The Witcher 3: Wild Hunt, a matching supported version/container, and a Verified operational runtime. A planned URL or Game Hub is not evidence that an editor exists.
Test the edited copy safely
Write to a new output file when the Tool supports it, keep the original backup, restore the edited copy into the correct profile/storefront location, and launch the game only after the file operation finishes. If the game rejects it, 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. Return to the untouched backup before trying another change.
Verification context: Windows/Steam Play save paths, .sav/.png files, storefront cloud support, and cross-save note were reviewed against current PCGamingWiki coverage.