◆ File conversionFREE
XML⇄XLSXPlurals, arrays, translatable flags — all preserved · send the strings.xml as a sheet, load it straight back.
Converter· Local processing
Drop your .xml here
or pick from your device · your file never leaves your browser

Your app speaks strings.xml.
Your translator wants Excel.

01 · what this tool actually does for you

Turn an Android strings.xml into an Excel sheet a translator or vendor can edit, then load it straight back — plurals, string-arrays, translatable flags, the root namespaces and placeholders all preserved, every resource keyed by its name. Not generic XML-to-table — the one step an Android localization handoff actually needs.

Files never leave your deviceIn-browser · zero upload · NDA-friendly
Deterministic conversionThe same input always yields the same output
Lossless round-tripstrings.xml→Excel→strings.xml keeps every entry
02 · two formats, one round-trip

strings.xml and Excel are each good at different things

This conversion exists so Android developers and translators each use the format they're comfortable with — without losing anything in between.

strings.xml.xml

Android's resource format: a resources root holding string, string-array and plurals entries, each addressed by name, with quantity keywords (one, other…) on plural items and a translatable flag telling the build what to skip. Precise — not something to hand-edit by eye.

Excel.xlsx

The interface translators, reviewers and vendors find most natural: one row per string, source and translation side by side, easy to filter, bulk-edit and annotate. The catch: open a strings.xml in raw Excel and the plural structure collapses, the translatable flag is lost, and it won’t load back into your app.

What this tool guards is exactly that “won’t load back”: on export it keeps each plurals quantity and string-array index in the key, carries the translatable flag in the Type column, and stores the root xmlns attributes in reserved @@resources.* rows — so the sheet rebuilds into a valid strings.xml on the way back. A couple of things a spreadsheet can’t hold are reported, never silently dropped: XML comments and the original indentation (the output uses a clean canonical layout), plus resource attributes beyond name and translatable.

03 · common questions

You're probably wondering

Will my file be uploaded?+
No. Parsing and conversion run entirely in your browser (a Web Worker handles large files); the file never leaves your machine and never touches a server. That's a hard requirement for NDA-bound localization work, so the tool is built fully client-side.
How do I send an Android strings.xml to a translator who only uses Excel?+
Convert the strings.xml to an Excel sheet here, hand the sheet to the translator or vendor, then load the edited sheet back to strings.xml — one row per string, source and translation side by side. A <string-array> becomes name[0], name[1]… and a <plurals> becomes name#one, name#other…, so the structure rebuilds exactly.
Does converting keep plurals, string-arrays and the translatable flag?+
Yes. Each <plurals> item keeps its quantity in the key (name#one, name#other), each <string-array> item keeps its index (name[0]), and translatable="false" is carried in the Type column so it round-trips. The <resources> root namespaces are stored in reserved rows and restored. XML comments and the exact indentation are not reproduced — the rebuilt file uses a clean canonical layout — and that is reported, never silent.
How is this different from just opening the XML in Excel?+
Open a strings.xml in raw Excel and the plural grouping flattens, the translatable flag vanishes, and inline markup gets mangled — it won’t load back into your app. This tool treats round-trip fidelity as the whole point: plural quantities and array indices live in the key, the translatable flag rides a column, and the XML rebuilds cleanly. It’s also fully local — nothing is uploaded.
Which files does it handle, and is it free?+
It handles Android res/values strings.xml resource files — <string>, <string-array> and <plurals>. Other Android resource types (<color>, <dimen>…) in the same file are skipped and reported, never silently converted. This tier is completely free, no account, no usage limits.
04 · who made this / why

Built by someone who's done this work

This isn’t a thin wrapper over a large model, and it isn’t an open-source library reskinned. It comes from years of game-localization frontline work and the pile of "nobody notices until it breaks" details that come with it.

The app ships a strings.xml; the translator only wants to edit in Excel — the format loss in between shouldn’t be a human’s job to absorb.

Hand a strings.xml to a vendor and nine times out of ten it comes back with the plural grouping flattened, the translatable flag wiped, quantities guessed at — and it won’t build. We hit every one of those, so the tool guards them by default: quantities and indices kept in the key, the translatable flag preserved in a column, the root namespaces stored and restored.

Free, fully local, instant. It’s one step in a workflow, not a platform — but it comes from a place that genuinely understands localization.