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.
Start with the least destructive explanation
When Cyberpunk 2077 progress appears missing, first verify the active PC location: 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/. Expected files/folders: sav.dat
metadata.*.json
screenshot.png. Many apparent save failures are actually profile, storefront, path-redirection, or cloud-selection problems rather than damaged game data.
Preserve every surviving copy
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. Before renaming, moving, replacing, or opening candidate backups, copy them outside the live directory. Do not use the only surviving file as the test specimen for repair or editing.
Check launcher and cloud state
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. Cloud notes: Steam Cloud, GOG Galaxy, and Epic cloud support are documented. Cross-progression cloud synchronization requires the CD PROJEKT/REDlauncher flow. A sync client can reintroduce an older or newer version after a manual restore, so recovery work should keep local and cloud copies conceptually separate until the wanted progress is confirmed.
Use format and compatibility clues
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. Cross-progression is a service-backed workflow. Local folder copies and cross-progression are related but not identical operations. If the file exists but is ignored, compare the complete directory structure, slot/profile naming, game edition, mods/DLC, and any companion metadata. Do not assume an extension change or generic checksum tool can repair a game-specific container.
Game-specific troubleshooting
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. If a known-good backup works, preserve it and create a fresh in-game save before further experiments. If no copy works, prefer read-only inspection and source-backed game-specific tooling over repeated writes.
Verification context: Windows, macOS, Steam Play paths and cross-progression/cloud notes were reviewed against current PCGamingWiki coverage.