XML Input0 chars

JSON Output

Conversion Rules

XML element→JSON object key

XML attribute→@attributeName key

Text-only element→String / number / boolean value

Repeated elements→JSON array

Mixed content (text + children)→#text key for text

CDATA→Plain string value

What is XML to JSON Converter?

XML (eXtensible Markup Language) uses angle-bracket tags to structure data hierarchically and is the backbone of SOAP APIs, RSS feeds, SVG graphics, and many enterprise systems. JSON has largely replaced XML for new APIs and data interchange because of its simpler syntax and native JavaScript support. This converter parses any well-formed XML document and produces formatted JSON, handling the structural differences automatically: XML elements become JSON object keys, attributes become @prefixed keys, repeated sibling elements become JSON arrays, text-only elements become primitive values, and CDATA sections are unwrapped to plain strings. The result is ready to use in any JSON-consuming application.

How to Use

Paste your XML into the input panel on the left, or click "Load Example" to try a sample document.
Click "Convert to JSON" to parse the XML and transform it into a JSON object.
Review the JSON output in the right panel — it is pretty-printed with 2-space indentation for readability.
Click "Copy" to copy the JSON to your clipboard, or "Download" to save it as a .json file.
If there is a parse error, the tool shows exactly which part of the XML is invalid so you can fix it.

Why Use This Tool?

Runs entirely in your browser — no data is sent to a server, making it safe for confidential XML documents

Handles XML attributes (converted to @attr keys), repeated elements (auto-detected as arrays), and CDATA sections automatically

Supports nested elements of any depth — deeply nested XML structures are faithfully represented in JSON

Auto-detects numbers and booleans in text content — numeric values become JSON numbers rather than strings

Download output as a .json file with one click for immediate use in your application

Gracefully handles XML namespaces and processing instructions without errors

Tips & Best Practices

XML attributes become @attributeName in JSON — for example, <user id="1"> produces {"user": {"@id": "1"}}.
Repeated sibling elements with the same tag name are automatically detected and converted to a JSON array.
Text-only elements become simple string, number, or boolean values rather than nested objects.
CDATA sections are treated as plain text — the CDATA wrapper is stripped and the content is preserved.
The XML declaration (<?xml version="1.0"?>) is ignored and does not appear in the JSON output.

Frequently Asked Questions

How are XML elements and attributes mapped to JSON?

Each XML element becomes a JSON object key. Attributes are prefixed with @ (e.g., id="1" becomes "@id": "1"). Text-only elements become primitive values (strings, numbers, or booleans). Repeated sibling elements with the same tag become a JSON array. Mixed content (text plus child elements) uses a #text key for the text portion.

When should I NOT use this converter?

Avoid this tool when your XML relies heavily on mixed content (text interleaved with child elements), processing instructions that carry meaning, or DTD/entity declarations that must be preserved. Also, very large XML files (hundreds of MB) may cause browser memory issues since the entire document is parsed in memory.

Why does the same element sometimes become an object and sometimes an array?

When an element appears once, it becomes a single JSON object. When the same element appears multiple times as siblings, they are automatically grouped into a JSON array. This means the JSON structure can change if the number of repeated elements changes — consider this when writing code that consumes the output.

How are CDATA sections handled?

CDATA sections (<![CDATA[...]]>) are treated as plain text content. The CDATA wrapper is stripped and the inner content is preserved as a string value, identical to how non-CDATA text content is handled.

What happens with XML namespaces?

Namespaced elements and attributes are preserved with their prefix in the JSON output. For example, <ns:element> becomes "ns:element" as a key, and xmlns declarations are kept as attributes. The converter does not resolve or validate namespaces.

Is my XML data sent to any server?

No. All parsing and conversion runs entirely in your browser. Your XML documents and the generated JSON never leave your device. No data is collected, stored, or transmitted to any server.

Real-world Examples

RSS Feed to JSON

Convert an RSS feed XML into JSON for programmatic consumption by a news aggregator or dashboard.

Input

<rss version="2.0"><channel><title>Tech News</title><item><title>AI Breakthrough</title><link>https://example.com/ai</link></item><item><title>New Chip Released</title><link>https://example.com/chip</link></item></channel></rss>

Output

{
  "rss": {
    "@version": "2.0",
    "channel": {
      "title": "Tech News",
      "item": [
        {
          "title": "AI Breakthrough",
          "link": "https://example.com/ai"
        },
        {
          "title": "New Chip Released",
          "link": "https://example.com/chip"
        }
      ]
    }
  }
}

SOAP API Response to JSON

Convert a SOAP API XML response into JSON for easier processing in a JavaScript application.