xml-minifier
An XML minifier removes the whitespace and comments that aid human readability but waste bandwidth and storage in production XML — emitting a single compact line that parsers consume identically while shrinking documents by 20-60%. The ZTools XML Minifier preserves the meaningful whitespace inside <pre>-style elements (or any element with xml:space="preserve"), optionally retains comments for legal/copyright headers, never breaks well-formedness, handles documents up to several megabytes, and reports the before/after size difference so users can quantify the gain.
Use cases
Reducing payload size for SOAP/REST APIs
A formatted 100KB SOAP request shrinks to 60KB minified. Faster transfer, less bandwidth cost. The receiving service parses the same data either way.
Production deployment of XML configuration
Authoring uses pretty-printed XML for review; production embeds the minified version to save startup parse time and disk space.
Storing XML in databases or log fields
A VARCHAR(2048) DB column won't fit a verbose XML payload. Minify first; pretty-print on read for inspection.
Embedding XML inside JSON or CDATA
When XML needs to be a value in another format, minified is much friendlier — no embedded newlines requiring escapes.
How it works
- Paste your XML — Any well-formed XML, formatted or not. The minifier validates first; malformed XML produces an error.
- Choose what to remove — Whitespace between tags (default on), line breaks (on), comments (off — keep legal headers), unnecessary self-closing-tag spaces (on).
- Preserve significant whitespace — Elements with xml:space="preserve" keep their internal whitespace. Common in <pre>, <code>, and certain mixed-content elements.
- Read minified output and savings — Single-line compact XML alongside a size-saving stat ("85KB → 47KB, saved 45%").
Examples
Input: <root> <a>x</a> <b>y</b> </root>
Output: <root><a>x</a><b>y</b></root>
Input: Verbose SOAP envelope (1,200 bytes)
Output: Minified envelope (480 bytes), saving 60% bandwidth.
Input: Document with xml:space="preserve"
Output: Whitespace inside the preserved element is left alone; everything else is minified.
Frequently asked questions
Will minification change the meaning of my XML?
No, as long as the document doesn't depend on whitespace between elements. Documents with significant whitespace need xml:space="preserve" on the relevant elements; without that, parsers may treat removed whitespace as significant in mixed content.
Why are comments preserved by default?
Many XML files contain copyright or license comments at the top that legal/compliance requires you keep. The minifier defaults to preserving comments so accidental stripping doesn't cause compliance issues. Toggle off for full minification.
Is minified XML faster to parse?
Slightly — less data to scan. But the bigger win is bandwidth/storage. For parser performance, schema-driven parsing matters far more than whitespace removal.
How does this differ from XML compression?
Minification removes whitespace, leaving plain text. Compression (gzip, EXI) wraps the bytes into a smaller binary format. They're complementary — minify, then compress, for maximum savings.
Can I round-trip — minify and then re-format?
Yes — the data is identical. Use the XML Formatter to re-pretty-print minified XML for inspection or editing.
Tips
- For truly maximum savings, gzip the minified XML — combined, you often get 80-90% size reduction.
- If your data has mixed content (text inside elements that contain other elements), test minified output carefully — whitespace there can be semantically significant.
- Keep human-readable XML in source control; minify at build time. Don't commit minified files.
- For very large documents, EXI binary XML compresses better than gzipped text XML — but tooling support is narrower.
Try it now
The full xml-minifier runs in your browser at https://ztools.zaions.com/xml-minifier — no signup, no upload, no data leaves your device.
Last updated: 2026-05-05 · Author: Ahsan Mahmood · Edit this page on GitHub