What happens to XML text content in JSON?

If an element contains only text and no attributes or children, the text becomes a simple JSON string value. If an element has both text content and attributes or children, the text is stored under a special #text key. For example, John becomes {"@lang": "en", "#text": "John"}.

Why is XML to JSON conversion not perfectly reversible?

XML has concepts that JSON cannot represent: element ordering is meaningful in XML but JSON object keys have no guaranteed order, XML distinguishes between attributes and elements while JSON has only key-value pairs, XML supports namespaces and processing instructions, and XML mixed content (text interspersed with elements) is difficult to map to JSON. Converting JSON back to XML may produce a different structure than the original.

What are the common XML to JSON conversion conventions?

Several conventions exist: BadgerFish preserves all XML information including namespaces and ordering. Parker (or Ray) is minimal, discarding attributes and using the simplest possible JSON. GData (Google Data) uses $t for text content. This tool uses a practical middle ground: @ for attributes, #text for mixed content text, and arrays for repeated elements.

XML to JSON Converter - Free Online Tool

Q: How are XML attributes handled in JSON?

XML attributes are converted to JSON properties with an @ prefix. For example, becomes {"book": {"@id": "1"}}. This convention clearly distinguishes attributes from child elements in the JSON output. The @ prefix is a widely adopted convention used by several XML-to-JSON conversion libraries.

Q: How are repeated XML elements handled?

When multiple sibling elements share the same name, they are automatically grouped into a JSON array. For example, A B becomes {"items": {"item": ["A", "B"]}}. Single elements remain as plain values, and repeated elements become arrays. This is the most common convention for representing XML sequences in JSON.

Paste XML and convert it to JSON instantly. Attributes are prefixed with @, repeated elements become arrays, and text content uses #text keys.

How to Use the XML to JSON Converter

Paste your XML content into the left textarea. The converter processes it automatically as you type (with a brief debounce) and displays the JSON result in the right textarea. You can also click the "Convert XML to JSON" button for immediate conversion. The status bar shows whether the XML is valid, the root element name, and counts of total elements and attributes. Use the copy button to grab the JSON output.

This converter follows practical conventions for mapping XML to JSON. Attributes are represented with an @ prefix on their names, such as "@id": "123". When an element contains only text and no children or attributes, it becomes a simple string value. When text coexists with attributes or child elements, it is stored under the #text key. Repeated sibling elements with the same name are automatically grouped into JSON arrays.

XML to JSON Conversion Challenges

Converting XML to JSON is not a straightforward mapping because the two formats represent data differently at a fundamental level. XML is a document markup language with rich metadata capabilities, while JSON is a data interchange format optimized for simplicity. Understanding the key challenges helps you interpret the converted output correctly and handle edge cases in your workflow.

Attributes vs Elements

XML distinguishes between attributes (metadata attached to an element) and child elements (structured content within an element). JSON has no such distinction; everything is a key-value pair. This converter uses the @ prefix convention to differentiate attributes from child elements. For instance, <user role="admin"><name>John</name></user> becomes {"@role": "admin", "name": "John"}. This convention is used by libraries like xml2js, xmltodict (Python), and the BadgerFish convention.

Mixed Content and Text Nodes

XML supports mixed content where text and elements are interspersed, such as <p>Hello <b>world</b> today</p>. This pattern is common in document-oriented XML (HTML, DocBook, DITA) but extremely difficult to represent in JSON. This converter captures the text content in a #text key but cannot perfectly preserve the interleaving of text and elements. For document-oriented XML, consider using a DOM-aware approach instead of JSON conversion.

Common Conversion Conventions

Several standardized conventions exist for XML-to-JSON mapping. The BadgerFish convention preserves nearly all XML information, including namespaces, by using $ for text content and @ for attributes. The Parker convention is the most minimal, discarding attributes entirely and converting element names to keys with text content as values. The GData convention (used by Google) uses $t for text content. This tool uses a pragmatic approach that balances information preservation with readability.

Where XML Is Still Used

Despite JSON's dominance in web APIs, XML remains essential in many domains. SOAP web services, which underpin much of enterprise software, use XML exclusively. RSS and Atom feeds for content syndication are XML-based. SVG (Scalable Vector Graphics) is an XML vocabulary. Microsoft Office documents (DOCX, XLSX, PPTX) are ZIP archives containing XML files. Android application manifests, Maven build configurations, and .NET project files all use XML. Government and healthcare data exchanges (HL7, FHIR) frequently rely on XML. Understanding XML-to-JSON conversion is therefore a practical skill for integrating with these systems.

Tips for Handling Nested XML

Deeply nested XML structures produce deeply nested JSON objects, which can be difficult to work with. When converting complex XML documents, consider whether you need the entire document or just specific subtrees. For very large XML files, streaming parsers (SAX-style) are more appropriate than DOM-based conversion. When the JSON output will be consumed by a typed language, plan your data model to handle both single-element cases (objects) and repeated-element cases (arrays) since the converter produces different structures based on element repetition.

Frequently Asked Questions

How are XML attributes handled in JSON?

Attributes get an @ prefix on their key name, like "@id": "123". This distinguishes them from child elements in the JSON output.

How are repeated XML elements handled?

Sibling elements with the same name are grouped into a JSON array. Single elements stay as plain values. This is the most common convention.

What happens to text content?

Text-only elements become simple string values. Elements with both text and attributes/children store text under the #text key.

Is the conversion reversible?

Not perfectly. XML preserves element ordering, supports namespaces, and distinguishes attributes from elements. Some of this information is difficult to recover from JSON.

What conventions does this tool use?

@ prefix for attributes, #text for mixed content text, and automatic arrays for repeated elements. This is a practical middle ground between full-fidelity and minimal conversion.

XML to JSON Converter

Embed This Calculator