You do not need to save manually in Big Walk. The host's game saves progress automatically, and House House does not provide a separate manual-save button. When the group wants to continue, the same host loads that journey first and everyone else rejoins.
The important part is choosing the host before your first long session. The host is the keeper of the shared world, so a guest cannot simply open the group's progress when that host is offline. Treat the host slot as the group's master copy.
Big Walk saving at a glance
| Question | Answer |
|---|---|
| Does Big Walk autosave? | Yes, on the host's game |
| Is there a manual save button? | No manual-save step is documented |
| Who owns the shared progress? | The host |
| Can a guest resume without the host? | Not through the normal in-game flow |
| What happens when the host leaves? | Every guest is disconnected |
| Does Steam support cloud saves? | Steam lists Steam Cloud |
This system fits a game intended to be played with the same friends across multiple sessions. It also means the person with the best attendance is usually a better host than the person with the fastest device. The player-count guide can help the group choose the world version before committing.
How to end a session safely
There is no official ritual required to trigger an autosave, but the host should end the session through the game's menu instead of force-quitting the application. Give players time to finish an interaction, return important prizes to a sensible place and stop moving items between characters. Then let the host end the session normally.
When the host stops, all guests are disconnected by design. That disconnect does not mean each guest lost a separate world save; the shared journey remains the host's responsibility. On the next game night, the host should load the existing journey rather than create a new one with the same group name.
Avoid powering off during a save. Players have reported lost or unreadable PC saves after crashes and sudden power failures. House House has not published a guaranteed recovery method, so a normal exit and a backup before a risky experiment are the safer choices.
How to continue your Big Walk world
- The original host opens Host Game and selects the existing journey.
- The host chooses the world version for the expected minimum group size.
- The host loads fully into the world before inviting anyone.
- Friends join through the active friends-list entry or the new Join Code.
- Confirm the expected landmarks and unlocked systems before moving new prizes.
House House says the 2-player, 3-player and 4+ selection can be made whenever the host starts a session. Think of that choice as the minimum number expected to take part, not a hard maximum; a smaller setting is more practical if several friends may leave early. Some things in the world adapt to the selection, but the official FAQ does not describe a separate save for each setting.
The host receives a fresh Join Code each time a session starts. Do not assume the code from the previous night is still the one the group should use. The Join Code guide shows where to find it and how to protect the session with a password.
Can you change the host?
There is no official cross-platform host-transfer button. Through the normal interface, continuing the same journey requires the player who owns the host save. This is why a PS5, Switch 2 or Mac group should decide on a dependable host before investing many hours.
PC players can find and copy local save files, but that is a manual backup technique rather than a supported in-game transfer workflow. Editing the contents of a save or changing its identifiers can make the slot unreadable or cause the game to overwrite another slot. Keep the untouched original and work only on a copy if you understand the risk.
Big Walk save file location on Windows
Community testing and a step-by-step PC video place the local saves here:
C:\Users\<your-name>\AppData\LocalLow\House House\Big Walk\user_data\save_games
AppData is hidden by default. The safest backup is to close Big Walk completely, copy the entire save_games folder to a separate location, and leave the original filenames and file contents unchanged. Add the date to the backup folder name so you know which copy predates a crash or an experimental route.
Steam lists Steam Cloud for Big Walk, but cloud synchronization is not a replacement for a versioned backup. A bad local state can sometimes synchronize too, and a conflict prompt can be easy to answer incorrectly. If Steam asks which copy to keep, compare timestamps before choosing.
What if your progress is missing?
First, confirm that the correct player is hosting and that they selected the original journey rather than a new slot. Check that Steam or the console is signed into the same user account used for the earlier session. If the slot is visible but the group appears in the wrong place, verify a known unlock such as the drawbridge, map room or train before assuming everything is gone.
On Windows, close the game and make a copy of the current save folder before attempting recovery. Some players report success with Windows Previous Versions, but that only works when Windows has actually retained an older snapshot and it is not an official Big Walk recovery guarantee. Do not delete the current files while testing an older copy.
For an unrecoverable or platform-specific problem, contact the official support address listed by House House: help@bigwalk.game. Include the host platform, game version, approximate time of the last good session and whether the game, device or power failed unexpectedly. The troubleshooting guide has a fuller report checklist.