⌘ K
html · whitespace · comments · live

Minify HTML to compact markup

Removes comments, collapses inter-tag whitespace, and squashes runs of spaces. Conditional IE comments are preserved. Runs locally.

HTML Minifier
Input
79 B
5 lines
Output
51 B
1 lines
Status
ready
live
Ratio
0.65×
out/in
input · html
output · minified html
<div class="card"><h1> Title </h1><p>Body</p></div>
Quick Start

How to minify HTML

Strips HTML comments (except IE conditional comments), collapses whitespace between tags, and squashes runs of spaces inside text nodes.

  1. 01

    Paste HTML

    Authored markup, server-rendered output, or a copy-paste from devtools.

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

    htmlPrettierASTstandalonelazy
    input · sourceraw · AST
    <div>  Hi  </div>
    loaded · parsedAST · ready
  2. 02

    Comments stripped

    <!-- ... --> blocks are removed. <!--[if IE]> conditional comments are preserved.

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

    stripindentprint-widthmemoisedlive
    step · optionscomments · live
    <!-- x --> → ""
    options applied · livelive
  3. 03

    Whitespace squashed

    Whitespace between tags collapses to nothing; runs of spaces inside text shrink to one.

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

    compactidempotentdeterministicdiff-cleanstable
    step · formattedwhitespace · ready
    <div>Hi</div>
    formatted · liveidempotent
  4. 04

    Copy or download

    One-line .html ready for a bundle artefact or email template.

    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 toolsHTML FormatterCSS MinifierJS MinifierXML MinifierCSS FormatterJS Formatter
Use Cases

When to minify HTML

Email templates, embedded snippets, static pages.

Email templates

Minify transactional HTML for delivery providers. 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

Embedded snippets

Drop HTML into JSON payloads or iframes. 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

Static pages

Trim a one-off landing page to save bytes. 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

Build comparison

Compare your build's output against this baseline. 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

Quick share

Paste compact HTML into chat or a gist. 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

Size budget

Estimate the bytes you'll save by minifying. 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

Whitespace between block-level tags is safe to collapse; whitespace inside <pre> may behave unexpectedly — check the result.
No — <style> and <script> contents are not minified. Use the CSS / JS minifier first.
Yes — <!--[if IE]> ... <![endif]--> blocks are preserved for legacy IE.
No. Attribute names, values, and order are unchanged.
No — the minifier 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!