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

Translate FormatJS JSON files safely

FormatJS catalogs need careful handling because a small placeholder mistake can break runtime formatting. Keep IDs stable and review ICU-heavy strings first.

Designed for message catalog JSON workflows

Protects the structure around IDs and message values

Pairs well with a CLI validation step before merge

A safer JSON translation flow

1

Start with extracted source messages

Use the source catalog produced by your FormatJS extraction flow.

2

Translate draft message values

Keep message IDs unchanged while translating the human-readable copy.

3

Validate placeholders

Use app tests and @json-translate/check to catch missing or changed placeholder tokens before release.