XML to JSON Converter
Readable JSON From Any Feed

Jobs This XML to JSON Converter Handles for You

This XML to JSON converter reads an XML document and rewrites it as readable JSON objects and lists. Tags become keys, the text inside them becomes values, and nothing gets lost. Your browser reads the XML itself, so no file, from any feed or system, ever travels to a server.

XML is older and wordier than JSON, yet it still carries a lot of the world’s data. Bank statements, shipping labels, product feeds and many government systems use it every day. Most web code, on the other hand, prefers JSON. This Denwix page fills exactly that gap.

Swapping brackets for tags is the simple part. It is keeping the meaning: which values were attributes, which elements were lists, and where the text sat. The converter follows one clear set of rules for all three, and then it reports what it found.

How Each XML Part Becomes JSON

Each element becomes a key, and its content becomes the value. An element holding only text turns into a plain value, such as "title": "Midnight Rain". An element holding other elements turns into an object with one key per child.

Attributes keep an @ in front, so id="bk101" becomes "@id": "bk101". When an element has attributes and text together, the text goes under a #text key. Because the same two conventions work in reverse, our JSON to XML converter can rebuild the original file.

Repeated Tags Become Lists Everywhere

XML has no list type. Instead, it simply repeats an element: three tag elements in a row mean a list of three. The converter turns such repeats into a JSON array.

However, a naive converter creates a trap here. A book with two tags gets a list, while a book with one tag gets a plain string, so the JSON changes shape from record to record. This tool spots the pattern and makes the single tag a one-item list as well. As a result, code that loops over the tags works on every book.

XML to JSON With Numbers and Booleans Kept

Everything in XML is text, even a price. By default the converter keeps it that way, which is the safest choice for IDs and codes. Turn on number detection when you want real JSON numbers and booleans instead.

Type detection turns 44.95 into a number and true into a boolean. Values with a leading zero, such as a zip code, still stay text, because turning them into numbers would change them.

Feeds, Sitemaps and SOAP Replies

An RSS feed is a channel element with a list of item elements inside. After conversion, you get a channel object with an item list, so each post has its title, link and date side by side. A sitemap works the same way: every url element becomes one entry, with its loc and lastmod as keys.

SOAP replies from older payment and shipping APIs wrap the useful data in several envelope layers. The converter keeps every layer, including namespace prefixes such as soap:Body. That way you can see the full structure first, and then pick the part your code needs.

Namespaces never collide, because the prefix stays part of the key. As a result, g:price from a product feed and price from the main document remain two separate keys.

Safe With Untrusted XML

Some XML files declare their own entities in a DOCTYPE. A hostile file can use them to pull in local files or to expand into millions of characters. Security teams know this as the XXE attack described by OWASP.

This converter never expands those entities, and the checks table tells you when a file tried to declare them. Since the reading also happens inside your browser, the file cannot reach anything on this site.

What Happens When the XML Breaks the Rules

A missing closing tag, an unescaped ampersand or two root elements make XML invalid. The converter stops, shows the reason, and names the line and column. Then Show me where puts the cursor right on it, so the fix takes seconds.

XML to JSON in the Browser, One Step at a Time

Developers use the conversion to test an old SOAP or payment API from modern code. Marketers use it to read a product feed or a sitemap without opening an XML editor. Analysts turn a government export into JSON, then load it into a notebook or a dashboard.

The rules for well-formed XML live in the W3C XML specification, and this reader follows them strictly. Once you have the JSON, our JSON formatter can indent it, sort its keys or squeeze it onto one line.