Skip to Content

Language

The QuickBox Pro dashboard can be displayed in seven languages, and each user chooses their own. Your language is your setting: on a shared server, one user can run the dashboard in German while another runs it in Chinese, and neither choice affects the other. You can set it just for the current login session or save it to your account so it follows you across browsers.

The six non-English translations are drafts

English is the source language that every label is authored in. The other six languages (Deutsch, Dansk, Español, Français, Português, and 简体中文) are machine-drafted and have not yet had a full native-speaker review, so you may still find rough wording or an untranslated string here and there. Corrections are welcome. If you spot something that reads wrong, let us know in the community and it will be fixed.


What you get

Seven languages

English, Deutsch, Dansk, Español, Français, Português, and 简体中文, each shown in its own name

Per-user choice

Your language is yours alone - it never changes what other users on the same server see

Session or account

Apply a language to just this login, or save it to your account so it follows you across browsers

Sensible fallbacks

The dashboard falls back to your browser language, then an admin default, then English

Admin fallback

Admins can set the dashboard-wide default language for users who have not chosen one

Separate from the CLI

Your dashboard language is independent of the server's command-line language


The languages

The dashboard ships these seven languages. Each is shown to you in its own name (its autonym), and every language reads left to right.

LanguageCode
English
en
Deutsch (German)
de
Dansk (Danish)
da
Español (Spanish)
es
Français (French)
fr
Português (Brasil)
pt-BR
简体中文 (Simplified Chinese)
zh-CN

Where to change your language

There are three places to change your dashboard language.

From the top bar

When you are signed in, a globe icon in the top bar opens a compact language menu. It lists all seven languages (each in its own name, with a flag), marks the one currently active with a check, and includes a reset row labelled Use account preference that drops any session-only override and returns you to your saved account language.

On the login page

Before you sign in, the same globe language menu is available on the login page as an icon-only button. Here the reset row is labelled Automatic, which lets the dashboard pick a language from your browser rather than any saved preference. A language chosen while signed out applies only to the current browser tab and is never saved.

In your profile

Your Profile page has a Language card, described as “Choose how this dashboard is displayed for you.” This is where the full controls live. Reach your profile from the user menu in the top bar.

In the Language card, a two-button toggle lets you choose the scope of your change:

ScopeWhat it does
This session
Applies to tabs using this login until you sign out. A quick, temporary switch.
My account on this dashboard
Used on this dashboard across browsers. Saving also clears this session's override.

The action button changes to match your choice:

  • With My account on this dashboard selected, the button reads Save language. Picking the inherit option instead turns it into Use Automatic, which reverts you to browser detection and the dashboard default.
  • With This session selected, the button reads Apply language. Picking the inherit option turns it into Reset session language, which drops the session override so your saved account preference takes over again.
Session vs account, in one line

Use This session for a quick, throwaway switch on the machine in front of you. Use My account on this dashboard when you want the dashboard to open in that language everywhere you sign in.


How your language is chosen

When you load the dashboard, it resolves your language in this order and uses the first one that applies:

OrderSource
1
Current session override - a language you applied to this login
2
Saved account preference - the language saved to your account
3
A matching browser language - detected from your browser's language settings
4
Dashboard fallback language - the admin-set default for this server
5
English - the final fallback if nothing else resolves

Because the first two steps are keyed to your own account, your language is fully isolated from every other user. Two people signed in to the same server hold independent languages at the same time. Browser detection never saves anything: it only picks a display language for the current visit, so a guest or a browser-matched choice leaves no stored preference behind.

How browser languages map

Browser detection maps close variants to a supported language: for example German variants map to Deutsch, British English maps to English, and most Chinese variants map to 简体中文. A variant with no close match (such as Traditional Chinese or European Portuguese) simply falls through to the next step in the order above.


Admin: dashboard fallback language

Administrators can set a dashboard-wide default language for users who have not chosen one of their own. This lives in Settings > General Settings > Timezone & Locale on the General Settings page, which is admin-only.

