Converting an RSS / Atom / SOAP response into JSON to consume in a JS app. Generating XML config from a JSON template (build configs, Spring beans, OOXML scaffolds). Quickly extracting nested values — convert XML to JSON, then use any JSON tool you already know. Round-tripping data and confirming the shape survives the conversion.

Single child vs array. A document with one becomes {"item": {...}} ; the same document with two becomes {"item": [..., ...]} . Consumers must handle both shapes (or normalise on the way out). Element order is not guaranteed. JSON objects don't preserve key order across all parsers/transmissions. If your XML has order-significant siblings, JSON is the wrong destination. Mixed content collapses. An element like hello world ! doesn't round-trip — text and inline elements interleave in a way that has no clean object representation. Attribute prefix collisions. If an XML element has a child whose name starts with @ , change the prefix to something else first. Namespaces are kept verbatim. ns:tag stays as the JSON key "ns:tag" . xmlns: attributes likewise. Numbers and booleans aren't auto-coerced. XML text is always strings; "1" stays "1" in JSON. Coerce types in your application code if you need them. JSON → XML requires a single root key. XML demands exactly one root element; the input JSON must be an object with one top-level key.

XML ↔ JSON Converter

Convert XML to JSON or JSON back to XML. Handles attributes, text nodes, and arrays sensibly.

Direction

Attribute prefix

Text node key

Indent

Input

Output

Enter input above to see the result.

What is this for?

XML and JSON are the two dominant data interchange formats and you regularly need to translate between them — for migrating from a SOAP API to a REST one, plumbing legacy feeds into a modern stack, or just reading XML in a tool that only speaks JSON. The mapping is opinionated rather than reversible-by-default, because XML has features (attributes, mixed content, ordered children) that JSON doesn't. This tool uses the conventional fast-xml-parser-style mapping: attributes get a prefix (default @), text nodes go to a key (default #text), and repeated child elements collapse to arrays. Both directions run in your browser.

When to use it

Converting an RSS / Atom / SOAP response into JSON to consume in a JS app.
Generating XML config from a JSON template (build configs, Spring beans, OOXML scaffolds).
Quickly extracting nested values — convert XML to JSON, then use any JSON tool you already know.
Round-tripping data and confirming the shape survives the conversion.

Common gotchas

Single child vs array. A document with one <item> becomes {"item": {...}}; the same document with two becomes {"item": [..., ...]}. Consumers must handle both shapes (or normalise on the way out).
Element order is not guaranteed. JSON objects don't preserve key order across all parsers/transmissions. If your XML has order-significant siblings, JSON is the wrong destination.
Mixed content collapses. An element like <p>hello <b>world</b>!</p> doesn't round-trip — text and inline elements interleave in a way that has no clean object representation.
Attribute prefix collisions. If an XML element has a child whose name starts with @, change the prefix to something else first.
Namespaces are kept verbatim. ns:tag stays as the JSON key "ns:tag". xmlns: attributes likewise.
Numbers and booleans aren't auto-coerced. XML text is always strings; "1" stays "1" in JSON. Coerce types in your application code if you need them.
JSON → XML requires a single root key. XML demands exactly one root element; the input JSON must be an object with one top-level key.