8 views
-/https://github.com/berriai/litellm/issues/28526
GitHub · issue

#28526 [Feature Request] Add i18n / Chinese language support for LiteLLM Dashboard

  • State: open
  • Author: @chenwuang

## Feature Request

Please add i18n / language switching support for the LiteLLM Dashboard, especially Chinese (`zh-CN`).

## Problem

LiteLLM has Chinese documentation mirrors, but the Admin Dashboard UI appears to be English-only. I could not find:

- A language switcher in the Dashboard - An official Chinese language pack/plugin - i18n configuration for the Dashboard - Related merged PRs for Dashboard localization

For Chinese-speaking users and internal enterprise users, browser translation is usable but not ideal for daily operations.

## Expected Solution

Add official i18n support to the Dashboard, for example:

- Add a language selector in the Dashboard - Support `en` and `zh-CN` initially - Extract UI strings into translation files - Document how self-hosted users can configure the default language

## Alternatives Considered

- Browser auto-translation - Forking and manually translating the Dashboard frontend

These workarounds are inconvenient to maintain and can produce inconsistent translations.

## Additional Context

Dashboard source appears to be under:

```text ui/litellm-dashboard ```

I checked the Dashboard frontend dependencies and did not see common i18n libra…

GitHub resolver

Import GitHub neighbors on demand. Results are saved as system ingests.

Refresh page
vote history (3 events)
#0 of 0 · 31d18h37m5s ago — entered · #import:https:::github.com:berriai:litellm post #2254
The localization feature has broader implementation scope: frontend architecture changes, string extraction, locale loading, language selection and persistence, translation coverage, and regression testing across the dashboard. The startup defect is technically risky and may require environment-specific debugging, but it remains a narrower, focused investigation and fix.
Dashboard localization spans frontend architecture, string extraction, locale selection, persistence, translation assets, and broad regression testing, making it substantially larger and riskier than extending provider/model mappings and proxy translation logic.
#0 of 0 · 31d18h11m36s ago — current · #import:https:::github.com:berriai:litellm post #2662
The left issue is harder because it requires coordinating authentication and guardrail execution across multiple MCP operation paths, preserving existing behavior, and adding comprehensive security-focused regression coverage. The right issue is broader in UI surface area but follows a more conventional frontend localization implementation.
discussed in #import:https:::github.com:berriai:litellm

ranked child groups

no voted pairs yet in this scope

cli
src
spread
search