Verified local conversion

XLF to ARB

Converting a .xlf 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

Convert supported files

Runs on your device

Drop XLF 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 1.2 to Application Resource Bundle

Converting a .xlf font to .arb repackages the same glyphs and metrics for a different delivery target. A .xlf file is an XLIFF document — the OASIS XML standard for moving translation work between tools. Each translatable string becomes a trans-unit holding a source element and, once translated, a target element, wrapped in a file element that records the source and target languages.

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 XLF to ARB?

The practical trigger for this conversion is usually a mismatch: with .xlf, verbose — several lines of markup per string. 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.

XLF vs ARB at a glance

AspectXLIFF 1.2 (.xlf)Application Resource Bundle (.arb)
Format typeText-based — characters and structure, so there is no visual quality lossText-based — characters and structure, so there is no visual quality loss
How it stores datathe root xliff element declares a version; file elements carry source-language and target-language attributesthe 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 atsending strings to a translation agency and getting reviewed work backlocalising a Flutter application through gen_l10n
Weak spotverbose — several lines of markup per stringthe @-key convention doubles the entry count and looks odd to anyone new to it
Metadataunit identifiers, source and target text and the declared source/target languages are preserved. Translation state, notes and inline placeholder markup are not carried into flat key-value formats, which have nowhere to record themkeys 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
01

Add your XLF file

Drop one or more .xlf 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.

02

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.

03

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.

04

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.

XLF to ARB questions, answered

Will converting XLF to ARB lose quality?

There is no visual quality to lose — xlf 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 XLF files here?

Yes — the .xlf 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 XLF?

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 XLF file?

In .xlf, unit identifiers, source and target text and the declared source/target languages are preserved. Translation state, notes and inline placeholder markup are not carried into flat key-value formats, which have nowhere to record 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 ARB back to XLF?

Yes — the reverse route exists as a separate tool. Bear in mind that round-tripping .xlf → .arb → .xlf is not a perfect undo when any lossy step is involved; keep your original if fidelity matters.