What counts as an empty attribute?

Any attribute whose value is an empty pair of quotes — like class="" or value='' — is removed when the switch is on. Boolean attributes like disabled (no value) are never touched, and non-empty values are preserved.

How does whitespace collapse work between tags?

Text nodes have runs of whitespace reduced to a single space, leading space after a tag is trimmed, and trailing space before the next tag is trimmed. The result is tags sitting directly against each other, with single spaces only where text needs them.

Are void elements handled specially?

Yes. Elements like meta, img, input, br, and link are recognized as void, so the minifier never looks for a close tag and never enters raw-text mode for them. Their opening tags are simply passed through after empty-attribute removal.

What happens to the doctype?

Declarations and processing instructions starting with <! or <? are emitted exactly as they appear, with no whitespace or attribute changes. The doctype therefore always stays at the top of the output.

Could minification change how a page renders?

In raw-text elements, never. Elsewhere, collapsing whitespace can change rendered spacing when text nodes sit between inline elements — browsers normally collapse such whitespace anyway, but test pages that rely on significant spaces.

Developer

HTML Minifier

Minify HTML by removing comments, whitespace, and empty attributes.

htmlminifycompressoptimizemarkup

Loading tool…

Recommended tools

Cloudflare

Free CDN, DNS, and edge hosting for developers.

Namecheap

Affordable domains and SSL certificates.

Affiliate links — we may earn a commission if you sign up.

About the HTML Minifier

The HTML Minifier compresses markup without breaking its meaning, and the key is what it refuses to touch. Content inside pre, code, textarea, script, and style elements is treated as raw text and preserved verbatim, so indented code samples, inline JavaScript, and CSS blocks keep their exact formatting while everything around them collapses. Three switches control the output: Strip comments removes  blocks, Collapse whitespace squeezes text nodes to single spaces and trims the seams around tags, and Remove empty attributes deletes pairs like class="" or value="" from opening tags. Void elements such as meta, input, img, and br are recognized as self-closing so they never trigger raw-text mode, and the doctype is passed through untouched. The bundled sample is a full page — header, style block, pre-formatted function, code snippet, an input with an empty value attribute, and an inline script — so loading it demonstrates every feature at once. Byte-size stats quantify the savings, and the result downloads as page.min.html.

Hand-written guide

Examples

Input

<div class="card">
  <!-- promo banner -->
  <h1>Welcome</h1>
  <p class="">Build tools that ship.</p>
</div>

Output

<div class="card"><h1>Welcome</h1><p>Build tools that ship.</p></div>

Note: The comment disappears, whitespace between tags collapses, and the empty class="" attribute is stripped from the paragraph.

Input

<pre>
function greet(name) {
  return "Hi, " + name;
}
</pre>

Output

<pre>
function greet(name) {
  return "Hi, " + name;
}
</pre>

Note: Inside pre the content is raw text — indentation and line breaks are preserved verbatim, exactly as a browser would render it.

Input

<input type="text" value="" placeholder="Search" disabled />

Output

<input type="text" placeholder="Search" disabled />

Note: The empty value="" attribute is removed while the rest of the void element — including its self-closing slash — passes through.

How to use

1
Paste your markup into the HTML input textarea, or click Load sample.
2
Set the switches: Strip comments, Collapse whitespace, Remove empty attributes.
3
Watch the Minified HTML result box update live.
4
Read the Original, Minified, Saved, and Savings stats to quantify the result.
5
Download the output as page.min.html.

Common use cases

Shrinking a static page before inlining it into an email or embed.
Comparing markup weight before and after removing comments in templates.
Cleaning generated HTML from WYSIWYG editors that emit empty attributes.
Preparing compact partials for a server that serves cached fragments.
Quantifying how much of a page is whitespace before a CMS migration.
Producing tidy snippets for documentation without manual clean-up.

Best practices

Trust the raw-text list: pre, code, textarea, script, and style content is never collapsed — do not expect savings there.
Remove empty attributes only when you are sure no framework reads their presence (some treat empty vs absent differently).
Keep comments that carry licenses or conditional logic; strip the rest.
Verify script content survives intact — the tool preserves it verbatim, including spaces that matter inside strings.
Minify templates before caching, not the source files you still edit.
Spot-check text nodes between inline elements, since collapsed spaces can change spacing in rendered prose.

Tips

Load the sample page first — it contains a pre block, a style block, a script, and an empty attribute in one file.
Watch the Saved stat jump when stripping large comment blocks from templates.
Toggle Remove empty attributes off when minifying markup for frameworks that detect attribute presence.
Download page.min.html and diff it against the source to review exactly what changed.

Frequently asked questions

Those elements hold raw text in HTML: whitespace inside pre is rendered literally, and collapsing spaces inside script or style strings would change behavior. The minifier copies their content verbatim until the matching close tag, so meaning is preserved.

Explore more developer tools

Browse the full collection of developer tools on the hub, or jump back to all categories.

All Developer tools All categories