JSON to XML for quick interop — not a full enterprise mapper

Some legacy hops still want XML. Paste JSON; get a deterministic element tree (arrays → repeated child tags). Call out naming rules for keys that aren’t valid XML names.

chars: 30

Input

Output

When to use

Prototyping against an older XML endpoint or teaching element shape from a JSON sample.

Examples

Input

{"user":{"id":1,"name":"Ada"}}

Output

<user><id>1</id><name>Ada</name></user>

How it works

Walks objects into elements; arrays become repeated nodes. Invalid name characters are replaced/prefixed. Root wrapper follows the tool’s convention.

Common pitfalls

Attributes vs child elements are a convention — check output.
JSON numbers/booleans become text content.
Not a full enterprise XML binder.

How this differs

JSON→XML here; XML→JSON to inspect SOAP-ish samples as objects.

FAQ

Is there one true JSON↔XML mapping?

No — we pick a simple convention and label it.

Attributes vs child elements?

Prefer child elements unless a toggle exists.

Uploaded?

No.

Reverse?

XML to JSON.

Runs in your browser. Nothing is uploaded. Not a security product —hashes and JWT decode are for debugging, not password storage or auth advice.