Baldur’s Gate 3 makes the folder boundary important: each save folder contains the .lsv archive and related slot context. Backing up the whole folder avoids separating the main payload from supporting files. Campaigns can also be sensitive to mods, so SaveEditor.com treats mod compatibility as part of restoration rather than calling every failed load corruption. Larian cross-save is useful for recent saves, but a complete local archive is still the better long-term backup.
Where Baldur's Gate 3 stores PC saves
The researched save-location boundary is Windows: %LOCALAPPDATA%Larian StudiosBaldur's Gate 3PlayerProfilesPublicSavegamesStory | macOS: $HOME/Documents/Larian Studios/Baldur's Gate 3/PlayerProfiles/Public/Savegames/Story/ | Linux / Steam Play: $XDG_DATA_HOME/Larian Studios/Baldur's Gate 3/PlayerProfiles/Public/Savegames/Story/. The known file or folder pattern is <save-folder><save-name>.lsv. 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. The same Larian profile hierarchy is used across desktop platforms, with OS-specific base directories. Steam also exposes a remote cloud area. 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 is documented. Larian account cross-save can synchronize a limited set of recent saves across supported PC storefronts/platforms. 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
Each campaign save is stored in its own folder and includes an .lsv archive. Preserve the whole save folder rather than extracting only the archive when making a normal backup. The current filename/folder evidence is <save-folder><save-name>.lsv. File-extension context: .lsv 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
When a campaign save fails after migration, check the exact save folder, mods, and profile before assuming the archive is damaged. Cloud cross-save only covers supported recent saves, not every local backup. 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, Linux, Steam remote/cloud, and Larian cross-save notes were reviewed against current PCGamingWiki coverage.