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.
Where Cyberpunk 2077 stores PC saves
The researched save-location boundary 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/. The known file or folder pattern is sav.dat
metadata.*.json
screenshot.png. This is the practical starting point because launcher, profile, and storefront context can change which copy is active even when two folders look similar.
Storefront and profile differences
Documented launchers or 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. When looking for a missing save, identify the executable/storefront you actually launched and the user/profile that created the progress before copying anything between directories.
Cloud synchronization
Steam Cloud, GOG Galaxy, and Epic cloud support are documented. Cross-progression cloud synchronization requires the CD PROJEKT/REDlauncher flow. A cloud service should be treated as another copy of the save, not as proof that the local folder is disposable. Before a manual restore, let synchronization finish, make an offline backup, and avoid starting the game while files are being replaced.
What the files represent
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. The current filename/folder evidence is sav.dat
metadata.*.json
screenshot.png. File-extension context: .dat, .json, .png A location guide does not claim that every file in the directory is safe to edit or that files from another storefront are automatically interchangeable.
If the save is not where expected
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. Also check redirected Documents folders, Steam Play prefixes, account IDs, and launcher-specific containers where applicable. Preserve every candidate copy before testing a restore so troubleshooting does not destroy the only surviving version.
Verification context: Windows, macOS, Steam Play paths and cross-progression/cloud notes were reviewed against current PCGamingWiki coverage.