LibreChat/client/src/locales
Marco Beretta 6c0d3a7cbb
Some checks failed
Backend Unit Tests / Build packages (push) Waiting to run
Backend Unit Tests / Codegraph select (push) Waiting to run
Backend Unit Tests / TypeScript type checks (push) Blocked by required conditions
Backend Unit Tests / Circular dependency checks (push) Waiting to run
Backend Unit Tests / Tests: api (shard 1/3) (push) Blocked by required conditions
Backend Unit Tests / Tests: api (shard 2/3) (push) Blocked by required conditions
Backend Unit Tests / Tests: api (shard 3/3) (push) Blocked by required conditions
Backend Unit Tests / Tests: data-provider (push) Blocked by required conditions
Backend Unit Tests / Tests: data-schemas (push) Blocked by required conditions
Backend Unit Tests / Tests: @librechat/api (shard 1/4) (push) Blocked by required conditions
Backend Unit Tests / Tests: @librechat/api (shard 2/4) (push) Blocked by required conditions
Backend Unit Tests / Tests: @librechat/api (shard 3/4) (push) Blocked by required conditions
Backend Unit Tests / Tests: @librechat/api (shard 4/4) (push) Blocked by required conditions
Codegraph E2E Votes / vote (full suite) (push) Waiting to run
Docker Dev Branch Images Build / publish (push) Waiting to run
Frontend Unit Tests / Client build recovery regression (push) Waiting to run
Frontend Unit Tests / Codegraph select (push) Waiting to run
Frontend Unit Tests / Build packages (push) Waiting to run
Frontend Unit Tests / TypeScript type checks (client) (push) Blocked by required conditions
Frontend Unit Tests / Tests: @librechat/chat (push) Blocked by required conditions
Frontend Unit Tests / Tests: @librechat/client (push) Blocked by required conditions
Frontend Unit Tests / Tests: Ubuntu (shard 1/2) (push) Blocked by required conditions
Frontend Unit Tests / Tests: Ubuntu (shard 2/2) (push) Blocked by required conditions
Frontend Unit Tests / Vite build verification (push) Blocked by required conditions
Sync Locize Translations & Create Translation PR / Sync Translation Keys with Locize (push) Has been cancelled
Sync Locize Translations & Create Translation PR / Create Translation PR on Version Published (push) Has been cancelled
↔️ fix: Follow the Interface Direction in Radix, the Composer and First Paint (#17264)
* fix: Follow the Interface Direction in Radix, the Composer and First Paint

Wrap the app in a Radix DirectionProvider driven by i18n so Tabs, Select and
menus stop rendering LTR subtrees in right-to-left locales, and swipe toasts
toward the inline end.

Chat direction becomes auto, ltr or rtl (auto by default; stored LTR/RTL
values are kept). The composer applies a forced direction as a dir attribute
instead of reversing rows, which double-flipped under an RTL document, and the
text fields default to dir=auto. The unused Jotai chat direction atom that
pinned every TextareaAutosize to ltr is removed.

index.html sets dir before first paint, and the language setting no longer
races i18n over document.lang.

* fix: Keep the Empty Composer Placeholder on the Interface's Reading Edge
2026-10-19 23:10:06 +02:00
..
ar 🌍 i18n: Update translation.json with latest translations (#14739) 2026-08-11 01:11:56 -04:00
bo
bs
ca 🌍 i18n: Update translation.json with latest translations (#14919) 2026-08-17 09:21:14 -04:00
cs 🌍 i18n: Update translation.json with latest translations (#14739) 2026-08-11 01:11:56 -04:00
da 🌍 i18n: Update translation.json with latest translations (#14739) 2026-08-11 01:11:56 -04:00
de 🌍 i18n: Update translation.json with latest translations (#14919) 2026-08-17 09:21:14 -04:00
en ↔️ fix: Follow the Interface Direction in Radix, the Composer and First Paint (#17264) 2026-10-19 23:10:06 +02:00
es 🌍 i18n: Update translation.json with latest translations (#14919) 2026-08-17 09:21:14 -04:00
et 🌍 i18n: Update translation.json with latest translations (#14739) 2026-08-11 01:11:56 -04:00
fa 🌍 i18n: Update translation.json with latest translations (#14739) 2026-08-11 01:11:56 -04:00
fi
fr 🌍 i18n: Update translation.json with latest translations (#14739) 2026-08-11 01:11:56 -04:00
he 🌍 i18n: Update translation.json with latest translations (#14919) 2026-08-17 09:21:14 -04:00
hu 🌍 i18n: Update translation.json with latest translations (#14739) 2026-08-11 01:11:56 -04:00
hy
id
is 🌍 i18n: Update translation.json with latest translations (#14739) 2026-08-11 01:11:56 -04:00
it 🌍 i18n: Update translation.json with latest translations (#14919) 2026-08-17 09:21:14 -04:00
ja 🌍 i18n: Update translation.json with latest translations (#14919) 2026-08-17 09:21:14 -04:00
ka
ko 🌍 i18n: Update translation.json with latest translations (#14919) 2026-08-17 09:21:14 -04:00
lt 🌍 i18n: Update translation.json with latest translations (#14919) 2026-08-17 09:21:14 -04:00
lv 🌍 i18n: Update translation.json with latest translations (#14739) 2026-08-11 01:11:56 -04:00
nb 🌍 i18n: Update translation.json with latest translations (#14739) 2026-08-11 01:11:56 -04:00
nl 🌍 i18n: Update translation.json with latest translations (#14919) 2026-08-17 09:21:14 -04:00
nn 🌍 i18n: Update translation.json with latest translations (#14739) 2026-08-11 01:11:56 -04:00
pl 🌍 i18n: Update translation.json with latest translations (#14919) 2026-08-17 09:21:14 -04:00
pt-BR 🌍 i18n: Update translation.json with latest translations (#14919) 2026-08-17 09:21:14 -04:00
pt-PT 🌍 i18n: Update translation.json with latest translations (#14919) 2026-08-17 09:21:14 -04:00
ru 🌍 i18n: Update translation.json with latest translations (#14919) 2026-08-17 09:21:14 -04:00
sk
sl
sv 🌍 i18n: Update translation.json with latest translations (#14919) 2026-08-17 09:21:14 -04:00
th 🌍 i18n: Update translation.json with latest translations (#14739) 2026-08-11 01:11:56 -04:00
tr 🌍 i18n: Update translation.json with latest translations (#14919) 2026-08-17 09:21:14 -04:00
ug
uk 🌍 i18n: Update translation.json with latest translations (#14739) 2026-08-11 01:11:56 -04:00
vi 🌍 i18n: Update translation.json with latest translations (#14739) 2026-08-11 01:11:56 -04:00
zh-Hans 🌍 i18n: Update translation.json with latest translations (#14919) 2026-08-17 09:21:14 -04:00
zh-Hant 🌍 i18n: Update translation.json with latest translations (#14919) 2026-08-17 09:21:14 -04:00
i18n.ts
README.md 🌐 fix: Scrollable Language Dropdown in Shared Chat Settings (#14954) 2026-08-17 22:42:28 -04:00
Translation.spec.ts 🔢 fix: Pair English Plural Keys as _one/_other for Locize (#17223) 2026-10-18 14:11:02 +02:00

LibreChat Localization Guide

This guide explains how to add new languages to LibreChat's localization system.

Adding a New Language

To add a new language to LibreChat, follow these steps:

1. Add the Language to Locize Project

  • Navigate to the LibreChat locize project,
  • Click the "ADD LANGUAGE" button, typically found within the "..." menu of the "Start to translate" card on the project overview page.

2. Update the Language Selector Component

Edit client/src/components/Appearance/Selectors.tsx and add your new language option to the languageOptions array:

{ value: 'language-code', label: localize('com_nav_lang_language_name') },

Example:

{ value: 'bo', label: localize('com_nav_lang_tibetan') },
{ value: 'uk-UA', label: localize('com_nav_lang_ukrainian') },

Note: Use the appropriate language code format:

  • Use simple codes (e.g., bo) for languages without regional variants
  • Use region-specific codes (e.g., uk-UA) when needed

3. Add Localization Keys

In client/src/locales/en/translation.json, add the corresponding localization key for your language label:

"com_nav_lang_language_name": "Native Language Name",

Example:

"com_nav_lang_tibetan": "བོད་སྐད་",
"com_nav_lang_ukrainian": "Українська",

Best Practice: Use the native language name as the value.

4. Create the Translation File

Create a new directory and translation file:

mkdir -p client/src/locales/[language-code]

Create client/src/locales/[language-code]/translation.json with an empty JSON object:

{}

Example:

  • client/src/locales/bo/translation.json
  • client/src/locales/uk/translation.json

5. Configure i18n

Update client/src/locales/i18n.ts:

  1. Import the new translation file:
import translationLanguageCode from './language-code/translation.json';
  1. Add it to the resources object:
export const resources = {
  // ... existing languages
  'language-code': { translation: translationLanguageCode },
} as const;

Example:

import translationBo from './bo/translation.json';
import translationUk from './uk/translation.json';

export const resources = {
  // ... existing languages
  bo: { translation: translationBo },
  uk: { translation: translationUk },
} as const;

6. Handle Fallback Languages (Optional)

If your language should fall back to a specific language when translations are missing, update the fallbackLng configuration in i18n.ts:

fallbackLng: {
  'language-variant': ['fallback-language', 'en'],
  // ... existing fallbacks
},

Translation Process

After adding a new language:

  1. The empty translation file will be populated through LibreChat's automated translation platform
  2. Only the English (en) translation file should be manually updated
  3. Other language translations are managed externally

Language Code Standards

  • Use ISO 639-1 codes for most languages (e.g., en, fr, de)
  • Use ISO 639-1 with region codes when needed (e.g., pt-BR, zh-Hans)
  • Tibetan uses bo (Bodic)
  • Ukrainian uses uk or uk-UA with region

Testing

After adding a new language:

  1. Restart the development server
  2. Navigate to Settings > General
  3. Verify your language appears in the dropdown
  4. Select it to ensure it changes the UI language code

Notes

  • Keep language options alphabetically sorted in the dropdown for better UX
  • Always use native script for language names in the dropdown
  • The system will use English as fallback for any missing translations