Convert JSON to XML

Two main reasons: (a) integrating with legacy enterprise systems that consume XML (SOAP APIs, older ERP / CRM systems, document-centric tools); (b) feeding into XSLT-based pipelines that transform XML to other formats. JSON dominates modern web APIs; XML dominates enterprise integration. Conversion bridges the two when systems need to talk.

Objects become parent elements; keys become child element names; values become element text content. So `{user: {name: 'Alice'}}` becomes `<user><name>Alice</name></user>`. Arrays in JSON don't have a direct XML equivalent — typically each array item becomes a sibling element with the same name (`<item>a</item><item>b</item>`).

Usually yes — indented for readability. The converter produces well-formed XML with indentation matching the JSON's nesting depth. Pretty-printed XML is more human-readable but larger; for production use where size matters, post-process to minify (remove whitespace between tags).

Partially. JSON numbers, booleans, and nulls all become XML text content (XML doesn't distinguish text types). A number 42 becomes `<value>42</value>` indistinguishable from a string '42'. Type-aware downstream tools can interpret based on element name or schema; type-blind tools just see text.

The converter uses elements throughout — JSON doesn't have an attribute concept, so everything maps to elements. If your downstream XML consumer expects attributes for some fields, you'd need to post-process or pick a converter with attribute-mapping conventions (e.g., `@`-prefixed JSON keys become XML attributes).