Where Are Fields of Mistria Save Files Located?
Fields of Mistria keeps every save slot as its own folder under %LOCALAPPDATA%\FieldsOfMistria, with settings.json sitting beside them.
Last updated
Mistria is a Unity game, and it follows the tidy version of the Unity convention: %LOCALAPPDATA%\FieldsOfMistria holds a saves folder and a settings.json, and that is the whole footprint. Each save slot is a folder inside saves, not a single file, so one farm can be several megabytes of data.
Updates arrive regularly, and a copy of the folder before a big patch costs seconds. Steam Cloud syncs everything on its own, but the container is capped at about 953 MB, and test farms people never revisit fill that space faster than most players expect.
Where Fields of Mistria stores this, by platform
%LOCALAPPDATA%\FieldsOfMistria
The saves folder holds one subfolder per slot; settings.json covers audio, display, and controls, and doubles as the easiest thing to delete when the game launches with bad settings. Steam Cloud syncs this whole directory.
~/.local/share/Steam/steamapps/compatdata/2142790/pfx/drive_c/users/steamuser/AppData/Local/FieldsOfMistria
The Windows build through Proton on Linux and Steam Deck, inside the prefix for app ID 2142790. Same layout as Windows, and cloud sync keeps the two copies in step if you play on both.
Frequently asked questions
How do I move a Fields of Mistria save to another PC?
Copy the whole FieldsOfMistria folder, or let Steam Cloud handle it. Keep the game closed while copying, and make sure the new machine finishes syncing before you launch, or you may start from an older date.
Which folder is my current save slot?
Each slot is a folder inside saves, named with an internal ID rather than your farmer's name. Sort by modified date to spot the active one. Renaming the folders does not rename the farm and can confuse the load screen.
Steam Cloud says the storage is full. What is taking the space?
The game's cloud container is about 953 MB, shared across every slot. Save folders grow with map coverage and item history, so retired test farms are the usual culprit. Delete the ones you will not revisit.
Notice an outdated path? Let us know.