Free HTML Minifier

WordPress

1. For one-off custom HTML in posts: paste in Code-view of the editor, minify, paste back in.
2. For sitewide HTML minification, install Autoptimize or W3 Total Cache and enable HTML minification in the plugin settings.
3. Verify with PageSpeed Insights or curl -s URL | wc -c before and after.

Next.js

1. Next.js's production build (next build) auto-minifies HTML output via terser. Confirm by inspecting .next/server/pages/*.html files.
2. For static export (next export), minification is included.
3. Use this tool only for one-off snippets you paste into next/head or component-level HTML.

Webflow

1. Webflow auto-minifies published HTML. Disable in site settings only if you have a specific debugging reason.
2. For custom-code blocks (header/footer/page-level): minify locally before pasting to keep blocks compact and reviewable.
3. For embed widgets: paste minified version to reduce clutter in Designer.

Ghost

1. Ghost's production templates serve auto-minified HTML.
2. For custom HTML cards in posts: use this tool to minify before pasting if the snippet is large or comment-heavy.
3. For theme development: enable Ghost's production mode (NODE_ENV=production) to test minified output locally.

Email (Mailchimp, SendGrid, Klaviyo)

1. Email HTML often hits the 100-200KB cap because of inline styles and copy-pasted content.
2. Minify before importing the template. Verify nothing visually breaks by sending a test email.
3. Some email clients (Outlook, Gmail) handle whitespace differently; spot-check on at least 3 clients.

Output looks the same as input

Cause: Your HTML had little whitespace to begin with, or it was already minified.

Fix: Compare the byte count in the stats panel. If reduced by under 5%, your input was already nearly optimal — further minification has diminishing returns.

JavaScript inside <script> tag breaks after minification

Cause: You used a tool that aggressively minifies inline JS without preserving its semantics.

Fix: This tool preserves inline script content. If you used a different minifier and the JS broke, run JS through Terser separately and re-embed the already-minified script before HTML minification.

Templating tags ({{ }}, {% %}) get garbled

Cause: Aggressive minification stripped whitespace around template delimiters.

Fix: Render templates to plain HTML first (build step), then minify. Or use a templating-aware minifier (the htmlnano-with-template-options plugin).

Output paste into CMS shows the raw < and > characters

Cause: CMS encoded HTML on paste, treating it as plain text instead of code.

Fix: Switch the CMS editor to "Code" mode or "HTML" tab before pasting. Most CMSes have a toolbar toggle. Pasting into a Visual editor encodes HTML by design.

IE-conditional comments disappeared

Cause: Standard minification strips all comments including conditional ones.

Fix: For IE 8/9 support (rarely needed in 2026), do not minify the section containing those comments. Most teams have dropped IE support entirely.

Tool seems to hang on large input

Cause: Input over 10MB pushes browser memory and clipboard.

Fix: Split into chunks of 1-2MB or use a CLI minifier (html-minifier-terser) for very large files. The browser-based tool is sized for typical HTML pages.

Stats panel shows 0% savings

Cause: Input HTML had no whitespace, comments, or redundancy to remove.

Fix: No action needed — your HTML was already minimal. Confirm by comparing original and output side by side; they should be identical.

Minified HTML breaks on a specific browser

Cause: Minifier removed a whitespace-sensitive feature (e.g., between inline elements where whitespace creates visual gaps).

Fix: Add the affected gap back as &nbsp; or use CSS spacing instead of relying on text whitespace. Inline elements (<span>, <a>) treat whitespace as a visible space; minification removes it.