-
-
Notifications
You must be signed in to change notification settings - Fork 0
Usage Files and Locations
Alex edited this page Oct 2, 2026
·
2 revisions
Part of the Usage reference. · ← Previous: Session daemon · Next: Exit codes & logging →
Aurelia stores its data under the user config directory (override it with
AURELIA_CONFIG_DIR):
-
Linux:
~/.config/Aurelia -
Windows:
%USERPROFILE%\.config\Aurelia
| Path | Contents |
|---|---|
session.json |
Persisted login session (refresh token). Encrypted with a key held in the OS keyring when one is available, otherwise plaintext with owner-only permissions. See Session storage. |
images/ |
Cached cover/header artwork (<APP_ID>_library.jpg). |
info_cache/ |
Cached info metadata (<APP_ID>.<LANGUAGE>.<COUNTRY>.json), TTL via AURELIA_INFO_CACHE_TTL (default 6h). |
tag_names.<LANGUAGE>.json |
Cached store tag names for a language, used to label info tags. |
logs/ |
Per-launch event logs. |
The OS keyring entry is stored under service aurelia, account session-key. Deleting it
makes an encrypted session.json unreadable. Run aurelia login again to create a new
one.
Game installs live in your Steam libraries (steamapps/common/...), which Aurelia
discovers automatically across all connected drives.
The Windows Steam runtime keeps every repair backup of its
master prefix as a timestamped .bak-<unix-time> sibling. Nothing deletes them except
steam-runtime uninstall.
Users
-
Usage
- Global behavior
- Authentication
- Library
- Store & discovery
- Collections
- Install & maintenance
- Launching
- Depots & branches
- Downgrade & pinning
- Steam Cloud
- Steam Workshop
- Friends & chat
- Inventory & market
- Configuration
- Proton & Wine
- Windows Steam runtime
- Luxtorpeda plugin
- umu-launcher plugin
- Launch scripts
- Session daemon
- Files & locations
- Exit codes & logging
- Windows Steam Runtime
Maintainers
Architecture