JSON to XML
Choose the root element and XML formatting for a parsed JSON value.
Runs in your browser. Nothing is uploaded.
Convert structured data into XML
JSON to XML parses a JSON value and serializes its structure as XML. Objects become nested elements, arrays become repeated child values according to the converter mapping, and scalar values become XML text. The page performs a data conversion so quoted JSON syntax, escaping, and nesting are handled by the engine instead of a string replacement.
Paste the sample, provide your own object, or drop a JSON file into the input area. The sample demonstrates a root element with name and private children. Download the result as converted.xml, or use XML to JSON for the reverse direction.
XML has a schema boundary
JSON and XML do not have identical data models. JSON has native arrays, booleans, numbers, and null, while XML has elements, attributes, text, namespaces, and an application-defined schema. A converter must choose a mapping for arrays and scalar values. The result can be well-formed XML and still need adjustments for SOAP, RSS, a vendor feed, or another strict contract.
Review element names when JSON keys contain spaces, punctuation, or a name that is not allowed by XML. Also check how the receiving system expects repeated elements, empty values, and root names. The converter does not invent a business schema or remove fields that look private.
Escaping and type fidelity
XML text must escape characters such as ampersands and angle brackets when they appear as data. The engine handles XML escaping while it writes the output, so a string containing markup is not silently treated as an element. Inspect the result when text includes quotes, Unicode, or line breaks.
XML commonly carries values as text. A number or boolean in the source may therefore need schema-aware interpretation after conversion. If the receiving application requires explicit type markers or attributes, add them according to that application's documentation.
Check before sending
Validate the generated XML with the same parser or schema used by the destination. Conversion, file reading, copying, and downloading happen in your browser, and nothing is uploaded. For a YAML representation of the same JSON data, see JSON to YAML. For a formatted view of the source, open JSON Formatter.
FAQ
Can I convert private JSON to XML without uploading it?
The JSON is parsed and converted to XML in your browser, without a conversion request. The input is never uploaded, and TheDevTab never receives it.
What JSON can be converted to XML?
Objects, arrays, strings, finite numbers, booleans, and null values can be serialized. The default root is root, while Use top-level key as root uses the only key of a one-key object as the root element.
How are JSON keys turned into XML names?
Object keys become element names, with invalid first characters or name characters replaced by underscores. Names beginning with xml are prefixed with an underscore, so inspect generated names when an external XML schema is strict.
How are arrays represented?
Nested array items are emitted as repeated elements with the same name, while a top-level array is wrapped in the selected root and its items use item elements. XML has no native array type, so the receiving schema must define the intended meaning.
How can I represent XML attributes and text?
In an object, a key beginning with @ becomes an XML attribute and #text becomes text content. Other keys become child elements, and values are escaped for XML text or attribute syntax.
Are JSON types preserved in XML?
Numbers and booleans are written as XML text, while null becomes an empty self-closing element, so XML does not retain JSON's native types. Pretty-print only changes whitespace and line breaks; it does not add type metadata.