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.
Which storefront context matters
Documented Vampire Survivors PC launchers/storefronts: 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. The active storefront/account should be identified before any restore because cloud and local storage may not use the same path or container across editions.
Documented cloud behavior
Steam Cloud, Epic cloud, and Xbox Cloud are documented. Cloud synchronization is useful for continuity, but it can also turn a restore into a conflict-resolution event. Let synchronization settle before making a manual backup, and keep an offline copy outside any folder monitored by the launcher or operating-system sync service.
Local save roots still matter
The researched local save boundary is 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>; the known file or folder pattern is SaveData.sav in the local save tree; backup copies are kept under the savesbackups structure.. A cloud-enabled game still has concrete local data involved in ordinary play, and that local context is what you need when identifying which copy was modified most recently.
Avoid accidental overwrite loops
Back up the complete saves directory including its backups subfolder before using the in-game delete/reset workflow or manually replacing SaveData.sav. When restoring, close the game and launcher, preserve both the current local copy and the backup you want to test, then place the intended data in the matching profile/storefront location. Do not repeatedly open the game between different copies without noting which side the cloud client selected.
Compatibility and conflict checks
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. If progress disappears or rolls back, 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. Resolve identity/path/cloud questions first. A cloud conflict is not proof that the save itself is corrupt, and a successful upload is not proof that files from another storefront are compatible.
Verification context: Reviewed against current PCGamingWiki Vampire Survivors save locations and documented manual backup/restore behavior.