JSON ↔ XML

Some payments, government, or legacy systems still emit XML, while frontend and Node services want JSON.

JSON → XML builds tags from nesting. XML → JSON folds elements into objects so you can Diff or generate a Schema.

Attributes, repeated children, and namespaces differ across conventions. Check key fields after convert.

Conversion stays local. Payloads with IDs or order numbers can be pasted as-is.

Why arrays sometimes disappear

A single same-name child in XML is often folded into an object, not an array. If the other side sometimes sends one and sometimes many, treat it as an array in the worst case.

Attributes and text nodes

Attributes such as id and currency are folded into the object. When conventions disagree, read the convert result before you write a parser. Don't assume attributes stay on the tag.

How to use it

Paste JSON or XML. Confirm it is a complete document, not a log fragment.
Choose JSON → XML or XML → JSON.
Check whether repeated nodes became arrays when the count changes.
Copy the result. Format or generate a Schema on the JSON side.
When there are many namespaces, watch only the tags you actually use.

When to use it

Turn a payment-callback XML into JSON you can test against.
Write fixtures as JSON, then convert back to XML for a legacy API.
Unify two payloads as JSON, then Diff.
Infer a JSON Schema from an XML sample.

Keep in mind

This is not a full XML Schema / SOAP suite.
Check rare nodes such as CDATA and processing instructions by hand.
The payload is not uploaded.

FAQ

How are XML attributes handled?

They are folded into objects by common rules. Recheck unusual attribute prefixes or namespaces.

Can arrays be lost?

Same-name sibling nodes usually become an array. A single child may become an object.

How is this different from YAML convert?

YAML is closer to config files. XML is closer to legacy API payloads.

Is the payload uploaded?

No.

Are the declaration and encoding kept?

The focus is structure. Don't treat the XML declaration or encoding header as a lossless round-trip.

Can it convert a SOAP envelope?

As ordinary XML, yes. You still split Header / Body business nodes yourself.

What if a tag name is invalid?

If a JSON key cannot be a tag name, convert may rewrite or fail. Rename the key first.

When should I use CSV instead?

Use CSV for tabular data. Use XML / JSON when you have nesting and attributes.