Skip to content

Configuration

SaveVault stores its config in the standard per-platform directory:

Platform Path
Windows %APPDATA%\SaveVault\config.toml
Linux ~/.config/SaveVault/config.toml
macOS ~/Library/Application Support/SaveVault/config.toml

Other files in the same folder:

File Purpose
custom_games.toml User-defined games
path-redirects.toml Persistent path redirects
themes/*.toml User-defined UI themes
manifest.yaml Cached PCGamingWiki / Ludusavi database
Setting What it does
theme / custom_theme_id UI appearance (system, dark, light, or a theme id)
backup_dir Where archives are stored
default_format zip, targz, or tarzst
additional_roots Non-Steam install roots
scan.parallelism Install-scan threads (null = all logical CPUs)
backup.parallelism Per-game compression threads (null = half logical CPUs)
retention.default_max_backups Per-game backup limit (default 4)
schedule.enabled / schedule.interval_hours Scheduled backups
live.enabled / live.rolling_snapshot_limit Live Protection

Everything here is editable from the GUI as well as the file.

Settings → General → Settings Backup (or savevault-cli settings export / import) copies portable preferences to a TOML file: schedule, live options, notifications, manual install roots, cloud-sync preferences, and built-in theme selection — optionally plus custom games and redirects.

It does not export machine-local state: backup_dir, scheduled/snapshot output folders, live on/off, cloud on/off, cloud sign-in, or rclone paths. Importing with schedule.enabled = true re-registers the OS scheduler on the new machine.

Terminal window
savevault-cli settings export --include-custom-games --include-redirects -o savevault-settings.toml
savevault-cli settings preview savevault-settings.toml
savevault-cli settings import savevault-settings.toml --dry-run

See the CLI reference for every flag.