XML to JSON

THE PRACTICAL GUIDE · NORMANDIN SYSTEMS

Get more from XML to JSON

XML to JSON converts XML to JSON. XML element trees can be represented as JSON objects, with conventions for repeated elements, attributes, and text content. Two XML documents can use namespaces or mixed content that cannot be represented faithfully by a simplistic object mapping. Review the actual output conventions. Include a repeated element and an attribute in a test sample if either occurs in production documents. Use the worked example to understand what a successful result looks like, then compare it with a small sample of your own input. Keep the original available until you have checked the output in its destination. Conversion establishes a representation; it does not establish that the underlying information is correct or that the receiving application accepts every supported feature.

Guide updated October 13, 2026

How to use this tool

1. Enter or load XML using the input controls. Begin with the worked example or a small sample for which you know the expected result.
2. Review any available conversion options, then inspect the JSON result. Resolve a reported parse error at its source before attempting to reuse the output.
3. Check the example below against your own data. Include a repeated element and an attribute in a test sample if either occurs in production documents.
4. Copy or save the resulting JSON content using the controls provided, then validate it in the application or parser that will actually consume it.

SEE IT IN PRACTICE

A worked example

<person><name>Ada</name></person>

{"person":{"name":"Ada"}} (mapping illustration)

A simple element hierarchy maps to nested properties. Attributes and repeated nodes require additional mapping rules.

Attributes, namespaces, and mixed text

An element can carry attributes, text, and child elements simultaneously. A simple JSON mapping needs a convention to keep those concepts distinct. Namespaces add another identity layer beyond the visible prefix spelling. Inspect these features before treating the result as a lossless conversion, particularly for document-oriented XML where text is interleaved with inline elements rather than organized as a simple data table.

Repeated elements and single elements

An XML response may contain one item today and several tomorrow. Some mapping conventions produce a scalar or object for the first case and an array for the second, which can surprise a JSON consumer. Test both cases. Also inspect attributes and text nodes separately: an attribute called id and a child element called id need an unambiguous representation if they can occur on the same element.

When this tool is useful

• Prepare JSON samples from XML responses while retaining a separate copy of the source.
• Use a small example to troubleshoot attribute and text-node mapping and identify a representation mismatch.
• Create structured fixtures for integration work without manually rewriting every field or symbol.

Tips for a better result

• Two XML documents can use namespaces or mixed content that cannot be represented faithfully by a simplistic object mapping. Review the actual output conventions.
• Include a repeated element and an attribute in a test sample if either occurs in production documents.
• After changing formats, compare meaningful values rather than whitespace alone. Read the JSON output with its intended parser when exact types or escaping matter.

Frequently asked questions