When to use it
Useful for working with legacy APIs that still respond in XML (SOAP, RSS feeds, some webhooks), converting to the JSON that most modern languages handle more easily — and the other way around.
Convention used
There's no single universal standard for XML↔JSON conversion. This tool uses the most common convention: attributes become keys prefixed with @ (e.g. @id), the text of a childless element becomes a plain string, and repeated elements with the same name become an array.
Frequently asked questions
Why does the JSON need a single root key to convert to XML?
Because an XML document always has exactly one root element — that root key's name becomes the generated XML's main tag.
Are XML namespaces supported?
Namespaces are treated as part of the tag/attribute name, with no special handling — for advanced cases with complex namespaces, the result may need manual adjustment.