Short answer: On Windows, the Steam edition stores its saves in %LOCALAPPDATA%StygianSavedSaveGames. Close the game, copy that entire folder to a separately named location, and verify the copy before deleting or replacing anything. Steam Cloud can move configured files between Steam computers, but it is a synchronization service, not an independent, versioned backup.
Do not assume that path belongs to the GOG edition. GOG provides an offline installer and does not require Galaxy to play, while Galaxy supports cloud saves in general; however, this game’s GOG save path and title-specific Galaxy cloud status have not been established. Moving a save between Steam and GOG therefore requires identifying the GOG folder on your own installation and treating compatibility as unconfirmed.
Where are Stygian: Outer Gods saves stored on Steam?
The verified Windows path for the Steam build is %LOCALAPPDATA%StygianSavedSaveGames. Steam’s published cloud configuration for app ID 2581410 matches files named *.sav. You can inspect that configuration on SteamDB’s Steam Cloud page for the game.
%LOCALAPPDATA% is a Windows shortcut for the local AppData folder belonging to the signed-in Windows user. It is not the game’s installation directory and may be hidden when you browse manually, so the quickest method is to paste the complete path into File Explorer’s address bar and press Enter.
| Edition | What is established | What is not established |
|---|---|---|
| Steam for Windows | %LOCALAPPDATA%StygianSavedSaveGames; Steam Cloud rule includes *.sav |
Whether every file in the folder is a save file |
| GOG for Windows | Offline installer is available; Galaxy is optional for playing | A title-specific save path, Galaxy cloud status, and guaranteed cross-store compatibility |
Do not substitute the save location for Stygian: Reign of the Old Ones. This guide concerns Stygian: Outer Gods.
How do I back up the Steam save folder?
A one-time backup needs no extra application or purchase. A USB flash drive is optional; any separate folder, another internal disk, network location, or removable drive can hold the copy. If the computer itself fails, keep at least one copy away from that computer.
Before you copy anything
- Finish or pause gameplay and exit Stygian: Outer Gods.
- If Steam shows a cloud operation in progress, wait for it to finish before handling local files.
- Choose a destination with a clear name, such as a folder that includes the game and the backup date.
- Do not delete, rename, or move the original live folder as part of the backup.
Windows Steam backup steps
- Open File Explorer and paste
%LOCALAPPDATA%StygianSavedSaveGamesinto the address bar. - Confirm that the folder opens. The Steam configuration identifies
*.savas the cloud-matched pattern, but copying the complete folder is the conservative choice because it preserves any additional files the game may use. - Right-click the
SaveGamesfolder, choose Copy, open your separately named destination, and choose Paste. Copy rather than cut or drag-and-drop so the live saves remain untouched. - Open the pasted folder and check that it contains the expected save files. Compare the folder contents with the source rather than assuming that a completed paste means the backup is usable.
- For protection against disk loss, copy the verified backup to a removable drive or another machine. Eject removable media normally after the copy completes.
The backup is independent of Steam Cloud and can be inspected without launching the game. Repeat the copy after important progress if you want a current manual snapshot.
How do I move a save to another Steam PC?
Use Steam Cloud first when both computers use the same Steam account and the game’s cloud setting is enabled. Steam describes downloading synchronized files before a game launches on another computer. Check the new computer’s progress before manually replacing anything.
- On the original computer, exit the game and wait for Steam’s synchronization to finish.
- On the destination computer, sign in to the same Steam account and install the current Steam edition.
- Allow Steam’s pre-launch cloud download to complete. Start the game and inspect the load menu before copying files by hand.
- If the expected progress is present, quit normally. Make a separate backup of the destination’s current
SaveGamesfolder before experimenting further. - If cloud synchronization is unavailable or the expected save is missing, exit the game. Open
%LOCALAPPDATA%StygianSavedSaveGameson the destination; if the folder already contains files, copy that folder to a safety location first. - Copy the backed-up source files into the destination folder. Do not erase the destination backup or the original source.
- Launch the game and check the load menu. If the save does not appear or the game behaves unexpectedly, exit and restore the untouched destination backup instead of repeatedly overwriting files.
Steam Cloud follows the files and rules configured for the Steam edition. It does not prove that a Steam save can synchronize with a GOG installation.
Can I move a Steam save to the GOG edition?
There is no verified GOG save path or confirmed Steam-to-GOG compatibility for this title, so a transfer is possible only as a cautious experiment rather than a guaranteed procedure.
Identify the GOG folder without guessing
- Install the current GOG edition. Galaxy is not required to launch the game when using the offline installer.
- Start the game, create a disposable save, and exit the game. Also exit Galaxy if it is running.
- Check the Steam-known folder first, but do not assume that a folder there belongs to the GOG build. Identify which directory changed when the disposable GOG save was created. Searching the game’s installation directory alone can miss a user-profile save folder.
- Keep separate copies of both the Steam source and the newly identified GOG destination before attempting a transfer. Name them so the storefront and date are unmistakable.
- With both games closed, copy the relevant save files into the GOG folder. Do not move or delete the originals.
- Launch the GOG edition and inspect its load menu. If the save is absent or causes a problem, close the game and restore the untouched GOG destination backup.
This procedure identifies where the GOG build writes files; it does not establish that the two editions use the same format, release data, or save schema. Keep the original Steam backup even if the first launch appears successful.
Does GOG Galaxy sync Stygian: Outer Gods saves?
Galaxy has a cloud-save system generally, but the examined feature information does not explicitly confirm cloud saves for Stygian: Outer Gods. Do not promise Galaxy synchronization for this game until the title’s own GOG listing or Galaxy client shows a cloud-save setting for the installed build.
The GOG edition can be played without Galaxy, so an offline installation will not automatically gain a cloud copy. If Galaxy presents a synchronization control, verify that it is enabled for this title and wait for synchronization to complete; still keep a manual copy because cloud sync is not a versioned offline archive.
Why did my save not appear on the new PC?
Most missing-save cases come from checking the wrong Windows profile, the wrong storefront folder, or a cloud operation that has not completed. Work through these checks in order.
- Check the Windows account. Paste the full Steam path while signed in as the same Windows user who created the save. Each user has a separate local AppData location.
- Use the full path. The save folder is under
%LOCALAPPDATA%, not normally under the game’s installation folder. Pasting the path is more reliable than browsing from the install directory. - Make a disposable save. Create one new save, exit, and compare recently changed folders. This can reveal the active directory for the installed build without guessing.
- Check Steam synchronization. On Steam, wait for cloud sync to finish before replacing local files. A conflict prompt should be resolved only after preserving both versions.
- Confirm the storefront. A Steam path is evidence for the Steam edition, not for GOG. The app ID
2581410identifies the Steam game but does not, by itself, prove the location of every local file. - Check the game’s load menu. A copied file that exists on disk may still be incompatible with the installed build; do not keep overwriting a working destination while diagnosing.
Will an Early Access save work in version 1.0?
The game entered Steam Early Access on April 14, 2025, and its full release is recorded as October 26, 2026. The publisher says older Early Access saves can be used, but it strongly recommends starting over with a fresh save to avoid technical issues. Its launch announcement states: “However, we strongly advise you to start a new playthrough with a fresh save file to avoid any unexpected technical issues.” Read the announcement on the publisher’s Steam community news page.
Back up the old progress before launching version 1.0 or trying a restore. Keep the old copy in a separately named folder and create a new 1.0 save rather than allowing an experiment to overwrite the only copy. If you choose to test the old save, regard the result as build-dependent and keep the fresh-playthrough option available.
An official April 2026 update also expanded save slots and added manual save/load slot selection, so older descriptions claiming that the game has no manual slots are outdated.
Which save method should I use?
Choose based on whether you need convenience, an independent archive, or recurring protection. These methods are not interchangeable.
| Method | Verified title support | Internet or client dependence | Independent offline copy | Setup effort | Main overwrite risk |
|---|---|---|---|---|---|
| Manual local copy | Steam Windows folder is documented; GOG location must be identified locally | None after files are available | Yes, when copied to separate media or a different machine | Low; repeat after new progress | Copying over a newer destination without first preserving it |
| Steam Cloud | Steam lists cloud support and publishes rules for this title | Steam account, client, and completed synchronization | No; synchronized files are not a separate versioned archive | Low when enabled | Choosing the wrong cloud version during a conflict or syncing an unwanted overwrite |
| GOG Galaxy cloud | Galaxy supports cloud saves generally; this title’s status is not established | Galaxy and an enabled title-specific cloud setting | Not unless you also export a manual copy | Unknown for this title | Assuming a cloud copy exists when the game is not configured for it |
| Windows File History | Can cover the folder when you include it in a backed-up library | Configured external drive or network location | Yes, through recurring copies to that destination | Higher than a one-time copy | Assuming AppData is covered automatically or restoring the wrong snapshot |
How can I make recurring backups with File History?
File History is useful when you want Windows to make repeated copies, but the game’s save folder is not a default library folder. Add the nondefault SaveGames folder to a library that File History backs up, select an external drive or network location, and confirm that the folder appears in the backed-up contents.
- Prepare the external drive or network location that will hold the history.
- In Windows File History settings, enable the chosen destination.
- Add
%LOCALAPPDATA%StygianSavedSaveGamesto a library included by File History; do not assume that merely enabling File History captures AppData. - Let a backup cycle complete, then inspect the destination to verify that the game folder is present.
- Before restoring, preserve the current live folder so a mistaken snapshot can be reversed.
For only this game, a dated File Explorer copy is simpler. File History becomes more useful when you want recurring protection for several folders and are willing to maintain the setup.
How do I verify that a backup is usable?
Verification means checking both the copy and the conditions under which you would restore it.
- Open the backup location and confirm the expected
*.savfiles are present. - Make sure the backup is outside the live
SaveGamesfolder and has a distinct name or date. - Keep the original source until the destination has been inspected.
- When moving between computers, preserve any destination files before copying the source over them.
- After a restore, use the in-game load menu to check for the save; file presence alone is not proof of compatibility.
- For an Early Access-to-1.0 experiment, retain both the old backup and any newly created 1.0 progress.
There is no published game-specific transfer-success rate, save-size measurement, or cross-store compatibility figure for this title. Treat every Steam-to-GOG attempt as unverified and keep a rollback copy.
Frequently Asked Questions
Can I keep an Early Access backup and a new 1.0 save on the same PC?
Yes. Store the Early Access copy outside the live SaveGames folder with a date and version label, and let the 1.0 installation use its own current folder. Before switching between them, copy the currently active folder to a new backup so neither generation becomes your only copy.
Should I copy only the .sav files?
The Steam cloud rule names *.sav, but that pattern does not prove that no other file matters to the game. Copying the entire SaveGames folder preserves any accompanying metadata and makes a later restore less selective.
Why does a different Windows account show no saves?
%LOCALAPPDATA% resolves inside the profile of the signed-in user. A save created under one Windows account will therefore not normally appear when you inspect the equivalent path under another account; sign in to the original account or copy the files deliberately between profiles.
Is the Steam app ID enough to locate the save folder?
No. 2581410 identifies the Steam application, while the save location comes from the game’s user-file configuration. Use the documented path and verify it with an actual save rather than inferring a folder from the numeric ID.