XML to JSON Converter

Understanding XML and JSON

XML (eXtensible Markup Language) is a versatile markup language that uses a hierarchical tag-based structure to represent data. Developed by the W3C in the late 1990s, XML became the standard for data exchange across enterprise systems, web services, and document formats. It supports features like attributes, namespaces, schemas (XSD/DTD), CDATA sections, and processing instructions that give it exceptional expressiveness and validation capabilities. Dive deeper into XML with our XML learning resource.

JSON (JavaScript Object Notation) is a lightweight, text-based data format that represents structured data using key-value pairs and ordered arrays. Its simplicity and native compatibility with JavaScript have made it the preferred format for REST APIs, configuration files, and client-server communication in modern web development. JSON supports six data types: strings, numbers, booleans, null, objects, and arrays. Explore JSON in depth in our comprehensive JSON guide.

The transition from XML to JSON reflects a broader industry shift toward simpler, more compact data formats. While XML excels in document-centric use cases with its rich metadata capabilities, JSON offers faster parsing, smaller payload sizes, and a more natural fit for the JavaScript-driven web ecosystem.

Why Convert XML to JSON?

As applications modernize and embrace RESTful architectures, converting XML data to JSON becomes a frequent requirement. Here are the most common real-world scenarios:

• Parsing SOAP API responses: Many enterprise services still return data in SOAP/XML format. Converting these responses to JSON allows your JavaScript or TypeScript frontend to process the data natively without XML parsing libraries, reducing bundle size and complexity.
• Processing RSS and Atom feeds: News aggregators, podcast apps, and content platforms consume RSS/Atom feeds that are XML-based. Converting feed data to JSON makes it straightforward to render in React, Vue, or Angular components and store in JSON-native databases.
• Migrating legacy XML configurations: Applications transitioning from older frameworks (Spring XML configs, Ant build files, web.xml) to modern tooling often need to convert XML configuration files to JSON equivalents for tools like package.json, tsconfig.json, or custom config files.
• Consuming XML-based data feeds: Financial data providers, weather services, and government open data portals frequently publish data in XML format. Converting to JSON enables easy integration with modern dashboards, data visualization libraries like D3.js, and NoSQL databases like MongoDB that store data natively in JSON-like documents.
• Building API translation layers: When building middleware or API gateways that sit between legacy XML systems and modern JSON-based microservices, XML to JSON conversion is a fundamental operation for request and response transformation.

How the Conversion Works

Converting XML to JSON requires mapping XML's rich feature set to JSON's simpler data model. The converter parses the XML document tree and systematically transforms each node into its JSON equivalent. Here is how each XML construct maps to JSON:

One important nuance is the loss of the attribute-vs-element distinction. In XML, <book isbn="123"><title>Dune</title></book> clearly separates the attribute isbn from the child element title. In JSON, both become object properties, so the @_ prefix convention is used to maintain this distinction. Similarly, when an element contains both text content and attributes, the special #text key holds the text value alongside the prefixed attribute keys.

Before and After Example

Here is a realistic example showing an XML document with attributes, nested elements, and repeated items being converted to its JSON representation:

<?xml version="1.0" encoding="UTF-8"?>
<library name="City Central">
  <location>
    <city>Springfield</city>
    <country code="US">United States</country>
  </location>
  <books>
    <book id="1" genre="fiction">
      <title>The Great Gatsby</title>
      <author>F. Scott Fitzgerald</author>
      <year>1925</year>
    </book>
    <book id="2" genre="science">
      <title>A Brief History of Time</title>
      <author>Stephen Hawking</author>
      <year>1988</year>
    </book>
  </books>
  <open>true</open>
</library>

{
  "library": {
    "@_name": "City Central",
    "location": {
      "city": "Springfield",
      "country": {
        "@_code": "US",
        "#text": "United States"
      }
    },
    "books": {
      "book": [
        {
          "@_id": "1",
          "@_genre": "fiction",
          "title": "The Great Gatsby",
          "author": "F. Scott Fitzgerald",
          "year": "1925"
        },
        {
          "@_id": "2",
          "@_genre": "science",
          "title": "A Brief History of Time",
          "author": "Stephen Hawking",
          "year": "1988"
        }
      ]
    },
    "open": "true"
  }
}

Notice several important conversion details in this example. The name attribute on<library> becomes @_name in JSON. The <country>element has both an attribute (code) and text content, resulting in the @_codeand #text properties. The two <book> sibling elements are automatically grouped into a JSON array. Also note that all values become strings in JSON since XML does not carry type information — 1925 and true appear as string values.

Tips and Best Practices

Related Tools

Explore more conversion and learning tools to work with XML and JSON formats: