Translate JSON Files in Seconds
Keys intact. Nesting preserved. Interpolation variables untouched. Just translated content where your strings used to be.
Manual JSON Translation Is a Minefield
You know the drill. Export your JSON locale file, open it in a spreadsheet or translation tool, carefully avoid breaking nested keys, hope nobody touches the variables, re-import, fix the broken structure, repeat for every language.
Nested keys get flattened or mangled by generic translation tools
Interpolation variables get translated or corrupted by generic tools
ICU plural rules break silently when tools don't understand MessageFormat syntax
Array indices shift, key ordering changes, formatting disappears
{
"welcome": "Welcome, {name}!",
"items": {
"count": "{count, plural, one {# item} other {# items}}",
"empty": "Your cart is empty"
},
"nav": {
"home": "Home",
"settings": "Settings"
}
}{
"welcome": "Willkommen, {name}!",
"items": {
"count": "{count, plural, one {# Artikel} other {# Artikel}}",
"empty": "Ihr Warenkorb ist leer"
},
"nav": {
"home": "Startseite",
"settings": "Einstellungen"
}
}What i18n Agent Preserves
Key Structure
Nested keys, dot notation, and array indices stay exactly where they are
Interpolation Variables
Variables like name, count, and price placeholders are recognized and left untouched across all major i18n frameworks
ICU Plural Rules
Plural categories are translated correctly while the ICU MessageFormat structure stays intact
Formatting & Whitespace
Indentation, key ordering, and JSON formatting match your source file
Works With Your i18n Framework
How It Works
No manual copy-paste. No string extraction. Just translated files.
Try i18n Agent Now
Drop your translation file here
JSON, YAML, PO, XML, CSV, Markdown, Properties
or click to browse
Target languages
Frequently Asked Questions
Enterprise team?
Still stuck on a TMS contract? Let's talk about migrating.