XML to JSON Converter Online

XML attributes are prefixed with @ in the JSON output to distinguish them from child elements. For example, <item id="123" status="active"> becomes {"item": {"@id": "123", "@status": "active"}}. This is a widely used convention that keeps the mapping unambiguous and reversible.

Repeated elements at the same level are automatically converted to JSON arrays. For example, multiple <item> elements inside a <list> parent become a JSON array of objects: {"list": {"item": [{...}, {...}]}}. Single elements remain as objects, not wrapped in an array.

Yes. Namespace prefixes are included in the JSON keys. For example, <soap:Envelope> becomes {"soap:Envelope": {...}}. This preserves the namespace context so you can identify which schema each element belongs to. You can strip prefixes by editing the output if your use case does not require them.

Yes. XHTML and SVG are both valid XML and can be parsed by our converter. The document structure is converted to nested JSON objects, which is useful for content extraction, structural analysis, or programmatic manipulation of markup.

When an XML element contains both text content and child elements (mixed content), the text is extracted to a special #text key in the JSON output. For example, <p>Hello <b>world</b></p> becomes {"p": {"#text": "Hello ", "b": "world"}}.

CDATA sections (<![CDATA[...]]>) are treated as text content. The raw text inside the CDATA block is extracted and placed in the JSON output as a string value, without the CDATA wrapper. This is correct since CDATA is just an XML mechanism for escaping special characters.

Yes. Paste the entire SOAP envelope including the Envelope, Header, and Body elements. The converter handles namespace prefixes (soap:, wsdl:, etc.) and produces a nested JSON structure that mirrors the SOAP message hierarchy. This is particularly useful when migrating legacy SOAP integrations to REST.

For most documents, yes. Use our JSON to XML converter to transform the JSON output back to XML. The @ prefix convention for attributes and the structural mapping make the round-trip largely reversible, though XML-specific features like processing instructions, comments, and DTDs are not preserved in JSON.

The converter handles XML files up to 10 MB comfortably, which covers virtually all configuration files, API responses, and data exports. Processing happens entirely in your browser, so performance depends on your device but is typically instant for files under 1 MB.