Key Structure Preservation
All JSON keys, nesting levels, and structural brackets are preserved exactly. Only string values are translated. The output JSON parses without errors.
JSON localization files for frameworks such as react-i18next, vue-i18n, and next-intl use nested key structures, interpolation variables like {{name}} or {count}, and pluralization keys such as one, other, few, and many.
A translator who edits a JSON file in a text editor and inadvertently changes a key name or removes a closing bracket will break your application build, which is why JSON belongs in a proper software localization workflow rather than a plain text editor.

All JSON keys, nesting levels, and structural brackets are preserved exactly. Only string values are translated. The output JSON parses without errors.
Interpolation variables such as {{name}}, {count}, %s, and {0} are identified and locked before translation, preventing accidental modification.
Target-language plural forms (one, few, many, zero, other) are generated according to Unicode CLDR plural rules for the target language.
The delivered JSON file is validated for syntactic correctness before delivery. No silent errors, missing commas, or encoding issues will reach your build system.
“Highly professional and meticulous work. They truly listened to my needs and communicated very responsively. Very satisfied with the work done.”
“It is a real pleasure to work with the BeTranslated team who has been very professional, flexible and responsive during all projects.”
“Great communication, perfect translations in different languages in a very short notice. I would recommend! We are very pleased, thank you :-)”
Everything you need to know about translating JSON strings files.
We support the JSON formats used by react-i18next, next-intl, vue-i18n, Angular's i18n tooling, LinguiJS, and Phrase. If you use a custom JSON schema, please send a sample file before requesting a quote so we can confirm compatibility.
Yes. Deeply nested JSON structures are supported. Keys at any nesting level are preserved exactly. If your JSON has both translatable string values and numeric or boolean values at the same level, only string values are sent for translation.
English typically has only two plural forms (one and other). Languages such as Polish, Russian, and Arabic use three to six plural forms. We generate all required plural forms for the target language according to Unicode CLDR plural rules and add them to the JSON output under the correct keys.
Send us your JSON strings file and we will quote as quickly as possible and return the translation in your file format.