Where Does Widelands Store Savegames?
Where Widelands keeps savegames, replays, maps, and config on Windows, macOS, and Linux.
Last updated
Widelands keeps saves, maps, and replays in one user folder per OS, with config beside it. Linux follows XDG on standard builds; Windows and macOS use their Documents and Library roots.
Version matching matters more here than in most open-source games. Point releases can desync multiplayer and invalidate old saves. Note the build number alongside any backup so restores land on equal versions.
Where Widelands stores this, by platform
%USERPROFILE%\Documents\Widelands\save
Saves in save/ plus maps, replays, and config nearby. Keep versions matched across machines; 1.3 and 1.3.1 cannot mix in net games.
~/Library/Application Support/Widelands/save
Same save/maps/replays layout. Exact path may vary by package (AppImage versus Flatpak); check the app settings if empty.
~/.local/share/widelands/save
XDG build default (USE_XDG=ON). Non-XDG builds use ~/.widelands/save instead. Check both if the folder looks empty after switching packages.
Frequently asked questions
How do I migrate Widelands saves?
Copy the whole user folder (save/, maps, replays, config) to the matching path on the new machine. Keep versions matched; 1.3 saves do not mix with 1.3.1 in multiplayer and old saves can misbehave. Test one campaign file first.
Why are there two candidate Linux paths?
Linux builds follow XDG when compiled with USE_XDG (the default): saves under the data dir, config under the config dir. Windows uses Documents\Widelands, macOS its Library path. Check build flags only if both candidate paths look empty.
Notice an outdated path? Let us know.