Big Walk Save File Location (Windows, macOS & Linux)

Big Walk stores its save files at %USERPROFILE%\AppData\LocalLow\House House\Big Walk\user_data\save_games on Windows. Checkpoint64 already knows this folder — it backs it up automatically and keeps every version, so a corrupted or overwritten save is one click from restored.

Good to know: Linux paths unconfirmed

Where Big Walk saves are stored

  • Windows%USERPROFILE%\AppData\LocalLow\House House\Big Walk\user_data\save_games
    or %USERPROFILE%\AppData\LocalLow\House House\Big Walk\user_data\save_games
  • macOS~/Library/Application Support/House House/Big Walk/user_data/save_games
  • Linux~/.var/app/com.valvesoftware.Steam/.local/share/Steam/steamapps/compatdata/1478500/pfx/drive_c/users/steamuser/AppData/LocalLow/House House/Big Walk/user_data/save_games

Where two locations are listed, which one is in use depends on the install (Checkpoint64 checks them in order and uses the first that exists).

The save data here is .sav files — back up the folder as a set, not single files, so a restore always keeps them consistent.

How to open the save folder

  • Windows — press Win+R, paste %USERPROFILE%\AppData\LocalLow\House House\Big Walk\user_data\save_games, and press Enter (the AppData folder is hidden in Explorer, which is why this path is so easy to miss — pasting it skips the hunt).
  • macOS — in Finder press Cmd+Shift+G (Go to Folder) and paste ~/Library/Application Support/House House/Big Walk/user_data/save_games.

Backing up Big Walk saves automatically

  1. Install Checkpoint64 (free) and pick Big Walk — the save path above is already preset.
  2. Auto-backup watches the folder and uploads a new version whenever it changes, keeping full history.
  3. Restore any version in one click if a save corrupts, gets overwritten, or a mod breaks it.

Sharing Big Walk saves with friends

Big Walk has co-op, so the folder above usually lives on one person's PC — whoever hosts. When they're offline nobody else can carry on, and if two people play separately, one session quietly overwrites the other.

Checkpoint64 lets a small group pass one Big Walk world around instead of renting a dedicated server. Whoever plays next takes a server-enforced lock, pulls the latest save, plays, and pushes it back; everyone else stays read-only until the lock frees up, so nobody saves over anybody. Every version is kept, so a bad session is one restore away. The dedicated server alternative guide walks through the full take-turns flow.

Common questions

Where does Big Walk store save files on Windows?

Big Walk keeps its saves at %USERPROFILE%\AppData\LocalLow\House House\Big Walk\user_data\save_games or %USERPROFILE%\AppData\LocalLow\House House\Big Walk\user_data\save_games. AppData is a hidden folder — paste the path into Explorer or the Win+R box to jump straight there. Checkpoint64 already knows this path and backs the folder up automatically.

Can I back up Big Walk saves automatically?

Yes — Checkpoint64 watches Big Walk's save folder and uploads a new version every time it changes, so you get automatic backups with full version history. Free download for Windows, macOS, and Linux.

How do I restore an earlier Big Walk save?

With Checkpoint64, open the save's version list and restore any earlier version in one click — it puts those exact files back in Big Walk's save folder. Without a backup tool there's usually nothing to go back to: the folder only holds the latest files.

Can I share Big Walk saves with friends?

Yes. Checkpoint64 syncs the Big Walk save folder to a shared team, so a friend can pull the latest world and keep playing even when the host is offline. A server-enforced lock means only one person can push a new save at a time, so two people can't overwrite each other — it's how a small group takes turns hosting without paying for a dedicated server.