Explorer
Tree explorer will appear here once JSON is loaded
Inspector
Select a node to inspect it
Tree explorer will appear here once JSON is loaded
Select a node to inspect it
Paste JSON and export it as XML. The document root becomes a <root> element, each object key becomes a child element named after that key, and each array element becomes a sibling <item index="0">, <item index="1"> and so on - a common, predictable convention for JSON-to-XML that doesn't require a schema to interpret.
JSON keys are not always valid XML element names - a key with a space, a symbol, or a leading digit gets sanitized (invalid characters become an underscore) while the original key is preserved in a name attribute, so no information is lost even when the element name itself had to change.
Text content is XML-escaped automatically (<, >, and & are converted to their entity equivalents), so values containing markup-like characters convert safely without producing invalid XML.
This mirrors the convention used by most JSON-to-XML tools and libraries, rather than inventing a custom schema - the output is plain, dependency-free XML with a standard declaration header, so it can be fed straight into an XML parser, an XSLT pipeline, or any tool that expects well-formed markup without first needing a schema definition to make sense of it.
The whole document converts in one pass, entirely client-side, so pasting a large nested config or API response and downloading the XML equivalent happens instantly, without a round trip to any server.