Translate JSON language files with AI
Import your JSON i18n files, let AI translate them using your glossary and project context, review every string and export ready-to-ship files.
Used by React, Vue, Angular, i18next, Laravel and most modern web frameworks.
What a JSON file actually holds
JSON is the default home for translatable copy on the web. i18next, react-intl, Vue I18n, Angular and Laravel all read it, which is why a JSON file is usually the first thing a developer needs translated — and why it is the format most likely to be handed to a generic translation tool and come back broken.
The structure varies more than people expect. Some projects keep a flat file where the key is the English sentence itself; others nest keys several levels deep by feature. Some store plurals as sibling keys, others as an object. A translator that treats the file as plain text will happily translate your keys along with your values, and nothing will resolve at runtime.
.json
{
"welcome.title": "Welcome back!",
"welcome.subtitle": "Log in to continue",
"buttons.save": "Save changes"
}What goes wrong when JSON files are translated badly
These are the failures that reach production, because none of them look like errors until they do.
Interpolation placeholders get translated
{{count}}, {name} and %s carry data into the sentence. If a model helpfully translates "count" to "conteggio", the value never renders and the string breaks silently in production.
Keys drift from the source file
When translations are edited by hand, a key gets renamed on one side and not the other. The app falls back to showing the raw key — usually in the one language nobody on the team reads.
Plural rules do not survive a copy-paste
English has two plural forms, Polish has four, Japanese has one. Copying the English structure into every language produces grammatically wrong output that no build step will flag.
Nesting gets flattened on the way back
A tool that flattens your file to translate it, then returns it flat, forces you to restructure it by hand — and your framework will not find a single key until you do.
How GetTranslated handles it
Import your JSON file
AI translates with your glossary
Review and approve every string
Export and ship
Want to see it on your own file first?
Paste a JSON file into the free tool and get the translated version back straight away — no account, no email address.
Open the free JSON translatorFrequently asked questions
Which JSON i18n libraries are supported?
Any of them. Flat files, nested objects and dotted keys are all read correctly, so i18next, react-intl, Vue I18n, Angular and Laravel JSON files work without configuration.
Are my placeholders preserved?
Yes. Placeholders are given to the model as part of the string with instructions to leave them untouched, and every suggestion is marked for review so you can confirm before shipping.
Does the exported file keep its structure?
Yes. Nesting and key order are rebuilt exactly as they were imported — the export is a drop-in replacement for the file you started with.
500 keys free forever. No credit card.