Add your I18NEXT file
Drop one or more .i18next 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 .i18next font to .arb 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 .i18next font to .arb repackages the same glyphs and metrics for a different delivery target. An i18next resource is the JSON translation file used by the i18next library: nested objects whose leaf values are the translated strings, addressed in code by dotted keys such as nav.settings.title. Because the file is ordinarily just named en.json, Novus Convert identifies it by the .i18next.json suffix so it is not mistaken for arbitrary JSON.
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.
The practical trigger for this conversion is usually a mismatch: with .i18next, no metadata at all — translators get keys and strings with no context. 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.
| Aspect | i18next JSON (.i18next) | 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 | nesting is structural: objects group keys, and lookups use a dotted path with the separator configurable | 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 | localising a React, Vue, Angular or Node application | localising a Flutter application through gen_l10n |
| Weak spot | no metadata at all — translators get keys and strings with no context | the @-key convention doubles the entry count and looks odd to anyone new to it |
| Metadata | dotted keys and their translated values are preserved. The format carries no descriptions or notes to lose; plural and context suffixes are treated as ordinary distinct keys, because they are exactly that in the file | 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 |
Drop one or more .i18next 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 .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.
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 ARB file. Outputs keep the original filename with the .arb extension.
There is no visual quality to lose — i18next 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.
Yes — the .i18next 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.
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.
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.
In .i18next, dotted keys and their translated values are preserved. The format carries no descriptions or notes to lose; plural and context suffixes are treated as ordinary distinct keys, because they are exactly that in the file. 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 .i18next → .arb → .i18next is not a perfect undo when any lossy step is involved; keep your original if fidelity matters.