Add your STRINGS file
Drop one or more .strings files onto the converter above, or browse for them. They load into browser memory only — nothing is uploaded, so there is no size-based pricing and no server queue.
STRINGS to ANDROIDXML
Converting a .strings font to .androidxml repackages the same glyphs and metrics for a different delivery target. Free, private, and validated — the file never leaves your browser.
Private for supported formats — processed in your browser
Runs on your deviceConvert supported files
Drop STRINGS files here
Batch files can each use a different output. Nothing uploads for local conversions.
Working inputs include camera RAW, browser-local audio/video, PDF, CBZ/CBR comics, office documents, ebooks, markup, 3D models, structured text, images, and archives.About converting Apple strings localization to Android string resources
Converting a .strings font to .androidxml repackages the same glyphs and metrics for a different delivery target. A .strings file is Apple's localization resource: a flat list of "key" = "value"; statements, one per translatable string, usually named Localizable.strings and stored inside a per-language .lproj directory. It is what NSLocalizedString and its SwiftUI equivalents look up at runtime.
An Android string resource file — catalogued here as .androidxml — is the res/values/strings.xml of an Android application: a <resources> element containing <string name=…> entries, plus optional <plurals> and <string-array> groups. Because every Android project names the file strings.xml, there is no real extension to key on, so Novus Convert recognises these by the .android.xml suffix and files them under .androidxml to keep them distinct from generic XML. For this route the practical draw is integrated with Android's whole resource-qualifier system, so locale selection is automatic and real plural support using the CLDR categories rather than a bolted-on convention — balanced against escaping rules are a common source of subtly broken translations, which is worth knowing before you commit a large batch.
Why convert STRINGS to ANDROIDXML?
The practical trigger for this conversion is usually a mismatch: with .strings, no plural support at all — that requires a second file in a different format. Switching to .androidxml buys you integrated with Android's whole resource-qualifier system, so locale selection is automatic, which is why it is the better fit for localising an Android application. Because the conversion runs locally, trying it costs nothing but a few seconds of compute on your own machine.
STRINGS vs ANDROIDXML at a glance
| Aspect | Apple strings localization (.strings) | Android string resources (.androidxml) |
|---|---|---|
| Format type | Text-based — characters and structure, so there is no visual quality loss | Text-based — characters and structure, so there is no visual quality loss |
| How it stores data | each entry is `"key" = "value";` — the trailing semicolon is required, and both sides use C-style escapes | entries are <string name=…> with the translatable text as element content; the name is the R.string identifier the code references |
| Strongest at | localising an existing iOS, iPadOS or macOS application | localising an Android application |
| Weak spot | no plural support at all — that requires a second file in a different format | escaping rules are a common source of subtly broken translations |
| Metadata | keys and translated values are preserved. Comments are not treated as structured notes, and plural rules cannot be represented — a catalog with plurals converted into .strings will lose the plural forms because the format has no way to hold them | string names and their text are preserved. Plural groups, string arrays, the translatable attribute and the directory-derived locale are not represented in flat catalog targets |
Pick ANDROIDXML as the output
Select .androidxml in the output menu next to each file. The menu only offers targets this engine can genuinely produce, so if ANDROIDXML is selectable, the route is real and validated.
Convert on your device
Press Convert. The font tables are parsed and rewritten locally with fonteditor-core; glyph outlines, hinting, and kerning survive the trip.
Verify and download
Each result is signature-checked before the download unlocks, so a failed encode can never masquerade as a valid ANDROIDXML file. Outputs keep the original filename with the .androidxml extension.
STRINGS to ANDROIDXML questions, answered
Will converting STRINGS to ANDROIDXML lose quality?
There is no visual quality to lose — strings is text-oriented and androidxml is text-oriented, so the question is structural fidelity. Text, ordering, and basic structure are preserved; complex layout, embedded objects, and styling beyond the target's model are simplified.
Is it private to convert STRINGS files here?
Yes — the .strings file is processed inside your browser tab and never uploaded. The font tables are parsed and rewritten locally with fonteditor-core; glyph outlines, hinting, and kerning survive the trip. Close the tab and the file is gone from memory.
Where will the ANDROIDXML file work?
Android Studio and the Gradle build read these natively, and translation platforms support them widely. Novus Convert parses the <resources>/<string> structure locally, rejects documents carrying a doctype or custom entities, and converts to and from the other localization formats; plurals and string arrays are outside the flat one-string-per-key model and are not carried across.
Will the ANDROIDXML file be bigger or smaller than my STRINGS?
It depends on the content: entries are <string name=…> with the translatable text as element content; the name is the R.string identifier the code references. Convert one representative file first and compare before batch-processing a large set.
What happens to the metadata in my STRINGS file?
In .strings, keys and translated values are preserved. Comments are not treated as structured notes, and plural rules cannot be represented — a catalog with plurals converted into .strings will lose the plural forms because the format has no way to hold them. Re-encoding through the browser pipeline does not carry embedded metadata into the output, which doubles as a privacy scrub — check the exported file if you specifically need tags preserved.
Can I convert ANDROIDXML back to STRINGS?
Yes — the reverse route exists as a separate tool. Bear in mind that round-tripping .strings → .androidxml → .strings is not a perfect undo when any lossy step is involved; keep your original if fidelity matters.