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.
Known Cyberpunk 2077 save-file structure
The researched filename or folder pattern is sav.dat
metadata.*.json
screenshot.png. File-extension context: .dat, .json, .png The documented format notes are: 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.
Why an extension is not enough
A save filename can identify a likely container, but it does not prove the internal schema, game version, checksum rules, encryption state, or editability. Cross-progression is a service-backed workflow. Local folder copies and cross-progression are related but not identical operations. SaveEditor therefore separates file identification from Tool compatibility and only labels a game-specific Tool Verified when its exact profile/version evidence passes the runtime gate.
Where the format is stored
PC save locations: 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/. 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. This matters because two releases can use different containers or companion files even when the visible slot name is similar.
Back up before inspecting or editing
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. A read-only viewer is lower risk than a writer, but the live save should still be copied first. Cloud context also matters: Steam Cloud, GOG Galaxy, and Epic cloud support are documented. Cross-progression cloud synchronization requires the CD PROJEKT/REDlauncher flow. Keep the original bytes available so any experiment can be reversed without relying on a cloud service or automatic backup.
What this reference does not claim
This page does not infer an undocumented checksum algorithm, encryption key, compression layer, or cross-store conversion from the file extension. Troubleshooting evidence: 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. Those questions require a verified parser/profile or a game-specific source, not a generic format guess.
Verification context: Windows, macOS, Steam Play paths and cross-progression/cloud notes were reviewed against current PCGamingWiki coverage.