How are null values represented in the XML output?

A null value becomes a self-closing element with an explicit nil marker, e.g. , rather than an empty tag, so it's unambiguous that the value is null and not an empty string.

Transform

JSON to XML Converter

Turn JSON into well-formed XML for legacy APIs, SOAP services, and XML-based pipelines.

Open JSON to XML Converter All tools

Arrays become repeated elements with the same tag name
Invalid characters in keys are sanitized into valid XML tag names
Customizable root element name

JSON to XML Converter — JSON Prism

{
  "id": 1042,
  "name": "Dana",
  "roles": ["admin", "editor"],
  "active": true
}

JSON Prism·Browser-only · No uploads

Practical guide

Build, validate, and reuse JSON with less friction.

A focused walkthrough for deciding when the tool fits your workflow.

The JSON to XML Converter turns a JSON object or array into well-formed XML. Object keys become element names, values become element content or nested elements, and arrays become a sequence of repeated elements — the structural conversion XML requires since it has no native array type.

How to use the JSON to XML Converter

Paste your JSON into the input panel.
Open the Convert panel; it opens directly on the XML tab.
Copy the generated XML, or download it as an .xml file.
Set a custom root element name if your target system expects something other than <root>.

What it handles

Arrays converted into repeated <item> elements, since XML has no native list type
Object keys sanitized into valid XML tag names — invalid characters become underscores, and a tag starting with a digit gets an underscore prefix
Special characters in string values (&, <, >, ", ') escaped automatically so the output is well-formed
null values represented as a self-closing element with an explicit nil marker, distinguishing them from empty strings
A customizable root element, defaulting to <root>

JSON code example

This JSON:

JSON

{
  "user": {
    "name": "Alice",
    "roles": ["admin", "editor"]
  }
}

converts to:

XML

<?xml version="1.0" encoding="UTF-8"?>
<root>
  <user>
    <name>Alice</name>
    <roles>
      <item>admin</item>
      <item>editor</item>
    </roles>
  </user>
</root>

When to use it

Legacy and SOAP APIs. Many enterprise and SOAP-based services still expect XML request or response bodies.
XML-only pipeline steps. When a downstream tool in a data pipeline only accepts XML, convert the JSON payload before handing it off.
Generating sample XML. Quickly produce example XML from a JSON mock or schema, for documentation or test fixtures.
Migrating from XML-based systems. Cross-check that a newer JSON-based payload maps back to the XML shape an older system still expects.

Questions about JSON to XML Converter

Everything you need to know before you start.

Paste your JSON into the input panel, open the Convert panel, and select the XML tab (or use this dedicated JSON to XML tool, which opens directly into it). Each object key becomes an XML element wrapping its value.

Each item in an array becomes a repeated <item> element inside the parent tag, since XML has no native array type. A tags array like ["a","b"] becomes two <item> elements inside a <tags> wrapper.

Yes — the top-level wrapper defaults to <root>, and it's configurable so the output matches the element name your target API or schema expects.

Keys with spaces or characters XML doesn't allow in tag names (like @ or %) are sanitized — invalid characters become underscores, and a tag that would start with a digit gets an underscore prefix — so the output is always well-formed XML.

A null value becomes a self-closing element with an explicit nil marker, e.g. <field xsi:nil="true" />, rather than an empty tag, so it's unambiguous that the value is null and not an empty string.

Ready to use it?