Translations

SaveVault’s desktop app is translated at runtime, and you can edit or add a language without rebuilding anything.

Shipped languages

English, Español, Deutsch, Français, Português (Brasil), 简体中文, and 繁體中文. Pick one under Settings → Appearance → Language, or leave it on System to follow your OS. System matches your OS locale to a shipped language (de-DE → Deutsch, any pt-* → Português (Brasil), Traditional-script Chinese such as zh-TW or zh-HK → 繁體中文, zh-CN or zh-Hans → 简体中文) and falls back to English when nothing matches.

savevault-cli config set locale pt-BR
savevault-cli config set locale system

config set locale accepts system, a shipped tag, or any tag of up to 16 letters, digits, hyphens, or underscores, so it also works for a language you created yourself in the editor.

The CLI’s own output is English-only; the native dialogs and OS notifications the CLI and launch wrapper show follow your language setting.

The Translations editor

The Translations page is hidden by default. Turn on Show Translations in Sidebar (show_translations_nav, off by default) to open it. It lists every UI string with the official value beside your override, so you can:

• Fix a string in a shipped language. Your edits are stored as a sparse override and always win over the shipped catalog; Reset To Official on a key, or Reset All To Official for the whole locale, returns to the official text.
• Create a new locale with any BCP-47 tag (ja, pl, uk, …), a display name, and a native name, then translate as many keys as you like. Untranslated keys fall back to English. Filter to Untranslated Only to see what’s left; the completion percentage updates as you go.
• Import and export a locale as JSON (Import… / Export…) to share it or move it between machines. If the file’s language tag already exists, you choose Merge into existing or Import as variant. Merging layers the imported strings over your saved file for that tag: keys the file doesn’t mention keep their current value, and the tag stays the same. A variant is saved as a separate language with -import added to the tag (for example de-import).
• Set Active to switch the app to the language you’re editing.

The language list marks each entry Official, Official + edited (a shipped language with your overrides on top), or Community (one you created or imported). Only Community languages can be deleted, with Delete. The completion figure counts keys whose text differs from the English source, whether it comes from the official catalog or your overrides.

Changes apply live, no restart needed.

Sharing on Steam Workshop

In the Steam edition, themes and translations can be published to and subscribed from the Steam Workshop. On the Translations page, Publish To Workshop (Update On Workshop afterward) appears once the language has local edits, and Refresh and Browse Workshop sit by the language list; Workshop languages also show up in Settings → Appearance → Language, labeled “(Workshop)”. Subscribed translations load by reference from Steam’s Workshop folder and are validated before use: keys must exist in the official catalog, placeholders must match, and any HTML beyond simple emphasis is stripped. Your own local edits always take precedence over a subscribed item, and unsubscribing cleanly removes it. Community translations can carry any BCP-47 tag, so a language SaveVault doesn’t ship can still be a one-click subscribe.

Steam holds Workshop downloads while it considers SaveVault “running”; see known issues if a subscription seems stuck.