JSON to XML

JSON arrays have no direct XML equivalent, so each item becomes a repeated element. Legacy and enterprise APIs are the reason this conversion still exists.

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
Comments, which JSON could not store
Attributes, which JSON could not store
Namespaces, which JSON could not store

Lost

Data types

Settings used

Serialised to XML elements with the object keys as tag names.

When not to convert

Not unless the receiving system demands XML. It is the larger and slower format.

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 JSON to XML lose anything?

Yes. Data types cannot be carried into XML and is dropped. JSON arrays have no direct XML equivalent, so each item becomes a repeated element. Legacy and enterprise APIs are the reason this conversion still exists.

Are my files uploaded when I convert JSON to XML?

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 JSON to XML?

Serialised to XML elements with the object keys as tag names.

When should I not convert JSON to XML?

Not unless the receiving system demands XML. It is the larger and slower format.