The field is labelled Dashboard fallback language, described as “Applies only when no personal or supported browser language resolves. Does not change the CLI language.” Its empty option reads No dashboard default (English fallback), and the seven languages above are the choices.

The fallback is only step 4

The dashboard fallback applies only when a user has no session override, no saved preference, and no matching browser language. It never overrides a choice a user has made for themselves, and it does not change the server’s command-line language (see below).


What follows your language, and what stays literal

Once your language is set, the dashboard formats numbers, dates, percentages, and relative times (“2 minutes ago”) for that language automatically.

Some content is deliberately never translated, because translating it would change its meaning or hide what the server actually reported. This stays in its original form in every language:

  • Raw command-line, terminal, and console output
  • Audit-log entries
  • Anything you or another user typed (names, notes, custom template text)
  • Third-party media metadata (titles, descriptions from other apps)
  • Device paths, IP addresses, and identifiers
  • Status codes, command names, and API payloads

The CLI language is separate

Your dashboard language and the server’s command-line (CLI) language are two independent settings. Changing your dashboard language never touches the CLI, and setting the CLI language never changes anyone’s dashboard.

The CLI language is a server-wide, admin-only setting. It controls the language of qb command output and regenerates the server’s operating-system locale. Set it with:

qb manage lang -o <code>

The CLI accepts the codes en, de, dk, es, fr, pt, and zh-cn (full names such as english or french also work). Note that the CLI uses dk, pt, and zh-cn, while the dashboard uses da, pt-BR, and zh-CN for the same languages. Full detail is on the CLI manage reference.

One is not the other

qb manage lang changes the whole server’s CLI and OS locale for everyone. It does not set, override, or read any user’s dashboard language. Likewise, the admin Dashboard fallback language field does not change the CLI. Pick the setting that matches what you want to change.


Translation status

English is the source-authored catalog: every label starts in English. The other six languages are broadly covered but are currently machine-drafted and have not had a full native-speaker linguistic review, so a user may still find occasional rough wording or a string that was missed.

Full native-speaker review, complete screen-reader and high-zoom acceptance, and per-language sign-off are ongoing rather than finished. If you find wording that reads wrong or a string that was missed, corrections are genuinely welcome.


Best practices

Do

  • Save your language to My account on this dashboard if you want it to follow you across browsers and devices
  • Use This session for a quick, temporary switch on a machine you do not own
  • Report any wrong or missing translation - the six non-English languages are drafts and welcome corrections
  • Admins: set a Dashboard fallback language if most of your users share a language other than English

Don't

  • Do not expect qb manage lang to change your dashboard language - the CLI language is a separate, server-wide setting
  • Do not assume audit logs, terminal output, or media titles will translate - those stay in their original form on purpose
  • Do not rely on a signed-out language choice to persist - it applies to the current tab only and is never saved

FAQ

No. Your dashboard language is tied to your own account and session. Two users signed in to the same server can run the dashboard in two different languages at the same time, with no effect on each other.
'This session' applies the language only to tabs using your current login, until you sign out - a quick, temporary switch. 'My account on this dashboard' saves the language to your account, so it is used across browsers. Saving to your account also clears any session-only override.
It uses the first of these that applies: a language you applied to this session, then your saved account preference, then a matching browser language, then the admin-set dashboard fallback, and finally English.
A language chosen on the login page applies only to that browser tab and is never saved. To make a language persist, sign in and save it to your account from the Language card in your profile.
No. They are independent. Your dashboard language never touches the CLI, and 'qb manage lang' sets a server-wide CLI and OS locale that does not change anyone's dashboard language.
The six non-English languages are machine-drafts pending native-speaker review, so an occasional string may still read in English. Separately, terminal output, audit logs, media metadata, paths, and identifiers are intentionally never translated. Corrections to draft translations are welcome.


Need help?

Join the Community

Media server operators sharing configs, getting support, and shaping the future of QuickBox Pro.

Dedicated Support
Feature Previews
Community Configs
Active Discussions
Join Discord Server
Last updated on