Add your XLIFF file
Drop one or more .xliff 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.
XLIFF to ARB
Converting a .xliff font to .arb 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 XLIFF 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 XLIFF 2.0 to Application Resource Bundle
Converting a .xliff font to .arb repackages the same glyphs and metrics for a different delivery target. A .xliff file is an XLIFF document written with the long extension, most often at version 2.0 — the redesigned OASIS standard in which each translatable string is a unit containing one or more segments, each with its own source and target. The payload matches the .xlf form; the structure is what changed.
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. For this route the practical draw is metadata lives with the string, so translators get context without a separate file and iCU MessageFormat covers plurals and gender without extra entries — balanced against the @-key convention doubles the entry count and looks odd to anyone new to it, which is worth knowing before you commit a large batch.
Why convert XLIFF to ARB?
The practical trigger for this conversion is usually a mismatch: with .xliff, less widely supported than 1.2 despite being the newer standard. Switching to .arb buys you metadata lives with the string, so translators get context without a separate file, which is why it is the better fit for localising a Flutter application through gen_l10n. Because the conversion runs locally, trying it costs nothing but a few seconds of compute on your own machine.
XLIFF vs ARB at a glance
| Aspect | XLIFF 2.0 (.xliff) | Application Resource Bundle (.arb) |
|---|---|---|
| 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 root xliff element carries srcLang and trgLang, replacing 1.2's source-language and target-language on file | 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 |
| Strongest at | interchange with tooling built against the 2.0 core | localising a Flutter application through gen_l10n |
| Weak spot | less widely supported than 1.2 despite being the newer standard | the @-key convention doubles the entry count and looks odd to anyone new to it |
| Metadata | unit identifiers, source and target text and the declared languages are preserved. Module data — change tracking, glossary entries, translation candidates — and inline markup are not represented in flat key-value targets | 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 |
Pick ARB as the output
Select .arb in the output menu next to each file. The menu only offers targets this engine can genuinely produce, so if ARB 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 ARB file. Outputs keep the original filename with the .arb extension.
XLIFF to ARB questions, answered
Will converting XLIFF to ARB lose quality?
There is no visual quality to lose — xliff is text-oriented and arb 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 XLIFF files here?
Yes — the .xliff 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 ARB file work?
Flutter's tooling reads ARB natively and the major translation platforms support it; elsewhere it is just JSON. Novus Convert flattens the bundle locally, skipping @-prefixed metadata keys so they do not appear as translatable entries, and converts to and from the other localization formats. Placeholder metadata and ICU plural structure are not representable in flat targets.
Will the ARB file be bigger or smaller than my XLIFF?
It depends on the content: 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. Convert one representative file first and compare before batch-processing a large set.
What happens to the metadata in my XLIFF file?
In .xliff, unit identifiers, source and target text and the declared languages are preserved. Module data — change tracking, glossary entries, translation candidates — and inline markup are not represented in flat key-value targets. 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 ARB back to XLIFF?
Yes — the reverse route exists as a separate tool. Bear in mind that round-tripping .xliff → .arb → .xliff is not a perfect undo when any lossy step is involved; keep your original if fidelity matters.