FREE
10,000 words offered on sign up

Translate app localization files without breaking them

Upload the resource file your project already uses. AI Glot reads XLIFF, JSON, ARB, Android XML, iOS .strings, .properties and CSV, translates the strings, and hands back a file that drops straight into your repository.

Translate a localization file
AI Glot app localization background

From resource file to release in 3 steps

No export, no reshaping, no copy-paste. The file you commit is the file you upload.

1. Upload the file your project already uses

XLIFF and XLF, JSON and ARB, Android XML, iOS .strings, Java .properties, .NET RESX, or a CSV export if that is how your team works. Send a ZIP of them if you have one file per language.

Upload a file →

2. Say what the strings need

Describe the tone, the terms that must never change, and how UI strings should read in each language. AI Glot shows you the plan, including every placeholder and inline tag it will leave alone, before anything runs.

Write your instructions →

3. Commit the translated file

Download the same format you sent, with keys, structure and markup unchanged. Nothing to reformat, nothing to merge by hand.

Export result →

Placeholders and tags are read, never rewritten

Interpolated variables, ICU plurals, HTML fragments and platform-specific markup are recognised as structure. AI Glot translates the words around them and leaves them byte for byte.

Built for the way apps are actually localized

Your format, both ways

The file comes back in the format it arrived in. No conversion to a spreadsheet and back, which is where keys go missing.

Keys and structure preserved

Identifiers, nesting and ordering survive the round trip, so the translated file is a drop-in replacement rather than a merge conflict.

Terminology that holds across releases

Your workspace glossary pins product names and UI vocabulary, so the same term does not drift between two sprints.

A whole language folder at once

Send a ZIP of same-type files and get a translated bundle back, instead of running one job per locale.

App localization file translation FAQ

Which localization formats can AI Glot translate?

XLIFF and XLF, JSON and ARB, Android XML, iOS .strings, Java .properties, .NET RESX, YAML, PO and POT, plus CSV and Excel if your team works from exports. Homogeneous ZIP bundles are supported for compatible types.

Will my placeholders and variables survive?

Yes. Interpolated variables, ICU message syntax, positional arguments and inline markup are treated as structure rather than as text. They are read so the sentence around them makes sense, and written back unchanged.

Do I still have to export to CSV first?

No. That was the old workaround and it is where keys and ordering get lost. Upload the resource file itself and it comes back in the same format.

Can I translate one file into several languages at once?

Yes. Set several target languages on the same job and AI Glot returns one translated file per language, all under the same instructions and glossary.

How do I keep UI strings short enough for the layout?

Say so in your instructions, in plain language. A rule like "keep buttons under 20 characters, prefer the shorter synonym" is applied across every string in the file.

Can I translate only the strings that are missing?

Yes. Tell AI Glot to leave existing translations alone and it fills the gaps only, which is what you want when a release adds forty strings to a file that already has two thousand.

Why not paste the file into a general AI assistant?

A resource file is a contract with your build. General assistants reflow JSON, drop keys, translate placeholder names and silently truncate long files. AI Glot works on the file as a structure and validates it before you get it back.

10,000 words offered on sign up

Ready to translate your localization files?

Create a free account →