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.
I18NEXT to RESX
Converting a .i18next font to .resx 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 I18NEXT 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 i18next JSON to .NET RESX resources
Converting a .i18next font to .resx 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 .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. For this route the practical draw is first-class in the .NET toolchain with designer support and compile-time accessors and can carry binary assets alongside strings, keeping a UI's resources together — balanced against extremely verbose — the schema preamble often outweighs the content, which is worth knowing before you commit a large batch.
Why convert I18NEXT to RESX?
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 .resx buys you first-class in the .NET toolchain with designer support and compile-time accessors, which is why it is the better fit for localising a WinForms, WPF, ASP.NET or MAUI application. Because the conversion runs locally, trying it costs nothing but a few seconds of compute on your own machine.
I18NEXT vs RESX at a glance
| Aspect | i18next JSON (.i18next) | .NET RESX resources (.resx) |
|---|---|---|
| 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 root is a plain <root> element; each entry is a <data name=…> containing <value> and optionally <comment> |
| Strongest at | localising a React, Vue, Angular or Node application | localising a WinForms, WPF, ASP.NET or MAUI application |
| Weak spot | no metadata at all — translators get keys and strings with no context | extremely verbose — the schema preamble often outweighs the content |
| 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 | 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 |
Pick RESX as the output
Select .resx in the output menu next to each file. The menu only offers targets this engine can genuinely produce, so if RESX 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 RESX file. Outputs keep the original filename with the .resx extension.
I18NEXT to RESX questions, answered
Will converting I18NEXT to RESX lose quality?
There is no visual quality to lose — i18next is text-oriented and resx 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 I18NEXT files here?
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.
Where will the RESX file work?
Visual Studio, Rider and the .NET SDK read RESX natively, and the major translation platforms support it. Anything outside the .NET world generally does not. Novus Convert reads the data/value/comment structure locally, refuses documents declaring a doctype or custom entities, and converts to and from the other localization formats; binary base64 resources are outside the string-catalog model and are not carried across.
Will the RESX file be bigger or smaller than my I18NEXT?
It depends on the content: the document root is a plain <root> element; each entry is a <data name=…> containing <value> and optionally <comment>. Convert one representative file first and compare before batch-processing a large set.
What happens to the metadata in my I18NEXT file?
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.
Can I convert RESX back to I18NEXT?
Yes — the reverse route exists as a separate tool. Bear in mind that round-tripping .i18next → .resx → .i18next is not a perfect undo when any lossy step is involved; keep your original if fidelity matters.