Where Are Journey Save Files Located on PC?
Where Journey keeps SAVE.BIN on Steam and Epic for PC, how the two copies differ, and the Linux path.
Last updated
Journey on PC keeps a single SAVE.BIN that records progress plus recent companions met along the way. Steam builds hold it in an Annapurna folder under LocalAppData with a userdata mirror, while Epic builds use Documents. Timestamps reveal the live copy when both update.
Linux runs through Proton with the familiar compatdata mirror of the Windows tree. Companion names parse out of the binary with community tools for the curious. Journey.cfg beside the save holds settings alone, so config resets never need touching progress.
Where Journey stores this, by platform
%LOCALAPPDATA%\Annapurna Interactive\Journey\Steam
Single SAVE.BIN for progress and companion history plus Journey.cfg for settings. A userdata mirror under app ID 638230 shadows it for cloud sync. Check timestamps when copies disagree. Epic builds instead use Documents Journey.
~/.local/share/Steam/steamapps/compatdata/638230/pfx
Proton prefix for app ID 638230 plus the standard userdata mirror. Continue inside pfx to the Annapurna path. Same binary format as Windows, so cross-platform copies work.
Frequently asked questions
how do I back up Journey saves
Copy SAVE.BIN from the winning location with the game closed, keeping a dated backup first. Check timestamps when two copies exist to find the live one. Cloud and local copies report to each other, so mismatches resolve by recency.
how do I move Epic saves to Steam
Copy SAVE.BIN from Documents Journey into the Steam AppData path to migrate stores. Back up the Steam file first in case versions disagree. Both builds read the same binary format, so the transplant just works.
how do I reset settings only
Delete Journey.cfg beside the saves to reset graphics and settings while keeping progress. The file regenerates on next launch. Wiping SAVE.BIN instead restarts the whole pilgrimage including companion history.
Notice an outdated path? Let us know.