Localee: AI translation for app localization files.
Localee translates your localization files with AI while keeping every key, placeholder, comment, and nesting level exactly where it was. Drop in JSON, YAML, XML, XLIFF, ARB, or Excel and get back files that still compile — in 50+ target locales.
Localee / en.json → de.json
en.json
{
"welcome": "Hi {name}, welcome back",
"cart_items": "{count} items in your cart",
"cta_upgrade": "Upgrade to Pro"
}
de.json · translated
{
"welcome": "Hallo {name}, willkommen zurück",
"cart_items": "{count} Artikel in deinem Warenkorb",
"cta_upgrade": "Auf Pro upgraden"
}
Why Localee
Structure stays intact
Keys, nesting, comments, and file format survive every translation. The output drops straight back into your repo — no manual repair pass.
Placeholders protected
ICU messages, {variables}, %@, and %s tokens are detected and carried over untouched, so runtime interpolation keeps working in every locale.
Every format you ship
JSON, YAML, Android XML, iOS strings, XLIFF, Flutter ARB, and Excel — one upload per file, 50+ target locales, no account needed to start.
Who it's for
Built for developers shipping multilingual apps.
If you maintain en.json by hand and dread the day someone asks for twelve more locales, Localee is built for you. Indie developers use it as an AI i18n file translator without a TMS subscription; SaaS teams run release files through it before handoff; mobile developers drop in Android strings.xml, iOS .strings, or Flutter ARB files and get back output that still compiles.
It also slots into existing localization pipelines. XLIFF exports from Phrase, Lokalise, or Crowdin come back with every placeholder intact, and the Excel localization translator covers the spreadsheets that agencies and stakeholders actually send you.
How it works
From source file to 50+ locales in three steps.
Upload the file you already have — JSON, YAML, XML, XLIFF, ARB, or Excel. Localee parses the structure instead of scraping text, so keys, nesting, comments, and ordering are never at risk.
The AI translates only the values, carrying ICU messages, {variables}, and %@ tokens across untouched. Download the result and drop it straight back into your repo: no manual repair pass, no diff noise, ready for CI. That is the difference between a localization file translator and a generic translation box.
Ship the next locale today.
Start a translation without signing up and see the first locales in minutes. Localee is free to try — bring the file you already have.
Open LocaleeFAQ
Questions, answered.
Is Localee free to use?
Localee is free to try — you can start a translation without signing up and see the first locales in minutes. Bring the file you already have; no credit card or account is needed to get started.
Which localization file formats does Localee support?
JSON, YAML, Android strings.xml, iOS .strings, XLIFF, Flutter ARB, and Excel. One upload per file, with 50+ target locales — including XLIFF exports from TMS platforms like Phrase, Lokalise, or Crowdin.
Will placeholders and ICU messages survive translation?
Yes. ICU messages, {variables}, %@, and %s tokens are detected before translation and carried over untouched, so runtime interpolation keeps working in every locale. Keys, comments, nesting, and file ordering are treated as untouchable too.
How is Localee different from DeepL or Google Translate?
Generic translators work on plain text — paste a localization file in and you get back broken keys, mangled placeholders, and lost comments. Localee parses the file structure first and translates only the values, so the output drops straight back into your repo and still compiles.
Can I translate one JSON file into 50 languages at once?
Yes. Upload the source file once, pick your target locales, and Localee generates one output file per locale in a single batch — each with identical keys and structure, ready to commit.
More from Twelvefold