Big Walk Save File Location, Backup and Host Transfer Guide

Big Walk saves progress automatically, but the save belongs to the host—not to every person who joined. The official FAQ confirms that the host is the keeper of shared progress and must host again when the group returns.

Windows save location reported by players

A Steam Community answer gives this folder:

%userprofile%\AppData\LocalLow\House House\Big Walk\user_data\save_games

This exact path is player-reported, not published in the official FAQ. Paste it into File Explorer’s address bar or browse there manually. If the folder is absent, first make sure the Windows host has created and loaded at least one game, then check the spelling and the currently signed-in Windows account.

The official FAQ establishes autosaving and host ownership; it does not publish a supported file-transfer procedure. Console saves and the Mac versions are managed differently, so do not invent equivalent folders by changing the Windows path.

Make a safe backup

1. Have every player leave the session.
2. Close Big Walk completely on the host computer.
3. Open the reported save_games folder.
4. Copy the relevant file—or the entire folder—to a dated backup folder outside the game directory.
5. Keep the original untouched until the backup has been tested.

Make the copy with the game closed. Copying while the game writes progress risks an incomplete or conflicting file. Do not edit the JSON by hand unless you accept that the save may become unreadable.

Transfer hosting to another Windows player

The community method is to close the game on both computers, copy the host’s save file, and place it in the recipient’s save_games folder. A Steam responder said the copied file should then appear as a hostable save. The same responder described the file as plain JSON containing completed challenges and restored items.

That procedure is useful but remains a single ordinary-player answer without an original-poster confirmation. Back up both machines first. Never overwrite the recipient’s folder blindly: preserve their existing saves, then copy the transferred file alongside them when possible.

What transfers—and what may not

Treat the world’s completed challenges and host-owned progress as the likely payload. Player identity, platform achievements, settings, cloud state and every carried object may not map cleanly. Steam players separately reported that important or held items can appear at spawn or Lost and Found, while some dropped prizes may return to their original puzzle after reloading. Those are community observations, not a formal save schema.

Community report

Steam has direct questions from groups that need another member to host after crashes or schedule changes. That is a real workflow gap, but no official migration tool is documented. Use the manual copy only as a reversible backup-and-test operation, and keep the original host save until the group verifies the new session.