Add your ARB file
Drop one or more .arb 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.
Converting a .arb font to .androidxml repackages the same glyphs and metrics for a different delivery target. Free, private, and validated — the file never leaves your browser.
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.Converting a .arb font to .androidxml repackages the same glyphs and metrics for a different delivery target. An .arb file is an Application Resource Bundle: a JSON object in which each key maps to a translatable string, and keys prefixed with @ carry that string's metadata — its description, its placeholder types and their formatting. It is the localisation format Flutter's intl tooling generates from and compiles to typed Dart accessors.
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.
The practical trigger for this conversion is usually a mismatch: with .arb, the @-key convention doubles the entry count and looks odd to anyone new to it. 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.
| Aspect | Application Resource Bundle (.arb) | 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 | the document is a single JSON object; ordinary keys map to strings, and @-prefixed keys map to metadata objects for the key of the same name | entries are <string name=…> with the translatable text as element content; the name is the R.string identifier the code references |
| Strongest at | localising a Flutter application through gen_l10n | localising an Android application |
| Weak spot | the @-key convention doubles the entry count and looks odd to anyone new to it | escaping rules are a common source of subtly broken translations |
| Metadata | keys and their translated values are preserved. @-prefixed metadata — descriptions, placeholder types and formats — and the @@locale marker are skipped rather than converted, because flat key-value targets have nowhere to put 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 |
Drop one or more .arb 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.
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.
Press Convert. The font tables are parsed and rewritten locally with fonteditor-core; glyph outlines, hinting, and kerning survive the trip.
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.
There is no visual quality to lose — arb 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.
Yes — the .arb 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.
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.
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.
In .arb, keys and their translated values are preserved. @-prefixed metadata — descriptions, placeholder types and formats — and the @@locale marker are skipped rather than converted, because flat key-value targets have nowhere to put 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.
Yes — the reverse route exists as a separate tool. Bear in mind that round-tripping .arb → .androidxml → .arb is not a perfect undo when any lossy step is involved; keep your original if fidelity matters.