Where Does UMU Store Runtimes and Prefixes?
UMU keeps downloaded runtimes in local share umu on Linux, with prefixes defaulting under Games umu. No config file exists by default.
Last updated
UMU is environment-driven with no config file to learn. Runtimes download into local share while prefixes default under a Games tree per game ID. Launchers override both freely, so effective paths come from the caller.
Proton resolution spans compatibilitytools roots across Steam flavors. Internal runtime layouts stay unverified and unquoted. Optional TOML files ride per invocation at chosen spots rather than fixed homes.
Where UMU stores this, by platform
~/.local/share/umu
Auto-downloaded runtime tree with versioned subfolders of unverified inner layout. Proton builds resolve through compatibilitytools roots beside it. Launchers override freely.
~/Games/umu
Default prefix home per game ID without launcher overrides. Proton logs opt in separately. Check caller variables when actual prefixes differ.
Frequently asked questions
Where are my UMU runtimes?
They live in the local share umu tree with versioned runtime subfolders. Proton builds resolve separately through compatibilitytools.d across Steam roots. Internal substructure stays unverified, so quote the roots rather than inner files.
Where is my UMU wine prefix?
It defaults under Games umu per game ID, or a default name without one. Launchers calling UMU override it freely, so check the caller when prefixes surprise you. Proton logs opt in separately to home.
How do I configure UMU?
Through environment variables with an optional per-run TOML at a chosen path. No daemon file exists to edit. Prefix, proton, exe and store keys all arrive per invocation.
Notice an outdated path? Let us know.