JSON to XML Converter

What this tool does

JSON to XML Converter produces indented, well-formed XML from any JSON document. Choose the root and array item element names, which keys become attributes and which key holds element text, add an XML declaration and mark null values with xsi:nil. Keys that are not legal XML names are made safe automatically and special characters are escaped.

Plenty of systems still exchange XML: SOAP services, RSS feeds, banking and government interfaces, office formats and many enterprise integrations. JSON and XML do not map one to one, though. XML needs a single root element, has attributes as well as child elements, cannot use names that start with a digit or contain spaces, and has no native array, so a list has to become repeated elements.

This converter applies the widely used conventions for that mapping. A key holding an array produces one element per item, so { "book": [a, b] } becomes two <book> elements. Keys beginning with the chosen prefix, such as @id, become attributes, and a #text key supplies the element’s text when it also has attributes. When the JSON has several top-level keys, or is an array, a root element wraps it. Invalid characters in names are replaced with underscores, and &, < and > in values are escaped. It runs locally using fast-xml-parser.

How to use JSON to XML Converter

1. Paste JSON into JSON input, or click Sample to see attributes, arrays and text nodes in action.
2. Set the Root element name and the Element name for array items.
3. Choose which keys become attributes, for example keys starting with @, and the key used for element text.
4. Pick the Indentation, and toggle the XML declaration and self-closing empty elements.
5. Optionally mark null values with xsi:nil so XML Schema validators read them as nil.
6. Copy the XML or download data.xml; convert several JSON files at once in batch mode.

Tips for better results

• Use the same prefix your XML to JSON tool produced (@ or @_) to round-trip documents without losing attributes.
• If the JSON has exactly one top-level key, that key becomes the root and no extra wrapper is added.
• Arrays nested directly inside arrays are wrapped in item elements, because XML has no other way to express a list of lists.
• Validate the result with XML Formatter, which also reports the line and column of any problem.

Common use cases

• Building a request body for a SOAP or legacy XML API from JSON test data.
• Producing an XML product feed or sitemap-like file from a JSON export.
• Supplying sample XML to colleagues who maintain XSLT or XML Schema files.
• Migrating configuration from a JSON-based tool to an XML-based one.

Common mistakes to avoid

• Expecting a specific XML Schema to be satisfied automatically; element order and namespaces must still match what the schema requires.
• Using keys with spaces or leading digits and being surprised by renamed elements such as _2024 or first_name.
• Giving a nested object to an attribute key; attributes can only hold plain values, so such keys are written as elements instead.