Well Dweller Save Location and Recovery

The Well Dweller save location for the Windows Steam recovery procedure is %LOCALAPPDATA%\WellDweller. An active slot can be named WellDweller1, with its backup named BACKUP_WellDweller1. Close the game and copy the whole folder first. If an old save crashes on loading, reset the Settings file, then restore the matching non-empty backup only if the active save is zero bytes.

Kyle Thompson publishes this recovery sequence in the September 26 update announcement and repeats it in the September 27 developer notes. The folder-copy and rollback steps below protect your files while following that sequence. The path is for the Windows case described by the developer; use it for that installation rather than treating it as a universal console-save path.

Open the Windows save folder

1. Close Well Dweller before working with its files.
2. Press Windows + R to open Run.
3. Paste %LOCALAPPDATA%\WellDweller and press Enter.
4. Find your active numbered slot, its matching backup and the file named Settings.

%LOCALAPPDATA% opens the current Windows account's local AppData directory. In the developer's example, the full path is C:\Users\Your Name\AppData\Local\WellDweller. Using the environment shortcut avoids accidentally looking inside another user's folder or typing “Your Name” literally.

If File Explorer opens a different account's files, stop and select the account where you played. You can paste the same shortcut into Explorer's address bar. AppData is normally hidden during manual browsing, so using the path directly is easier than searching each folder by hand.

For a healthy run, you can stop here and make a manual backup. The reset and replacement procedure is intended for a loading problem; finding the folder is not a reason to alter a working save.

Make a recovery copy before changing anything

Copy the complete WellDweller folder into another directory, with a recognizable name such as WellDweller-before-recovery-2026-10-02. Keep this copy outside the live save folder. Include the active files, backups and Settings file, rather than copying only the slot you think is damaged.

In File Explorer, enable file-name extensions if they are hidden. Compare the complete names shown in your folder before renaming anything. The developer's examples use WellDweller1 and BACKUP_WellDweller1; preserve any extension present in your actual installation instead of creating an extra one accidentally.

Use the Size column or each file's Properties to check its actual size. A zero-byte file has no saved data. A file larger than zero has content, although size alone does not prove every part of it is valid. The developer's sequence uses this check to decide which branch to try.

Reset Settings and test a non-empty active save

The first developer instruction is to remove the file named Settings. After copying the folder, delete that file from the live directory while leaving your numbered saves in place. Then launch the game and try the affected slot if its active file is larger than zero bytes.

This step keeps the two kinds of files separate: Settings stores configuration, while the numbered file is the slot you want to load. Inspect your controls and display options after the reset before starting a difficult room. Reapply the settings you need for your controller or keyboard.

If the slot loads, check the current area, inventory and most recent objective, then test a normal save and reload. Keep the recovery copy until those checks succeed. You do not need to replace a functioning non-empty slot merely because a backup is also present.

If a non-empty slot still fails after the Settings reset, preserve both files and report the failure with your platform, version and file sizes. The official sequence does not guarantee that every non-empty file is recoverable, so keep your original evidence available for support.

Restore a backup when the active slot is zero bytes

Follow this branch only after making the copy above and confirming the numbered active file is empty.

1. Locate the backup for the same slot. For WellDweller1, use BACKUP_WellDweller1, not another numbered backup.
2. Confirm that the matching backup is larger than zero bytes.
3. Remove the zero-byte active file from the live folder.
4. Rename the healthy backup to the active file's exact name, removing only BACKUP_ from the filename.
5. Launch the game and load that slot.

The developer's example restores slot 1. If your affected slot has another number, match that number throughout. Replacing slot 2 with a slot 1 backup would load a different run, which is why the filename check comes before deletion or renaming.

If the matching backup is also zero bytes, stop this procedure and keep your folder copy. An empty file cannot supply progress. Repeated renaming does not turn it into a healthy save. If several backups exist, preserve all of them so the developer can see the available recovery files.

Check your progress after recovery

A backup may be older than the run you remember. Check the area, ability inventory and recent pickups before immediately saving over it. This tells you how much progress the recovered file actually contains and lets you plan the route you need to repeat.

Install the September 26 update before continuing a recovered Steam run. The announced correction prevents the specific save-and-pause timing trigger; backup recovery deals with damage that already happened. After you confirm the restored slot saves and reloads normally, create a fresh manual copy without discarding the original recovery folder yet.

If your real problem is a missing reward after returning spirits, use known bugs instead of assuming the save file is empty. A loadable slot and a reward-state issue are different symptoms, and the file-size test helps separate them.

Windows, handhelds and other editions

Use this path when you are running the Windows Steam edition, including a handheld running Windows. For SteamOS, console editions or a different storefront, identify that edition's storage location before copying or changing files. A Steam Deck compatibility badge describes playability, not identical Windows folder paths.

Reviewed October 2, 2026 against the two developer sources linked above. The original recovery uses the Settings reset, file-size branch and matching backup rename. The protective copy, slot comparison and post-recovery checks are this wiki's added procedure for making those steps easier to follow and reverse.