XML to JSON — Legacy In. Modern API Out.

Q: Repeated elements?

Auto-detected as arrays. a b becomes {"items": {"item": ["a", "b"]}}.

What it actually does

MAP

Convention-aware

Attributes prefix with @. Text content keys as #text. Repeated children become arrays. Configurable.

EMIT

Pretty or compact JSON

Indented for readability. Minified for the wire. Both produce valid JSON.

BATCH

Folder in

Drop multiple XML files. Each becomes its own JSON. Free tier has no batch limit.

How it works

Open morph.cool — browser only.
Drop the .xml file or paste the content.
Pick JSON as the output. Tune attribute and array handling.
The .json downloads. Valid, well-shaped, ready for the API.
The XML stays where it was. Nothing uploaded.

0Upload

∞Batch limit

1-clickExport

Why people leave the upload-and-queue tools

Most enterprise integrations end with the same problem: the legacy system speaks XML and the new system speaks JSON. Online converters queue. CLI tools require install. Morph runs fast-xml-parser via WebAssembly in your tab — attribute prefix configurable, array detection automatic, text content handling explicit.

Frequently asked

How are XML attributes represented in JSON?

Default convention: prefix with @. So becomes {"@id": "7"}. Configurable to other conventions.

Repeated elements?

Auto-detected as arrays. ab becomes {"items": {"item": ["a", "b"]}}.

Mixed content (text + child elements)?

Text content keyed as #text. Mixed content preserved as ordered arrays where needed.

Pretty-printed or minified?

Both. Default is pretty (2-space indent). Toggle for minified.

Can I batch?

Yes. Drop a folder of XMLs, get JSONs. Free tier has no batch limit.

Is there a free tier?

Yes. Everything that runs on your device is free with no cap. AI and server work is paid in credits, about a cent each.

XML to JSON XML in. JSON out.

XML walked locally