Where Does Tarisland Store Settings on PC?
Where Tarisland keeps settings and keybinds in its install folder, and how the Steam Proton path mirrors it.
Last updated
Tarisland keeps settings inside its own install folder rather than Documents or AppData. A Demo tree holds Saved data with Config and SaveGames branches: INI files for graphics and input, plus a SettingSave.sav for keybinds. The launcher opens the install directory directly.
Steam builds on Linux run through Proton, mirroring the same tree inside compatdata for app ID 3126180. Much of the character progress lives server side as with any MMO, so these files carry settings and binds rather than heroes. Back up before hand edits; the game overwrites sloppy INI work silently.
Where Tarisland stores this, by platform
<install-dir>\Demo\Saved\Config\WindowsNoEditor
Install-relative settings tree: GameUserSettings.ini for graphics, SettingSave.sav for binds, Input.ini as reference. Find the root through the launcher Manage option. Edit with the game closed and keep backups of hand-tweaked files.
~/.local/share/Steam/steamapps/compatdata/3126180/pfx
Proton prefix for app ID 3126180; inside pfx continue to the install-relative Demo path. Steam Deck uses the same compatdata root. Settings transfer between Windows and Linux by copying the same relative files.
Frequently asked questions
how do I move Tarisland settings to a new PC
Copy GameUserSettings.ini and SettingSave.sav from the WindowsNoEditor folder with the game closed. Paste into the same relative spot on the target install. Keybind edits through converted JSON need the uesave round trip, so back up first.
where is the Tarisland install folder
Open the install folder through the launcher Manage option, then Demo, Saved, Config, WindowsNoEditor. The folder sits wherever you installed the game, often C:\Tarisland. Paste the path into Explorer rather than hunting by hand.
how do I enable hidden graphics options
Edit GameUserSettings.ini for graphics toggles like VSync, since the menu omits some options. Arbitrary keybinds need the SettingSave.sav JSON conversion workflow instead. Keep a backup copy of every file you hand edit.
Notice an outdated path? Let us know.