Delimiter.live
6 tools

XML Tools

XML tools pretty-print and validate XML documents and convert them to and from JSON and CSV. Formatting indents nested elements so a compact document becomes readable; validation reports whether the document is well-formed and where it breaks. Parsing happens in your browser with external entity resolution disabled, so hostile documents cannot reach out to other systems.

XML remains the interchange format for SOAP services, RSS and Atom feeds, sitemaps, Office document internals and a great many enterprise integrations. Most of the work it creates is unglamorous: making a single-line document readable, finding the unclosed tag, or turning a feed into JSON something modern can consume.

A note on safety, because it matters here more than with other formats. XML parsers that resolve external entities can be tricked into reading local files or making network requests — the XXE class of vulnerability. The tools here parse with entity resolution disabled.

Read and check

2 tools

Make a document readable and confirm it is well-formed.

Convert

4 tools

Move between XML and the formats modern tooling prefers.

What people use these for

  • Pretty-print a single-line SOAP response so you can find the fault element.
  • Check that a hand-edited sitemap or RSS feed is still well-formed before publishing.
  • Convert an XML API response to JSON so a JavaScript client can consume it.
  • Turn an XML product feed into CSV for review in a spreadsheet.
  • Generate XML from a CSV export for a legacy integration that accepts nothing else.

XML Tools: frequently asked questions

Does the validator check my document against a schema?
No. It checks that the document is well-formed — tags balanced and properly nested, attributes quoted, one root element. Validating against an XSD or DTD is a separate step that requires the schema itself, which these tools do not fetch.
Are external entities processed?
No, deliberately. External entity resolution is disabled, which prevents the XXE attacks that turn an XML parser into a way to read local files or make outbound requests. A document relying on external entities will not expand them here.
How are XML attributes handled when converting to JSON?
Attributes are preserved rather than dropped, prefixed to distinguish them from child elements. This is necessary because JSON has no native concept of an attribute, so a lossless conversion has to encode the distinction somehow.
Why does my XML fail with an "undefined entity" error?
XML predefines only five entities: < > & " and '. HTML entities such as   are not valid in plain XML unless a DTD declares them. Replace them with numeric character references like   instead.
All tools →

Last reviewed 7 August 2026.