JSON to XML Converter

JSON and XML do not map onto each other perfectly, so every converter has to choose a convention. The widely used approach applied here prefixes attributes with @ and stores mixed content under #text, which keeps the round trip predictable. Two differences are worth knowing: XML has no native array type, so a single-item list converts back as a plain value rather than a one-element array, and XML values are always strings, so a number written in JSON returns as a string. XML also restricts tag names — they cannot start with a digit or contain spaces — so illegal characters in JSON keys are replaced with underscores.

Each JSON key becomes an element name and its value becomes the element content. An array produces one element per item, all sharing the key’s name. Going the other way, repeated sibling tags collapse into an array, attributes are prefixed with @ and mixed text is stored under #text.

The JSON-to-XML mapping is a convention, not a standard, so another tool may produce different output for the same input. Round trips are not perfectly lossless: single-item arrays return as plain values, all XML values come back as strings, and comments and processing instructions are stripped.

A book object with a title, a year and a two-item tags array becomes a <book> element containing <title>, <year> and two <tags> elements. Converting that XML back produces the original object with tags restored as an array.

1. Choose whether you are converting JSON to XML or XML to JSON.
2. Paste your document into the box.
3. For JSON to XML, name the root element.
4. Copy or download the converted result.

• Expecting a single-item array to survive the round trip as an array.
• Assuming numbers stay numbers — everything returns from XML as a string.
• Using JSON keys with spaces or leading digits, which are not valid XML tag names.
• Hand-escaping ampersands before converting, which double-escapes them.

This converter maps JSON structures onto XML elements and reads XML back into JSON. Arrays become repeated sibling tags, XML attributes become @-prefixed keys, element text becomes #text where an element has both, and CDATA sections are unwrapped safely.

Developers integrating modern JSON APIs with older XML-based systems, SOAP services or RSS feeds.

• Works in both directions with a consistent, documented convention.
• Preserves XML attributes rather than silently discarding them.
• Sanitises key names that are not legal XML tag names.
• Escapes reserved characters so the XML is always well-formed.

• Feeding a JSON API response into a legacy system that only accepts XML.
• Turning an RSS or SOAP response into JSON for a JavaScript front end.
• Inspecting the structure of an unfamiliar XML document as JSON.
• Building XML fixtures for tests from JSON sample data.