Convert XML to JSON Online — Free

How to convert XML to JSON

1. 1

   Add your XML file

   Drop or select a .xml file. Files up to 50MB process locally in your browser — nothing uploaded.

2. 2

   Run the conversion

   Your XML parses via the browser's DOMParser, element names become JSON object keys, attributes become @-prefixed keys (e.g., @id), text content becomes #text (or flattens when the element has no attributes/children), and repeated child elements collapse into arrays.

3. 3

   Download your JSON

   One click saves the result as a .json file. Your original file stays on your device.

Why convert XML to JSON?

Modern web stacks expect JSON. Many older APIs (government data feeds, legacy enterprise services), RSS/Atom feeds, SOAP/WSDL services, OPML, SVG source, GPX route files, and Android/iOS resource files still emit or consume XML. Converting to JSON lets you handle XML data with standard JavaScript tooling, Mongo/CouchDB-style databases, or any language's JSON library.

Common XML to JSON use cases

• Converting RSS or Atom feed XML into JSON for a JavaScript-based feed reader or aggregator
• Translating SOAP API responses from a legacy enterprise system into JSON for modern REST consumers
• Parsing a GPX (GPS exchange) XML file into JSON for integration with a web map or fitness tracking tool
• Migrating Android/iOS XML resource files into JSON for a cross-platform localization workflow

What file size to expect

A 10 KB RSS feed with 20 items becomes a JSON file of 8-12 KB — similar size. XML's verbose angle brackets are offset by JSON's required quotes and commas. For attribute-heavy XML (like SVG), JSON output can be 20-30% larger because attributes get @-prefixed as object keys.

Technical notes: XML → JSON

Conversion follows a common XML-to-JSON convention: elements become objects, attributes become @-prefixed keys, text content is either the sole value (when no attributes/children) or a #text key (when mixed with attributes). Repeated sibling elements with the same name collapse into an array. XML namespaces can be preserved or stripped via a toggle. CDATA sections decode to their contained strings. XML entities (&, <, >, ", ') are unescaped during parsing. Mixed content (text interspersed with elements) is preserved but may produce verbose JSON.

Compatibility and browser support

Output JSON is parseable by every modern tool. The conversion semantics follow the BadgerFish or Parker convention (similar to what xml2js, fast-xml-parser, and many cloud APIs produce). If you need a different convention (e.g., JsonML), post-process the output.

XML vs JSON

Frequently Asked Questions