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 .xlf 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 .xlf 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.
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. For this route the practical draw is a real published standard rather than a vendor convention and expresses review state and inline formatting that simpler formats cannot — balanced against verbose — several lines of markup per string, 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 .xlf buys you a real published standard rather than a vendor convention, which is why it is the better fit for sending strings to a translation agency and getting reviewed work back. Because the conversion runs locally, trying it costs nothing but a few seconds of compute on your own machine.
| Aspect | i18next JSON (.i18next) | XLIFF 1.2 (.xlf) |
|---|---|---|
| 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 root xliff element declares a version; file elements carry source-language and target-language attributes |
| Strongest at | localising a React, Vue, Angular or Node application | sending strings to a translation agency and getting reviewed work back |
| Weak spot | no metadata at all — translators get keys and strings with no context | verbose — several lines of markup per string |
| 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 | 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 |
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 .xlf in the output menu next to each file. The menu only offers targets this engine can genuinely produce, so if XLF 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 XLF file. Outputs keep the original filename with the .xlf extension.
There is no visual quality to lose — i18next is text-oriented and xlf 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.
Every serious translation management system reads XLIFF 1.2, and it is the safest common denominator for handing work to a vendor. Novus Convert reads both 1.2 trans-units and 2.0 units through one bounded parser, rejects documents carrying a doctype or custom entities outright, and converts to and from the other localization formats locally.
It depends on the content: the root xliff element declares a version; file elements carry source-language and target-language attributes. 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 → .xlf → .i18next is not a perfect undo when any lossy step is involved; keep your original if fidelity matters.