Add your RESX file
Drop one or more .resx 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 .resx font to .i18next 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 .resx font to .i18next repackages the same glyphs and metrics for a different delivery target. A .resx file is a .NET XML resource file: a list of named data elements, each holding a value and an optional comment, used for the translatable strings and embedded assets of a .NET application. Visual Studio compiles it into a binary .resources file that is embedded in the assembly.
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. For this route the practical draw is plain JSON, so every tool in the JavaScript ecosystem already reads it and nesting keeps large catalogs navigable — balanced against no metadata at all — translators get keys and strings with no context, which is worth knowing before you commit a large batch.
The practical trigger for this conversion is usually a mismatch: with .resx, extremely verbose — the schema preamble often outweighs the content. Switching to .i18next buys you plain JSON, so every tool in the JavaScript ecosystem already reads it, which is why it is the better fit for localising a React, Vue, Angular or Node application. Because the conversion runs locally, trying it costs nothing but a few seconds of compute on your own machine.
| Aspect | .NET RESX resources (.resx) | i18next JSON (.i18next) |
|---|---|---|
| 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 root is a plain <root> element; each entry is a <data name=…> containing <value> and optionally <comment> | nesting is structural: objects group keys, and lookups use a dotted path with the separator configurable |
| Strongest at | localising a WinForms, WPF, ASP.NET or MAUI application | localising a React, Vue, Angular or Node application |
| Weak spot | extremely verbose — the schema preamble often outweighs the content | no metadata at all — translators get keys and strings with no context |
| Metadata | entry names, values and comments are preserved. The schema preamble, resheader declarations and base64 binary resources are not represented in string-catalog targets, and the culture — which lives in the filename — is not part of the document at all | 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 |
Drop one or more .resx 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 .i18next in the output menu next to each file. The menu only offers targets this engine can genuinely produce, so if I18NEXT 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 I18NEXT file. Outputs keep the original filename with the .i18next extension.
There is no visual quality to lose — resx is text-oriented and i18next 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 .resx 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.
Universally readable as JSON, and supported natively by i18next and every major translation platform. Novus Convert flattens nested objects into dotted keys locally — matching how the strings are addressed in code — and converts to and from the other localization formats.
It depends on the content: nesting is structural: objects group keys, and lookups use a dotted path with the separator configurable. Convert one representative file first and compare before batch-processing a large set.
In .resx, entry names, values and comments are preserved. The schema preamble, resheader declarations and base64 binary resources are not represented in string-catalog targets, and the culture — which lives in the filename — is not part of the document at all. 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 .resx → .i18next → .resx is not a perfect undo when any lossy step is involved; keep your original if fidelity matters.