⌘ K
xml · minify · single-line · live

Minify XML documents

Removes comments, strips whitespace between tags, and collapses indentation runs so XML payloads shrink for transport. Runs locally.

XML Minifier
Input
167 B
10 lines
Output
124 B
1 lines
Status
ready
live
Ratio
0.74×
out/in
input · xml
output · minified xml
<?xml version="1.0" encoding="UTF-8"?><root><item id="1"><name>Hi</name></item><item id="2"><name>World</name></item></root>
Quick Start

How to minify XML

Three passes: kill <!-- comments -->, remove whitespace between > and <, then collapse double-spaces.

  1. 01

    Paste XML

    SOAP envelope, RSS feed, config file, SVG — anything well-formed.

    Parsing runs through Prettier’s standalone bundle (or the language-specific equivalent) loaded lazily — no parser ships until the tool is opened.

    xmlPrettierASTstandalonelazy
    input · sourceraw · AST
    <root>
  <a/>
</root>
    loaded · parsedAST · ready
  2. 02

    Comments stripped

    Every <!-- ... --> block disappears, including multi-line ones.

    Indent width, tab style, and print-width re-format through a memoised pass — switching 2 → 4 spaces never re-parses, only re-prints.

    cleanindentprint-widthmemoisedlive
    kill · options<!----> · live
    <!-- gone -->
    options applied · livelive
  3. 03

    Whitespace squashed

    Newlines and indentation between tags vanish; in-tag attribute spacing stays.

    The formatter is deterministic and idempotent: running it twice produces byte-identical output, which keeps diffs and git noise to a minimum.

    packidempotentdeterministicdiff-cleanstable
    ws · formattedtight · ready
    <a/><b/>
    formatted · liveidempotent
  4. 04

    Copy or save

    One-line XML on the clipboard or as a .xml file. Document never leaves your tab.

    Download writes a Blob with the language-appropriate extension; copy uses navigator.clipboard.writeText so the output preserves all whitespace exactly.

    exportclipboardbloblanguage MIMEclient-side
    ok · copiedready · done
    ✓ Copied
    shipped · ready to shipsuccess
Pro tips

Formatting tips that keep diffs sane

Pick one config and pin it

Inconsistent formatting causes diff churn. Commit .prettierrc / .editorconfig and enforce in CI.

Format on save

Editor integration is faster feedback than a pre-commit hook. Use both for belt-and-braces.

Idempotency matters

Running the formatter twice should produce identical output. Test this on a representative file.

Match the language community

Default to community conventions: 2 spaces for JS/CSS, 4 for Python, tabs for Go. Fights over indent are a productivity tax.

Print-width drives wrapping

80, 100, and 120 are the common targets. Wider lines parse fast but review slower side-by-side.

Don&rsquo;t mix formatters and linters

Prettier handles whitespace; ESLint handles correctness. Disable overlapping rules to avoid fight-club configs.

Related toolsXML FormatterHTML MinifierJSON MinifierSQL MinifierCSS MinifierGraphQL Minifier
Use Cases

When to minify XML

SOAP, RSS, SVG, transport efficiency.

SOAP payloads

Shrink envelope size before posting to a legacy endpoint. Idempotent: running the formatter twice produces byte-identical output, which is the foundation of a clean CI gate. Pair with a pre-commit hook so PRs arrive already formatted, focusing review on logic.

idempotent

SVG embedding

Strip whitespace from an SVG before inlining into HTML. Pairs with EditorConfig + .prettierrc for end-to-end consistency. Whitespace-only changes vanish so reviewers see real diffs, and git blame stays honest about who wrote what.

CI-ready

RSS feeds

Smaller feed = faster fetch for syndication clients. Output respects your indent width, tab style, and print-width — settings carry over for repeat runs. Switching 2-space to 4-space costs nothing in CPU but standardises an entire codebase.

diff-clean

Config bundling

Compact a plist or app config file for shipping. Format-on-save is the fastest feedback loop; CI is the safety net. Together they make inconsistent indentation a thing of the past and free up review cycles for genuine concerns.

PR-friendly

Diff comparison

Compare two XML payloads on a single line. Whitespace-only changes don't trigger downstream content-hash invalidations, so CDN cache keys and CI cache layers stay warm. Real changes get all the rebuild budget.

review-ready

URL transport

Encode a compact XML doc in a single query param. Pairs with linters (ESLint, Stylelint, pylint) that catch what formatting alone can't — bugs, unused imports, dead code. Each tool stays in its lane, and the codebase stays clean.

deterministic
FAQ

Frequently asked questions

No — purely a whitespace transform. Use an XML linter to validate well-formedness.
Whitespace inside CDATA may collapse — review output if you store significant whitespace in CDATA.
Preserved as-is: <br/> stays <br/>.
No special handling — the minifier is naive. Inspect output if your schema relies on preserved whitespace.
No — minification runs locally in your browser tab.
Suggest a tool

Something missing?

Tell us what you need. We ship the top requests every two weeks.

Sent straight to the maintainers · no account needed
47 in queue·8 shipped this month
Request queued. Thanks!