---
title: Languages
description: Use Venom Cloud in Bahasa Indonesia, Simplified or Traditional Chinese, Cantonese, Japanese or Korean, and how translations are added without making pages heavier.
section: cloud
order: 14
audience: [user, operator]
sources: [services/nodejs-cloud/lib/i18n, services/nodejs-cloud/messages, services/nodejs-cloud/components/ui/language-select.tsx]
features: [cloud.i18n]
---

Venom Cloud speaks seven languages:

| Language | Code |
|---|---|
| English | `en` |
| Bahasa Indonesia | `id` |
| 简体中文 (Mandarin, Simplified) | `zh-Hans` |
| 繁體中文 (Mandarin, Traditional) | `zh-Hant` |
| 廣東話 (Cantonese, written in Traditional characters) | `yue` |
| 日本語 (Japanese) | `ja` |
| 한국어 (Korean) | `ko` |

## Choose a language

Open the account menu at the bottom of the sidebar and pick a language under **Language**, or press ⌘K (Ctrl+K) and
type "language". The page redraws at once.

**Automatic** (the default) follows your browser's language list: the first language there that Venom speaks wins, else
English. Chinese for Hong Kong or Macau (`zh-HK`, `zh-MO`) reads as Cantonese, Chinese for Taiwan as Traditional, other
Chinese as Simplified.

The choice is kept in a cookie (`venom_lang`) on this browser for a year. It is not sent anywhere else and is not
stored on your account, so another device starts on Automatic.

## What is translated

Translated: the console's frame (sidebar, settings menu, top bar, bell, account menu, ⌘K), sign-in and onboarding, Home,
the app rail, the public site's header, footer, home page, pricing and audience pages, and these apps: Notes, Chat,
Support, Incidents and Status, Flags and Experiments, and the Forms builder, Funnel and Calendar. In the admin
console, the page headers and tables are translated, and on Routing, Gears and Providers everything is: the routing canvas,
model choice, the gear editor, connecting a provider, provider status and the failover drill. So are the compute pages
(daemons, public nodes, fleet, autoscaling, GPU sharing) and the safety editors (filters, guardrails, permissions, red
team, MCP servers), the log explorer on Requests, the failure cause cards, and Model quality, Evals, Scorecard and
Shadow. Queries you type in the log explorer keep their English field names and operators.

Still English: Tasks, People, and a few leftovers in Forms, Funnel,
Calendar and the databases in Notes. A string with no translation yet shows in English. Dates
and numbers follow the language's own conventions.

Not translated: your own content (notes, issues, messages), the names of products and models, the public docs, and the
API, CLI and MCP tool descriptions, which stay in English so agents and scripts see stable text.

Chinese, Japanese and Korean text uses your system's fonts for that language. Nothing is downloaded.

## Why it stays light

Each product area's strings are a separate file per language. A page loads only the files it uses, in one language,
on the server. The browser gets those strings with the page and no dictionary in the app's code, so adding a language
does not make any page bigger. If a component needs a file the page did not load, the browser fetches that one file
once (cached for a year) and shows the text as soon as it arrives, never a raw key.

## Loading a namespace on demand

Each page passes the message namespaces it needs. When a shared component asks for one the page did not pass, the browser fetches it from `GET /i18n/{locale}/{ns}`, so a raw message key is never shown. The route serves one namespace in one language as JSON.
