JSON vs XML

Before JSON took over, XML was the universal format for exchanging data between systems. Both formats are still in active use today, and understanding their trade-offs helps you read legacy systems and make good design decisions. In this lesson of our JSON tutorial series, we compare the two formats side by side and explain when each one is the right choice.

The Same Data, Two Ways

Here is a small product record in JSON:

json

{
  "product": {
    "id": 501,
    "name": "Mechanical Keyboard",
    "price": 89.99,
    "tags": ["input", "gaming"]
  }
}

And the equivalent XML:

xml

<product>
  <id>501</id>
  <name>Mechanical Keyboard</name>
  <price>89.99</price>
  <tags>
    <tag>input</tag>
    <tag>gaming</tag>
  </tags>
</product>

The XML version repeats every element name as a closing tag, which makes it noticeably longer. For large payloads this verbosity translates into real bandwidth and parsing cost.

Structural Differences

Data model: JSON maps directly to objects and arrays in programming languages. XML is a document tree with elements, attributes, and text nodes, so a value like price could live in an element, an attribute, or text content, and consumers must know which.
Types: JSON distinguishes numbers, booleans, and null natively. In XML everything is text until a schema says otherwise; <price>89.99</price> is just a string.
Arrays: JSON has first-class arrays. XML represents lists by repeating elements, and parsers cannot always tell one child from a list of one.
Parsing: browsers parse JSON with one built-in call. XML requires DOM or SAX parsing and often XPath for navigation.

Where XML Still Wins

XML is not obsolete. It retains genuine strengths:

Documents with markup: mixed content such as a paragraph containing bold text is natural in XML and awkward in JSON. HTML itself is XML-like for this reason.
Mature validation: XML Schema (XSD) and DTDs are long established, although JSON Schema has largely closed this gap.
Namespaces: XML can safely combine vocabularies from different organizations in one document.
Established ecosystems: SOAP web services, RSS and Atom feeds, SVG images, Android layouts, and Maven configuration files are all XML and are not going anywhere.

Where JSON Wins

For structured data exchange between programs, JSON is smaller, easier to read, faster to parse, and maps cleanly onto native data structures. That is why essentially all new public web APIs are JSON-first, why configuration formats such as package.json chose it, and why document databases adopted it as their storage model.

Making the Choice Today

Choose JSON for APIs, configuration, logging, and anything consumed by JavaScript. Choose XML when you are integrating with an existing XML ecosystem such as SOAP or RSS, or when your data is a marked-up document rather than a record. Many enterprises run both, exposing modern JSON APIs in front of older XML services.

Key Takeaways

JSON is more compact and maps directly onto native objects and arrays with real types.
XML treats everything as text and shines for markup-heavy documents and namespaced vocabularies.
New web APIs are almost universally JSON; XML persists in SOAP, feeds, SVG, and configuration ecosystems.
Pick the format that matches your data: records favor JSON, documents favor XML.

Next up: Parsing JSON in JavaScript, where JSON.parse and JSON.stringify get a full, practical treatment.