How to Convert JSON to XML with Custom Root and Array Items

The Core Challenge: JSON vs XML Structure

Consider this JSON. It's clean and compact:

{
  "catalog": {
    "book": [
      {
        "title": "XML for Beginners",
        "author": "John Doe",
        "price": 29.99
      },
      {
        "title": "Advanced XML",
        "author": "Jane Smith",
        "price": 39.99
      }
    ]
  }
}

Converting this to valid XML requires decisions:

• What should the root element be if the JSON has no natural wrapper?
• How do array items get named? <book> or <item>?
• How are data types (numbers, booleans, nulls) represented?

The JSON to XML converter handles all of these with configurable options.

1. Setting the Root Element

XML requires a single root element for every valid document. If your JSON is an array or an object without a natural wrapper, you need to specify one:

<catalog>
  <book>
    <title>XML for Beginners</title>
    <author>John Doe</author>
    <price>29.99</price>
  </book>
  <book>
    <title>Advanced XML</title>
    <author>Jane Smith</author>
    <price>39.99</price>
  </book>
</catalog>

The Root Element input (default: root) controls this value. For most use cases, set it to a meaningful name like catalog, data, or response. The XML output updates instantly when you change this field.

2. Naming Array Items

JSON arrays become repeated XML elements. The tag name for each element is configurable via the Array Item input (default: item).

For an array like ["red", "green", "blue"]:

<root>
  <item>red</item>
  <item>green</item>
  <item>blue</item>
</root>


<root>
  <color>red</color>
  <color>green</color>
  <color>blue</color>
</root>

Choose an Array Item name that makes semantic sense for your data. If the root is catalog, array items could be product. If the root is users, array items should be user.

3. Data Type Handling

JSON has distinct data types; XML elements are text. The converter preserves type information through the element structure:

The XML output is always well-formed, with proper nesting and no orphaned elements.

Best Practices for JSON to XML Conversion

• Set a descriptive root element. Don't leave the default root — use something domain-specific like catalog, response, or config.
• Name array items semantically. If the root is users, items should be user. If the root is products, items should be product. This makes the XML self-documenting.
• Validate the XML output. After conversion, paste the result into an XML validator to ensure it's well-formed and matches your schema requirements.
• Handle arrays explicitly. If your JSON has deeply nested arrays, ensure the Array Item name doesn't collide with any existing element names in the same scope.
• Use JSON Editor for complex JSON first. If your JSON needs editing before conversion, use the JSON Editor to modify it, then paste the cleaned version into the converter.

Related Tools

Frequently Asked Questions