Do I need a full TMS to localize JSON?

Not always. Smaller teams can start with source JSON files, focused translation, human review, and CI validation.

What should be checked manually?

Review strings with brand terms, placeholders, legal meaning, checkout impact, support commitments, and product-specific context.

Developer JSON translation

A practical JSON localization workflow

Small teams often need localization without a full translation management system. JSON Translate gives you a focused workflow around the files your app already uses.

Start JSON localization Compare limits

Works with existing locale files and repositories

Supports review of placeholders and protected terms

Keeps validation close to your release process

A safer JSON translation flow

Translate from the canonical locale

Choose the source locale that product and engineering trust, then generate target JSON files from it.

Review in small batches

Translate by feature, namespace, or release area so reviewers can check context efficiently.

Automate the guardrails

Use @json-translate/check in CI so missing keys and placeholder changes fail before deployment.