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.
Prepare the source PC
On the source system, identify the actual Cyberpunk 2077 save root: 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/. The expected file/folder pattern is sav.dat
metadata.*.json
screenshot.png. Close the game, let the active launcher finish writing and synchronizing, then make a complete offline copy rather than transferring a file that may still be open.
Preserve storefront and profile identity
Documented storefronts: 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. A transfer between two PCs is simplest when both systems use the same storefront/account/profile context. If the destination uses a different store or container, treat that as a migration problem rather than an ordinary restore.
Move the complete save boundary
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. Put the copied data on the destination only after confirming the destination save path. If the game creates a new empty save first, keep that new folder as another backup so you can compare structures and revert.
Handle cloud sync deliberately
Steam Cloud, GOG Galaxy, and Epic cloud support are documented. Cross-progression cloud synchronization requires the CD PROJEKT/REDlauncher flow. Decide whether the local transferred copy or cloud copy should be authoritative before launching the game. If possible, preserve both. After the transferred save loads correctly, make a fresh in-game save and let the launcher synchronize normally.
Check compatibility before blaming the transfer
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. Compatibility note: Cross-progression is a service-backed workflow. Local folder copies and cross-progression are related but not identical operations. If the destination does not see the transferred progress, 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. Verify game edition/version, store, profile IDs, redirected folders, and mod/DLC dependencies before editing the save itself.
Verification context: Windows, macOS, Steam Play paths and cross-progression/cloud notes were reviewed against current PCGamingWiki coverage.