XML to JSON

XML distinguishes attributes from child elements and JSON does not, so attributes are mapped into keys. Comments and namespaces are dropped.

Runs in your browser // nothing is uploaded

Loading converter

What survives the conversion

Derived from what each format is able to store, not from what the conversion promises.

Kept

Nested structure
Data types, which XML could not store

Lost

Comments
Attributes
Namespaces

Settings used

Parsed with the browser's own XML parser, then mapped to a JSON object tree.

When not to convert

Not for a document where attribute versus element ordering carries meaning, such as SOAP or XSLT.

About these formats

Data

What is a JSON file?

JSON is a lightweight text format for structured data, standardised as ECMA-404. It supports objects, arrays, strings, numbers, booleans and null, and nothing else. That deliberate minimalism is why it replaced XML as the default format for web APIs and configuration.

Read the format guide

Common questions

Does converting XML to JSON lose anything?

Yes. Comments, Attributes, Namespaces cannot be carried into JSON and are dropped. XML distinguishes attributes from child elements and JSON does not, so attributes are mapped into keys. Comments and namespaces are dropped.

Are my files uploaded when I convert XML to JSON?

No. The conversion runs in your browser tab, so the file is never transmitted and the page works offline once loaded.

What settings does Filoven use for XML to JSON?

Parsed with the browser's own XML parser, then mapped to a JSON object tree.

When should I not convert XML to JSON?

Not for a document where attribute versus element ordering carries meaning, such as SOAP or XSLT.