No processing of your file contents takes place on any server. You need no data-processing agreement with gottrix to handle confidential or business documents.
Hosted in GermanyGlobal Content Delivery
Origin servers at Hetzner in Germany, delivered worldwide through a content delivery network. Your file contents are never transmitted in the process - they never leave your device.
JSON is the language of modern APIs and web apps, yet many enterprise systems, SOAP services, RSS/Atom feeds, Office and configuration formats still require XML. This tool serialises your JSON tree into equivalent, well-formed XML.
The conversion runs entirely locally in your browser (fast-xml-parser, pure JavaScript). Object keys become elements; keys prefixed "@_" become XML attributes - exactly mirroring XML-to-JSON, so a round-trip is preserved. Because XML needs exactly one root element, a top-level array or an object with several top-level keys is wrapped in a <root> element; array entries become repeated <item> elements.
You will meet this when exporting to a legacy system, an XML-only import, a SOAP endpoint or an Office template. The result is indented, well-formed XML with an XML declaration - ready to open or feed into an XML toolchain. Invalid JSON is rejected with a clear error, and nothing is uploaded.
One structural difference shapes the result: XML requires exactly one root element. A JSON array at the root therefore gains an enclosing node, and array items of the same name become repeated elements of that name - precisely the shape XML processors and XSD schemas expect.
Specifications
Specifications
Input formats
JSON
Auto-conversion
XLSX, SQLite
Output format
XML
Batch processing
No
Processing
Locally in your browser (JavaScript)
File upload
None
In 3 steps
Drop or pick your JSON file.
The tool serialises it to XML.
Download the XML file.
Limitations: The result is well-formed XML with exactly one root element: arrays or objects with several top-level keys are wrapped in <root>, array entries become <item>. Keys prefixed "@_" become attributes - JSON has no native attribute concept, so without that prefix everything becomes elements. JSON numbers and booleans are written into the XML as plain text, since XML itself has no data types. Invalid JSON is rejected with a clear error.
FAQ
Is my file uploaded?
No. The conversion runs entirely locally in the browser - nothing is sent.
How are XML attributes produced?
Keys prefixed "@_" become attributes - exactly mirroring XML to JSON.
Why a <root> element?
XML needs exactly one root. Arrays and objects with several top-level keys are therefore wrapped in <root>.
What happens to JSON arrays?
Array entries become repeated <item> elements.
Is a round-trip possible?
Yes, the "@_" attribute convention matches our XML to JSON tool.