Which languages can I translate into?

Better i18n ships 215 languages: 183 base languages on ISO 639-1 codes, plus 32 regional and script variants on BCP 47. You pick from that list in Languages → Add language inside your project — nothing has to be requested, enabled or upgraded first.

Looking for one in particular? Search this page for its name (⌘F / Ctrl+F). The tables below are grouped by region and give the native name alongside the code, because the native name is what your translators will recognise.

Two questions people mean by "do you support X?" #

Most confusion here comes from collapsing two separate things. Keep them apart:

A language your provider does not reach is still a fully working language. You or your translators fill it in the editor, or AI translation fills what it can and you review it. Nothing about the platform degrades — only the automatic first draft is unavailable.

If automatic coverage matters to you, check translation providers before you pick one. Google and Azure are the widest.

Your language is not in the list #

The list follows ISO 639-1, and that standard assigns codes to languages, not to every variety or dialect. Bhoti, Ladakhi, Balti, Konkani dialects and similar varieties have no entry of their own.

Two ways forward:

1. Use the closest coded language. Bhoti is a Tibetic language written in Tibetan script, so bo (Tibetan) is where it belongs. Pair it with a glossary and translation guidelines so AI translation and your reviewers keep the wording you want. This is the usual answer.
2. Ask us to add the code. Language codes come from a shared reference list, so you cannot type in an arbitrary one — the project will reject it. If you need a code that genuinely is not there, message us in the widget with the code and language name and we will add it.

Right-to-left languages #

Five are right-to-left: Arabic (ar), Persian (fa), Hebrew (he), Urdu (ur) and Yiddish (yi). Direction is a property of the language itself, so the translation editor renders them RTL and the SDK exposes the direction to your app. You configure nothing.

European languages #

The widest coverage on the list, including every EU official language.

Middle East and North African languages #

Arabic, Hebrew and Persian are right-to-left; direction is set on the language, so you configure nothing.

Sub-Saharan African languages #

Machine-translation coverage is thinnest here — Google and Azure reach most of these, DeepL reaches none of them. They work exactly the same in the editor either way.

South Asian languages #

Several use their own script, and the editor renders each one in it — Devanagari, Bengali, Tamil, Sinhala, Thaana.

East and Southeast Asian languages #

Chinese is here as the base code zh; if you need Simplified and Traditional as separate languages, use the script variants below.

Central Asian and Caucasian languages #

Several use non-Latin scripts. The editor renders each one in its own script, and the native name is what your translators will recognise.

Languages of the Americas #

Indigenous languages of the Americas. For Spanish and Portuguese as spoken here, the regional variants below are usually what you want.

Pacific languages #

Small speaker populations, full platform support. No machine-translation provider covers most of them, so expect to translate these by hand or with AI review.

Regional and script variants #

Add one of these alongside the base language when the copy genuinely differs — pt-BR and pt-PT are two independent languages here, with their own keys, coverage and publish status. Codes come out in BCP 47 casing, so they drop into next-intl, react-i18next, Expo or Flutter without a mapping layer.

Constructed languages #

Available for completeness. These are real entries you can add, not placeholders.

Esperanto eo · Ido io · Interlingua ia · Interlingue ie · Volapük vo

What this does not cover #

Languages here mean translation target languages in your project. Two related things are separate:

• Help centre and CMS content have their own language settings, set per content entry — see translating content entries.
• Document translation — sending a PDF, DOCX or slide deck and getting the same file back translated — is not something Better i18n does. It translates the strings your application ships. More on what counts as a translation file.