Where Does GameVault Store Games and Config?
GameVault keeps installed games, metadata and server config in mapped volumes. The Linux and Windows roots and what to persist.
Last updated
GameVault splits data between a games library and a metadata tree with server config nearby. Clients cache their own view while the server holds the source of truth.
Paths depend on install choices and volume binds, so two setups rarely match literally. The server settings screen and compose file name the real roots. Back up library plus database together or restores mismatch.
Where GameVault stores this, by platform
/gamevault/games/
Server library plus metadata and config; database alongside per setup. Persist all three. Exact names may vary by GameVault version, so confirm against server settings or the compose file.
%APPDATA%\GameVault
Desktop client cache and downloaded installs under the user profile, with the exact game folder settable in client settings. Server side remains the source of truth for the collection.
Frequently asked questions
Which GameVault folders must persist?
Persist the games library, metadata and database volumes (see the compose file or install settings). Without them, installs and artwork vanish on update. Back up the database plus the library as one set.
How do I migrate GameVault?
Copy the library, metadata and database to the new host with a matching GameVault version. Reindex after the move. Exact internal names may vary by release, so keep installer settings beside the backup.
Notice an outdated path? Let us know.