We use optional, privacy-limited Google Analytics to understand which product features help. Translation text is never sent to analytics.

Privacy details
Developer JSON translation

Validate JSON translations in CI

Translation problems are cheaper to fix before merge. Pair JSON Translate output with a CI validation step for safer localization releases.

Catch missing and extra locale keys before deployment

Detect placeholder drift in translated strings

Use the free @json-translate/check npm package

A safer JSON translation flow

1

Translate your target locale

Generate translated JSON files from the source locale in JSON Translate.

2

Add the CLI to CI

Run npx @json-translate/check against source and target locale files in pull requests.

3

Block broken translations

Fail the build when a translated file has parse errors, missing keys, extra keys, or changed placeholders.