XML formatter & converter

XML formatter & XML ⇄ JSON — free

Pretty-print, minify and validate XML with exact line & column errors, then convert XML to JSON and back with your choice of mapping convention — and an honest account of what each conversion drops. All on your device; external entities are never processed.

or paste / drop a file

Mode

Indent

Keep short text on one line

XML input

XML output

Formatted and converted on your device — nothing is uploaded. External entities and DOCTYPE definitions are never processed, so hostile XML (e.g. billion-laughs payloads) stays inert.

There is no canonical XML ⇄ JSON mappingwhy this tool asks you to choose

XML has things JSON simply does not: attributes, comments, CDATA sections, processing instructions, namespaces, node order, and mixed text-and-element content. Every converter must choose what to keep, what to rename and what to throw away — which is why several competing conventions exist, and why this tool tells you exactly what each one loses on your document.

Compact (fxp default) — the fast-xml-parser mapping: attributes become @_name keys, text becomes plain values, repeated elements become arrays. Readable and popular; loses order and comments.
BadgerFish — attributes become @name keys and element text moves into a $ key, so text and attributes never collide. Verbose but unambiguous.
Parker — elements only: attributes are dropped entirely and the root element is absorbed. The cleanest JSON to consume, and the lossiest — this tool counts every attribute it discards.
Round-trip faithful — an ordered node list that keeps comments, CDATA and processing instructions. Not pleasant to read, but it is the only convention from which the original XML can be rebuilt.

Rule of thumb: converting data (configs, API payloads, exports) — use Compact or Parker. Converting a document you need to reproduce — use Round-trip faithful.