Inscryption is narrative-state heavy; back up the complete Daniel Mullins GamesInscryption directory before altering or replacing SaveFile.gwsave so recovery remains possible.
For this PC reference, the documented storage is Windows: %USERPROFILE%AppDataLocalLowDaniel Mullins GamesInscryption. The known file or folder pattern is SaveFile.gwsave and related backup/progression records. Inscryption keeps its principal progression in a game-specific LocalLow save file with companion/recovery context. Story progression is highly stateful, so preserve the whole directory before experimentation.
Backup guidance: Close Inscryption, let the launcher finish any synchronization, then copy the complete documented save directory to a dated folder outside the live path. Preserve companion files rather than selecting only the newest-looking record. Cloud support is storefront-dependent and can restore a different SaveFile after a manual replacement. Launcher and cloud context matters because The active Steam, GOG installation determines which local profile and cloud copy can overwrite the save. Identify the storefront and account before restoring files.
Compatibility and recovery should stay conservative. Treat saves as version-, storefront-, account-, and mod-sensitive unless the game or a separately verified migration workflow proves otherwise. A similar filename or extension is not evidence that two releases are interchangeable. If the expected progress is not visible, If progress is missing after a restore, confirm the active Windows account, storefront/profile, cloud state, and exact directory first. Restore the untouched backup before experimenting with individual files or older autosaves. SaveEditor.com only labels a game-specific editor as available when a separate linked Tool has a verified operational runtime; this reference page by itself is not an editor claim.