Cyberpunk 2077 is organized around save-slot folders rather than a single global save. Keeping the folder together matters because the main sav.dat payload sits beside metadata used to describe the slot. A robust backup copies the entire slot or, preferably, the full Cyberpunk 2077 save directory. Cross-progression adds a second synchronization layer, so a local restore should be completed while the game is closed and before a remote copy is allowed to win a conflict.
Identify the exact save you intend to edit
The researched Cyberpunk 2077 PC save location is Windows: %USERPROFILE%Saved GamesCD Projekt RedCyberpunk 2077 | macOS: $HOME/Library/Application Support/CD Projekt Red/Cyberpunk 2077/saves | Linux / Steam Play: Steam Play: <SteamLibrary-folder>/steamapps/compatdata/1091500/pfx/. Known file/folder pattern: sav.dat
metadata.*.json
screenshot.png. Storefront context: Steam, GOG Galaxy, Epic Games Launcher, REDlauncher. All storefronts ultimately use the local save area documented here, while cross-progression depends on CD PROJEKT account/launcher services rather than a simple folder copy. Do not edit a similarly named file from a different profile, edition, or cloud cache.
Make an untouched backup first
Copy complete save-slot folders, or copy the entire Cyberpunk 2077 save directory. Do not separate sav.dat from its metadata when creating archival backups. Keep that copy outside the live save directory and do not overwrite it with later experiments. Cloud context: Steam Cloud, GOG Galaxy, and Epic cloud support are documented. Cross-progression cloud synchronization requires the CD PROJEKT/REDlauncher flow. If a launcher can synchronize the save, prevent it from silently replacing either the original or edited copy while testing.
Understand the format boundary
Cyberpunk 2077 stores saves as slot directories. A slot contains the main sav.dat payload plus metadata and, commonly, a screenshot. The slot directory should be treated as one save unit. File-extension context: .dat, .json, .png Compatibility note: Cross-progression is a service-backed workflow. Local folder copies and cross-progression are related but not identical operations. 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 Cyberpunk 2077, 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 slot is absent in-game, verify that the entire slot folder was restored. If cloud or cross-progression is active, compare timestamps before allowing the remote copy to overwrite a manual restore. Return to the untouched backup before trying another change.
Verification context: Windows, macOS, Steam Play paths and cross-progression/cloud notes were reviewed against current PCGamingWiki coverage.