AVCodex apps are multilingual by default. As a builder, you pick the Display Language for your app, and the choice flows through everything your consumers see: the AI's responses, the chat UI chrome, transactional emails, and the document direction.
| Code | Language | Code | Language |
|---|---|---|---|
EN |
English | RU |
Russian |
ES |
Spanish | JA |
Japanese |
PT |
Portuguese | KO |
Korean |
FR |
French | ZH |
Chinese |
DE |
German | AR |
Arabic *(RTL)* |
IT |
Italian | HI |
Hindi |
NL |
Dutch | TR |
Turkish |
PL |
Polish | VI |
Vietnamese |
TH |
Thai | ID |
Indonesian |
MS |
Malay | FIL |
Filipino |
Twenty languages are wired through the app. English is the source and fallback dictionary. The other nineteen ship with translations for the most common consumer-facing strings, and any missing key falls back to English gracefully. Arabic is currently the only right-to-left language in the supported set.
Setting the Display Language updates four things at once:
- The AI's replies. A respond-in-language directive is injected into the system prompt, so the AI answers in the chosen language even when your prompt is authored in English.
- The consumer chat UI. The auth flow, history sheet, in-chat menu, file storage sheet, install prompts, package modal, and credit-purchase flow are all translated.
- Transactional emails. OTP codes, password resets, and welcome emails go out in the chosen language. White-label customizations still take priority where set.
- Document direction and locale tags. The page's
<html lang>and<html dir>are set so screen readers, on-screen keyboards, and the chat input all behave correctly. RTL languages flip layout automatically.
- Open your app and click Settings in the top navigation.
- Scroll to the Language card and pick a language from the dropdown.
- Optionally override text direction. Direction defaults to LTR for most languages and RTL for Arabic.
- Changes save live.
Two common cases:
- Canadian public sector and Quebec deployments. French display language is often a procurement requirement, not a nice-to-have. Setting it at the app level covers the UI and the emails, not just the AI replies.
- Multi-site enterprise rollouts. If you're deploying a room-support agent across a client's global estate, consider one app per language region rather than one app trying to serve everyone. The display language is per-app.
Note that Display Language governs the interface and the AI's default response language. Your knowledge sources stay in whatever language you uploaded them in, and retrieval still works across languages, though quality is best when the knowledge base and the display language match.
*AVCodex · Your AV expertise. Amplified by AI.*