Web Widget languages — 50 out of the box.

Overview — what "supported" means

A language ships in the Web Widget when every user-visible string in the chat UI has a translation reviewed by a native speaker. That includes the composer placeholder, the send button tooltip, connection-state banners, quick-reply chips, and every error toast. If a string can't be translated with a straight equivalent (idioms, culture-specific phrasing), the review pass writes a locale-appropriate rewrite rather than falling back to English.

The list on this page is the actual runtime table — the widget loader ships these codes and pulls the matching pack on first paint.

Coverage at a glance

How the visitor's language is detected

Detection runs once, at widget mount, and picks the first hit in this order:

1. Explicit override. If your page sets window.Knocket.locale = 'ja' before the widget loads, that wins. See Override in Code.
2. HTML lang attribute. If <html lang="fr"> is present, the widget adopts it. This is the cleanest option for multilingual sites — set it server-side per page.
3. Browser locale. Falls back to navigator.languages[0]. Region variants collapse to the base language (e.g. pt-BR → pt).
4. English. If none of the above matches a shipped pack, the widget stays in English rather than a partially translated state.

The full list — 50 languages

Ranked by global speaker count. Every row is a shipping language pack; the code column is the exact string the widget expects.

Override in code

If you already know the visitor's preferred language (from your app state, an account setting, or a URL param), tell the widget explicitly:

<script>
  window.Knocket = window.Knocket || {};
  window.Knocket.locale = 'ja'; // must be set before the loader script
</script>
<script src="https://cdn.knocket.ai/w.js" async></script>

Or after the widget has mounted, change it live:

Knocket('setLocale', 'zh-Hans');

The widget re-renders every string, flips direction for RTL languages, and keeps the current conversation intact.

Fallback behavior

Two edge cases worth calling out:

• Unshipped locale. If you pass an unknown code (e.g. xx or an obscure regional variant), the widget falls back to English silently and reports the miss in the console analytics.
• Regional fallback. Regional codes collapse to their base language when a regional pack isn't shipped. pt-BR → pt, en-GB → en. Simplified/Traditional Chinese are separate packs (zh-Hans vs zh-Hant) — do not alias them.