JSON to XML Converter

If your JSON is an object with exactly one key, that key becomes the root element. The sample does this, and its @id key becomes an attribute:

Anything else gets wrapped in an element called root. That includes an object with two or more keys, and a bare string or number:

Every result starts with an XML declaration naming UTF-8 and is indented with two spaces.

An array doesn't get its own wrapper. Each item is written as a separate element carrying the array's key name, which is the usual XML way to show a list:

That rule causes trouble at the top level. A JSON array, or a single key that holds an array, produces several root elements in a row, and an XML document may only have one:

Wrap the list in two keys, one for the container and one for each item, such as {"people":{"person":[{"name":"Ada"},{"name":"Alan"}]}}. That gives one people root holding two person elements. Nested arrays are flattened the same way: [[1,2],[3]] under one key becomes three sibling elements.

Ampersands, angle brackets and double quotes in values are escaped. An apostrophe is left as it is, which is fine in element text. null and empty objects become self-closing tags:

An empty string gives an open and close tag with nothing between them, and an empty array produces no element at all, only a blank line. Numbers and booleans are written as plain text, with no type information, so 36 and "36" give identical XML.

JSON keys can be any string, but XML element names can't start with a digit or contain spaces. The converter copies keys as they are, so these come out broken:

A parser will reject that document. Rename such keys first, for example first_name and twoFactor. The #text key produced by our XML to JSON converter has the same problem: it is written as an element, not as the text content, so move that value into a normal key before converting back.