Format XML and check well-formedness

Formatting places structural children on separate lines with two spaces per level. For example, <items><item id="1"/><item id="2"/></items> becomes a readable list of two item elements. Minifying removes whitespace-only text between structural child nodes. Comments and processing instructions remain. This is a parser-based rewrite: quote style, empty-element syntax, namespace declarations and entity spelling may change. It is not a byte-preserving editor or XML canonicalizer.

Text mixed with markup, such as <p>Hello <b>world</b>!</p>, is serialized without reindenting its subtree. The same applies to subtrees marked xml:space="preserve" and elements containing CDATA. Text-only elements, including whitespace-only values, are kept. In other structural elements, whitespace-only nodes are treated as indentation. XML without a schema cannot prove that whitespace is insignificant; review the result before replacing a whitespace-sensitive document.

The native browser parser checks XML syntax, including matching tags and quoted attributes. It does not validate XSD, DTD rules, application requirements or document meaning. Error wording and locations vary by browser, so this page reports a consistent syntax error instead of claiming a portable line and column. DTD and entity declarations are rejected before parsing; no external resource is fetched by the formatter. XML is shown as text and is never inserted into the page as active markup.

XML parsing runs only when you select Process XML. Input is limited to 20,000 characters so native parsing stays bounded on phones, with additional node, depth and UTF-8 output limits. The preview shows up to 12,000 characters; Copy and Download XML include the complete result. Downloads use UTF-8, and any XML encoding declaration is updated accordingly. Editing the input or mode clears the previous result.