JSON to XML

Convert JSON data to XML format for integration with XML-based systems

JSON Input

XML Output

Success
Warning

What is JSON to XML Converter?

Modern services trade JSON, but huge swathes of enterprise infrastructure still speak XML — SOAP APIs, B2B EDI feeds, banking middleware, telecom OSS/BSS systems, and government data exchanges. When the system on the other end of the integration only accepts XML, you need a fast way to translate. JSON to XML Converter does that mapping in your browser, deterministically: every JSON key becomes an XML element, nested objects become nested elements, and arrays repeat the same tag for each item.

The conversion follows the conventions documented in the W3C's XML 1.0 specification — well-formed elements, properly escaped content, and a UTF-8 declaration. For background on the source format, the official JSON specification and RFC 8259 are the canonical references.

How to Use JSON to XML Converter

  1. Paste Your JSON – Drop your JSON object or array into the left panel. The root must be either an object or a single-element array; XML can't represent two sibling root elements.
  2. Watch the Conversion – XML is generated automatically as you type. The right panel updates in real time with no Convert button needed.
  3. Check Element Names – Every JSON key becomes an XML element name. If a key contains a space or starts with a digit, it's sanitised so the output stays well-formed.
  4. Inspect Arrays – Array items repeat the parent's tag name (e.g., a "sectors" array becomes multiple <sectors> elements). This matches the most common JSON-to-XML mapping convention.
  5. Copy or Download – Use Copy to put the XML on your clipboard, or Download to save it as a .xml file ready for your integration.

Pro Tip: If the target system needs XML attributes (not elements), prefix the JSON key with @ (e.g., "@id": "BS-4471"). The converter recognises this convention and emits the value as an attribute instead of a child element.

Example

A base-station configuration: JSON keys become XML element names, nested objects become nested elements, and array items repeat the same tag.

JSON → XML Convert
base-station.jsonJSON
{
  "baseStation": {
    "id": "BS-4471",
    "vendor": "Ericsson",
    "sectors": [
      { "tac": 12001, "band": "n78" },
      { "tac": 12002, "band": "n28" }
    ]
  }
}
base-station.xmlXML
<?xml version="1.0" encoding="UTF-8"?>
<baseStation>
  <id>BS-4471</id>
  <vendor>Ericsson</vendor>
  <sectors>
    <tac>12001</tac>
    <band>n78</band>
  </sectors>
  <sectors>
    <tac>12002</tac>
    <band>n28</band>
  </sectors>
</baseStation>

Common Use Cases

Integrating With Legacy SOAP APIs

Plenty of carrier billing, finance, and government APIs still accept only SOAP — and SOAP envelopes are XML to their bones. If your application produces JSON internally but needs to call one of these services, this converter is the bridge. Drop the JSON in, take the XML out, wrap it in your SOAP envelope, and you're done.

Generating XML for Configuration Files

Many telecom network elements (HSS, MME, SGSN) and database systems still load configuration from XML. If your config lives in a JSON-first source (a git-tracked config-as-code repo, for instance), convert it here as part of your build step. MDN's XML reference is a good companion when you're double-checking the output structure.

Producing RSS / Atom / Sitemap Feeds

RSS, Atom, and sitemap.xml are all XML formats with strict schemas. If your content management system stores entries as JSON, you can convert each entry to XML and concatenate the results into a valid feed. For the format details, the W3Schools XML tutorial covers the basics.

Key Features

  • Real-Time Conversion – Output updates as you type; no Convert button to click.
  • Well-Formed XML Output – Includes the standard <?xml version="1.0" encoding="UTF-8"?> declaration and properly escapes &, <, and > in text content.
  • Nested Structures – Arbitrarily deep JSON objects and arrays are walked recursively to produce matching XML hierarchies.
  • Attribute Support – The @key convention emits attributes instead of child elements when you need them.
  • Privacy First – Conversion runs entirely in your browser; nothing is uploaded.

Frequently Asked Questions

How are JSON arrays represented in XML?

Each array item is emitted as a separate element using the parent key's name. So "sectors": [{...}, {...}] becomes <sectors>...</sectors> twice. This is the most common convention but not the only one — some systems prefer a wrapper element (<sectors><item>...</item></sectors>). If the target system needs the latter, wrap the array in an object first.

What happens with JSON keys that aren't valid XML element names?

XML element names can't contain spaces, can't start with a digit or the letters "xml", and can only use a restricted set of characters. Invalid characters are replaced with underscores; if a name starts with a digit, an underscore is prepended. The XML spec is the source of truth — see the Name production in XML 1.0.

How are null values converted?

XML has no built-in null. A JSON null is emitted as an empty self-closing element (<field/>) so the absence of a value is preserved. If your target system needs the xsi:nil="true" convention from XML Schema, you'll need to post-process the output.

Does the tool handle namespaces?

Not automatically — XML namespaces require explicit prefix declarations (xmlns:foo="...") and the input JSON has no notion of those. For namespace-aware output, manually add the xmlns attributes to the root element after conversion, then validate against your schema using a tool like an online XSD validator.

Is my data safe?

Yes. The conversion is implemented entirely in client-side JavaScript. Neither the input JSON nor the output XML is sent over the network, cached, or logged.

Related Tools

  • JSON Formatter – Format your JSON before conversion so it's easier to spot mapping issues.
  • JSON Validator – Make sure the input is valid JSON before you bother converting.
  • JSON to CSV – When the target system speaks CSV instead of XML.
  • JSON to Table – Preview your JSON as a table to confirm the shape before converting.

Useful Resources