Translate Android strings.xml files with AI
Import your Android strings.xml resources, let AI translate them with your glossary and context, review every string and export ready-to-ship resource files.
The native localization format of every Android app.
What a Android strings.xml file actually holds
Every Android app keeps its user-facing copy in res/values/strings.xml. Localizing means producing the same file under res/values-it, res/values-de and so on, with identical name attributes — the resource compiler matches them by name and falls back to the default file when one is missing.
The format has its own escaping rules, its own way of marking strings as untranslatable, and its own quirks around plurals and formatting arguments. Most of them only announce themselves at build time, or worse, at runtime on a user's device.
.xml
<resources>
<string name="welcome_title">Welcome back!</string>
<string name="save_button">Save changes</string>
</resources>What goes wrong when Android strings.xml files are translated badly
These are the failures that reach production, because none of them look like errors until they do.
Unescaped apostrophes fail the build
An apostrophe in a resource string must be written \'. Miss one and aapt stops the build with an error that points at the resource, not at the translation.
translatable="false" gets ignored
Strings flagged this way are identifiers and configuration values, not copy. Translate them and you ship an app pointing at a URL that does not exist.
Format arguments lose their order
%1$s and %2$d are positional. Languages reorder sentences freely, so translations must use the numbered form — an unnumbered %s in a reordered sentence throws at runtime.
Plurals are treated as ordinary strings
The plurals element takes quantity keys that differ per language. Copying the English one, two, other set into every locale produces wrong grammar for most of them.
How GetTranslated handles it
Import your Android strings.xml 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 Android strings.xml file into the free tool and get the translated version back straight away — no account, no email address.
Open the free Android strings.xml translatorFrequently asked questions
Is translatable="false" respected?
Yes. Strings marked as untranslatable are skipped on import and left exactly as they are on export.
Is escaping handled automatically?
Yes. Apostrophes, quotes and newlines are escaped the way the resource compiler expects, so exported files build without manual fixing.
Where do the exported files go?
Each export corresponds to res/values-{code}/strings.xml in your project — for example values-de for German.
500 keys free forever. No credit card.