Vampire Survivors is unusually helpful because the game maintains backup copies inside its saves tree, but cloud synchronization can undermine a manual reset or rollback if the wrong copy wins. SaveEditor documents both the local AppData path and Steam’s 1794680 remote file so a player can identify whether a change was made locally or restored by the launcher. The safest recovery is to preserve the whole saves/backups tree, then choose one dated SaveData copy intentionally rather than deleting folders while cloud sync is still active.
Known Vampire Survivors save-file structure
The researched filename or folder pattern is SaveData.sav in the local save tree; backup copies are kept under the savesbackups structure.. File-extension context: .sav The documented format notes are: The game has evolved through multiple storage layouts and storefronts. Current Windows local data uses the Vampire_Survivors saves tree while Steam cloud keeps SaveData under app ID 1794680.
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. Cloud synchronization can immediately recreate a file you intentionally removed. Disable or resolve cloud state before testing a manual rollback so you know which copy wins. 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: Windows/local: %APPDATA%Vampire_Survivorssaves ; Steam cloud mirror: <Steam-folder>userdata<user-id>1794680remoteSaveData ; Epic: %APPDATA%Vampire_Survivors_EGS<user-id> ; Microsoft Store: %LOCALAPPDATA%Packagesponcle.VampireSurvivors_9pv5cyp4vwdsrSystemAppDatawgs<user-id>. Storefront context: Steam, Epic Games Launcher, Microsoft Store. Epic and Microsoft Store have different roots. A Steam cloud file and local SaveData.sav may represent the same progress at different synchronization moments. 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
Back up the complete saves directory including its backups subfolder before using the in-game delete/reset workflow or manually replacing SaveData.sav. 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, Epic cloud, and Xbox Cloud are documented. 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 old progress returns after deletion, check cloud sync. For a manual rollback, copy a dated backup to the live saves directory only after preserving the newest state. Those questions require a verified parser/profile or a game-specific source, not a generic format guess.
Verification context: Reviewed against current PCGamingWiki Vampire Survivors save locations and documented manual backup/restore behavior.