# Multilingual Apps
Configure your app's display language so the AI, the chat UI, and emails all speak your audience's language.
---
Chipp 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 (left-to-right or right-to-left).
## Supported Languages
| 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 |
20 languages are wired through the app. English is the source/fallback dictionary; the other 19 ship with translations for the most common consumer-facing strings, and any missing key gracefully falls back to English. Arabic is the only right-to-left language in the supported set today; if you need Hebrew, Farsi, Urdu, or another language, email us at support@chipp.ai.
## What Display Language Affects
Setting the Display Language updates four things at once:
- **The AI's replies.** Chipp injects a `Respond in .` directive 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. Whitelabel customizations still take priority where set.
- **Document direction and locale tags.** The page's `` and `` are set so screen readers, on-screen keyboards, and the chat input all behave correctly. RTL languages flip layout automatically.
## Setting the Default Language (Builder)
**1.**
Open Settings
Open your app and click **Settings** in the top navigation.
**2.**
Pick the Display Language
Scroll to the **Language** card and pick a language from the dropdown.
**3.**
(Optional) Override Text Direction
The text direction defaults to LTR for most languages and RTL for Arabic. If your content needs the opposite (a left-to-right magazine in Arabic, or a right-to-left poetic layout in English), toggle the override.
**4.**
Done -- Saves Live
Language changes are live-on-save. You don't need to publish a new version of the app -- the next consumer message already uses the new language.
## Tips for Multilingual Apps
| Tip | Why It Helps |
|-----|--------------|
| Author the system prompt in English | The AI translates output into the consumer's chosen language. English prompts are easier to maintain, and large models work best with them. |
| Localize the welcome message and conversation starters | Starters are static text -- they don't auto-translate. Write them in the target language so first impressions match. |
| Mix-language knowledge sources are fine | Knowledge sources can be in any language. The AI reads them as-is and translates retrieval results into the consumer's language. |
| Consider Arabic typography | Arabic apps benefit from a font that supports Arabic glyphs and proper kerning. Set a custom font in **Style Studio** if needed. |
| Voice mode | The voice agent does not yet respect the Display Language toggle -- if you want voice replies in a specific language, ask for it explicitly in your system prompt. See [Voice Cloning](/docs/guides/voice-cloning) for caveats around accent and TTS providers. |
## Limitations
- The Chipp **builder dashboard itself is English-only**. The consumer chat experience is translated; the dashboard you log into to configure the app is not.
- Conversation starters, custom CTAs, welcome messages, and any text you author manually are **not auto-translated**. Write them in the target language.
- Some hosted-integration error messages (Google, Microsoft, etc.) come from the third-party provider and are not translated by Chipp.
## Related
- [Setup card](/docs/guides/maximize-chipp-capabilities) — author conversation starters, system prompt, and welcome message
- [Embed Widget](/docs/guides/embed-widget) — the embedded widget inherits your app's Display Language
- [Voice Cloning](/docs/guides/voice-cloning) — language and accent in voice mode