JSON to XML Converter - Attributes & Live Tree

JSON to XML - the conventions that matter

JSON and XML represent data very differently. JSON has objects, arrays, and primitive types. XML has elements, attributes, and text content - with no native concept of arrays or booleans. Converting between them means making a series of conventions explicit, and getting them right is the difference between XML that "looks okay" and XML that actually validates against a schema.

Attributes vs elements - the @ convention

The most common convention, used by Newtonsoft's Json.NET, FreeFormatter, and most JSON-XML libraries, is to prefix a key with @ to mark it as an XML attribute rather than a child element. So:

{"@id": "42", "name": "Rahul"}

becomes:

<root id="42"><name>Rahul</name></root>

When an element needs both attributes and text content, a special #text key holds the text value alongside the @-prefixed attributes.

Arrays - XML's biggest gap

XML has no array type. A JSON array like "tags": ["new", "sale"] is conventionally represented as repeated elements with the same tag name: <tags>new</tags><tags>sale</tags>. Some schemas instead expect array items wrapped in a generic container, like <tags><item>new</item><item>sale</item></tags>. This tool supports both - pick whichever matches the schema you're integrating with.

Booleans, numbers, and null in XML

XML text content is always a string - there's no native boolean or number type. A JSON true becomes the text true, and a JSON null becomes an empty element. If the system consuming your XML needs typed values, it typically uses an xsi:type attribute or a separate schema (XSD) to specify expected types - this is outside what a generic converter can infer.