XML Formatter Online — Pretty Print and Minify

Format the document first: an unclosed or stray tag breaks the indentation ladder immediately, and the line that jumped to the wrong depth points at the fault. Parsing stops at the first error, so fix one and format again. Usual suspects are a bare ampersand in a product name, a quote inside an attribute, and a file truncated during export.

Only whitespace and line breaks between nodes change; values, attributes and element order are preserved. For formats where whitespace inside a text node is significant, though, the added indentation is real content — send the recipient the minified version and keep the pretty one for reading.

The two buttons differ here, and it is worth knowing in advance. «Minify» keeps CDATA sections and comments as they were. «Format» rebuilds the document node by node: text inside CDATA stays text, but the CDATA wrapper is gone and the < and & characters in it come out escaped; comments do not reach the formatted output at all. So if you are editing a feed with HTML inside CDATA, use the formatted view for reading and send the recipient the original or the minified version.

Snippets and files of a few thousand lines format quickly. A full marketplace feed weighing tens of megabytes does not belong in a textarea: the whole string lives in the tab's memory and the browser starts to stall. Use a desktop editor for that, and bring a single branch of the document here.

Indentation is extra bytes on every request. A SOAP body, a transfer over a poor connection or long-term storage are all cheaper compact, and a machine does not need readability. The usual rhythm is: fold before sending, expand when you need to understand a response.

Nobody but you. Parsing and printing happen in the page script inside your open tab, and no request carrying the file is made in this flow. That makes it fine to tidy up an export holding prices, stock levels or order details without handing it to a third-party service.