XML to JSON Converter — Online, Free, No Upload

What is XML → JSON?

An XML to JSON converter turns an XML document into a structured JSON representation you can pipe into JavaScript, Python, or any modern service. The tricky part is that XML has three concepts JSON doesn't: attributes, mixed content, and named-but-repeatable siblings. This tool applies the industry-standard mapping used by fast-xml-parser and xml2js: attributes become @-prefixed keys, text content lives under #text, and repeated siblings are automatically collapsed into arrays. Parsing runs on a hand-written tokenizer (no DOMParser dependency), so it works in Node, edge functions, and any browser without extra polyfills.

How to convert XML to JSON online

1. 1Paste your XML into the left editor (from a SOAP response, RSS feed, config file, etc.).
2. 2The right pane instantly renders the JSON equivalent, indented for readability.
3. 3Switch the attribute prefix (@, $, _, or none) to match the JSON library you plan to feed downstream.
4. 4Enable 'Parse numbers & booleans' if you want typed values in the output — leave it off to keep everything as strings for lossless round-trip.
5. 5Copy the result or switch to Tree view for a structural preview before shipping.

Use Cases

Code Examples

<library>
  <book id="b1">
    <title>Refactoring</title>
    <author>Martin Fowler</author>
  </book>
</library>

{
  "library": {
    "book": {
      "@id": "b1",
      "title": "Refactoring",
      "author": "Martin Fowler"
    }
  }
}

import { XMLParser } from "fast-xml-parser";
const parser = new XMLParser({ ignoreAttributes: false, attributeNamePrefix: "@" });
const obj = parser.parse(xml);

Key Concepts

Attribute vs. element

XML distinguishes <book id="b1"> (attribute) from <book><id>b1</id></book> (child element). JSON has no such distinction, so the tool marks attributes with a configurable prefix.

Mixed content

XML allows text and child elements to interleave inside the same parent. When mixed content is detected, the text goes under #text and children keep their own keys.

Sibling → array coercion

Two or more <book> siblings become an array of book objects. A lone <book> stays a scalar — this is convenient but can bite you when a variable-cardinality element is sometimes an array and sometimes not.

Lossy vs. lossless

String values → JSON strings is lossless. Enabling 'Parse numbers & booleans' introduces coercion ("123" → 123, "true" → true) that can lose information for zero-padded IDs, phone numbers, or the literal string "true".

Tips & Best Practices

• ▸For always-array coercion (so downstream code doesn't need to type-check), post-process the JSON to wrap known collections in arrays even when they have a single element.
• ▸If your XML has namespaces (xmlns:soap, etc.), they appear literally in the tag names in the JSON output. Strip them with a JSON transformer if you don't care about the namespace.
• ▸CDATA blocks are preserved as text but not marked — if you need to distinguish CDATA from a normal text node, wrap it in a sentinel string before conversion.
• ▸For very large XML documents (>10 MB), streaming parsers like sax-js are more memory-efficient than this tool's in-memory approach.
• ▸Round-tripping XML → JSON → XML is not always identical: whitespace between elements and attribute order aren't preserved. Semantic content is.