Choose your languages

Start with the languages your customers need most. You can add more later without changing your application integration.

1. Open Languages

1. Open Languages for your project.
2. Search by language name, native name, locale code, or country.
3. Enable the language for your project.

Your source language stays enabled automatically.

2. Request development translations

The plugin requests the enabled target locales from project settings. It has no target-locale list option. To translate and publish those languages during an authorized development build, configure:

translation: {
  enabled: true,
  maxChargeMicros: 100_000,
  waitTimeoutMs: 300_000,
  publish: "development",
}

The translation option requires a development project token and environment: "development". The per-build cap is expressed in microdollars; 100_000 is $0.10. Production publication is explicit in Releases.

Product terminology

In Languages, add required target wording for important product terms. Save glossary version creates and activates a new version of those rules for subsequent work. Keep placeholders intact when editing translations; glossary validation still applies.

Verify

Open a translation run and confirm the language is included before reviewing its result.

Failure and next

If a language cannot be enabled, check the project fallback settings and troubleshoot the dashboard.