Developer JSON translation
Translate i18next JSON without breaking keys
Paste or upload an i18next locale file, choose target languages, and keep the parts your app depends on intact.
Preserves nested key paths such as checkout.summary.total
Keeps interpolation tokens and product terms under control
Outputs valid JSON that can go straight back into your locale folder
A safer JSON translation flow
1
Start with source JSON
Use your canonical source locale, usually en.json, as the structure to preserve.
2
Protect risky terms
Add brand names, product names, variables, and technical terms before translating.
3
Review the output
Download translated JSON and review the highest-risk screens in your app before shipping.