Where Are Tacoma Save Files Located?
Where Tacoma keeps its Unity saves and options files on each desktop OS, plus the Store variant path.
Last updated
Tacoma saves Unity-style per OS: LocalLow on Windows, Application Support on Mac, XDG config paths on Linux. Saves and options share the company folder with numbered JSON files. Microsoft Store builds redirect to a packages path instead.
The Epic cloud folder hints at sync without replacing local copies. Options live in a named JSON beside the saves rather than the registry alone. Back up the whole company folder; the files are small and few. Store copies per playthrough for easy revisits later.
Where Tacoma stores this, by platform
%USERPROFILE%\AppData\LocalLow\Fullbright\Tacoma
Unity saves and TacomaOptions.json together in the company folder. Store builds redirect to packages wgs instead. Proton mirrors this tree in compatdata on Linux. Copy whole folders with the game closed.
~/Library/Application Support/com.fullbright.tacoma
Same Unity layout under Application Support. Cloud sync supplements but never replaces local copies. Reveal Library through the Option-key Go menu.
~/.config/unity3d/Fullbright/Tacoma
XDG config home with matching save JSON names. Proton builds instead mirror the Windows tree in compatdata. Native and Proton paths never mix on one machine.
Frequently asked questions
how do I back up Tacoma saves
Copy the Fullbright folder with the game closed to move saves and options together. Per-OS roots differ while inner names match. Cloud builds sync separately; manual copies guard reinstalls.
how do I tweak Tacoma settings
Edit TacomaOptions.json with the game closed for graphics and gameplay tweaks. Registry keys on Windows mirror some of the same values. Keep a copy before hand edits; malformed JSON resets options.
where are saves on Linux
Yes through Proton with the standard compatdata mirror of the Windows tree. Continue inside pfx to the LocalLow path. Same Unity layout as native Windows.
Notice an outdated path? Let us know.