Where Does Vermintide 2 Store Config and Saves?
Vermintide 2 keeps settings, saves and crash logs in a Fatshark folder in Roaming. Config files, logs, and Linux.
Last updated
Vermintide 2 keeps its local state in one Roaming folder: Fatshark\Vermintide 2 holding user_settings.config for graphics and keybinds, save_data.sav for local progress, launcher logs and a console_logs folder with timestamped crash logs. Darktide uses the identical layout under its own Fatshark folder, so skills transfer.
The read-only flag on user_settings.config is the recurring villain: settings reset every launch until it is cleared, and subscribed mods revert to disabled for the same reason. Character progress needs no backup since Fatshark holds it server-side. Linux mirrors the layout inside the Proton prefix for app ID 552500.
Where Warhammer: Vermintide 2 stores this, by platform
%APPDATA%\Fatshark\Vermintide 2
user_settings.config holds graphics and keybinds; save_data.sav holds local progress; console_logs holds timestamped crash logs. Clear read-only on the config when settings reset or mods disable themselves. Darktide mirrors this layout under Fatshark\Darktide. Steam Cloud syncs the tree.
~/.local/share/Steam/steamapps/compatdata/552500/pfx/drive_c/users/steamuser/AppData/Roaming/Fatshark/Vermintide 2
The Windows layout mirrored inside the Proton prefix, where 552500 is the game's Steam app ID. Some installs use ~/.steam/steam instead of ~/.local/share/Steam. Same user_settings.config and save_data.sav filenames, so configs move across freely.
Frequently asked questions
how do i move vermintide 2 settings to a new pc
Copy the whole Fatshark\Vermintide 2 folder to the new machine with the game closed. user_settings.config carries graphics and keybinds, save_data.sav carries local progress. Character levels and loot are on Fatshark's backend and follow your account. Reinstall mods from the Workshop afterward.
why do vermintide 2 settings reset on launch
Clear the read-only flag on user_settings.config. Fatshark's own support gives this exact fix: the file locks after some updates or cloud conflicts, and the game silently discards changes while set. Right-click, Properties, uncheck Read-only. Also set graphics quality to Custom once so the menu writes values at all.
where are vermintide 2 crash logs
Open the console_logs subfolder and grab the timestamped log matching your crash. Fatshark support asks for exactly this file plus user_settings.config and the launcher log beside it. The logs name the failing subsystem, which beats guessing between mods, drivers and DirectX.
Notice an outdated path? Let us know.