XML Minify: Compress and Validate XML Instantly

How to use the xml minify

1. Paste or type your XML into the input area.
2. Check Keep processing instructions if you need to preserve <?xml ...?> declarations.
3. The tool automatically validates and compresses the XML as you type.
4. If an error is found, the message shows the exact line and column.
5. Copy the compact result from the output box.

How the xml minify process works

The tool uses a hand-written tokenizer that reads the input character by character, tracking line and column numbers for error reporting. It recognizes elements, attributes, text nodes, CDATA sections, comments, processing instructions and entity references.

During the xml minify pass, comments are discarded entirely. Processing instructions are kept only when the option is enabled. Whitespace-only text between tags is dropped. In other text nodes outside CDATA, runs of whitespace collapse to a single space and the edges are trimmed, except that one space is kept next to a neighbouring element so mixed content such as mixed <b>bold</b> tail keeps its word breaks. Attribute values inside tags are preserved exactly as written, including their internal spacing.

A stack tracks open element names. When a closing tag is encountered, its name must match the top of the stack. If the stack is not empty at the end of the input, or if a mismatch occurs, the tokenizer stops and reports the position of the error.

What is preserved and what is removed

Understanding what changes during minification helps avoid surprises. Here is a summary of how each XML construct is handled:

Supported entities and references

The tokenizer validates five predefined XML entities: &, <, >, " and '. Numeric character references in decimal (A) and hexadecimal (A) form are also accepted. Any other named entity reference triggers a validation error because resolving it would require an external DTD.

This tool does not process DOCTYPE declarations or resolve external entities. If your XML relies on a DTD for entity definitions, you should resolve those entities before you xml minify the document. For inspecting raw XML structure before or after compression, you can use an xml viewer.

Practical use cases

Minifying XML reduces file size by removing bytes that carry no semantic meaning. This matters most in two scenarios: network transfer and storage. When an API sends large XML payloads, stripping comments and whitespace can reduce the byte count by ten to thirty percent depending on how heavily the original was formatted.

Configuration files that are read by machines rather than humans benefit from minification too. A build system that packages XML resources into an application can run them through a minifier to shrink the final bundle. If you later need to convert that compact XML into another format, tools exist to transform it to CSV, YAML or HTML.

Common mistakes and edge cases

Whitespace handling is the most frequent source of confusion. In mixed content, where text and child elements alternate, collapsing whitespace can change rendering in formats like XHTML. The minifier collapses runs of whitespace inside text to one space, which is correct for data-oriented XML but can still alter documents where whitespace is significant (for example elements with xml:space="preserve", which this tool does not honour).

Another edge case involves attribute ordering. XML treats attribute order as insignificant, and this tool preserves whatever order appears in the source. Self-closing tags like <br/> remain self-closing rather than being expanded to <br></br>.

If you need to compare a minified file against a formatted original, structural comparison is more reliable than string comparison. An xml diff tool handles this by parsing both documents first.

Worked examples