HTML Minifier
Minify HTML online. Strip comments, whitespace, and reduce file size for faster page loads.
Paste HTML and click Minify to remove whitespace, comments, and redundant attributes. Reduces page weight and improves Core Web Vitals.
Input HTML
Minified Output
Why Minify HTML?
HTML minification removes whitespace, comments, and optional tags that browsers don't need. A typical HTML page can shrink by 15-30% after minification. That's bytes that don't travel over the network, don't get parsed, and don't slow down your page load.
Is it the biggest performance win? No, that's images, JavaScript, and CSS. But HTML minification is free performance. It costs nothing to implement, breaks nothing, and compounds with every page view. For a site with millions of visits, a 20% reduction in HTML size saves real bandwidth and money.
Paste your HTML, get a minified version. The tool strips comments, collapses whitespace, and removes unnecessary attributes while preserving the document's functionality. Your HTML will render identically, just smaller.
What Minification Removes
| Element | Before | After | Savings |
|---|---|---|---|
| Whitespace | <p> Hello </p> | <p>Hello</p> | Usually 15-25% of file size |
| Comments | <!-- Navigation --> | (removed) | Varies, can be significant |
| Empty attributes | class="" | (removed) | Small per occurrence |
| Newlines | Multiple line breaks | Collapsed to single space | 5-10% typical |
| Optional end tags | </li>, </p> | (can be removed) | Small but adds up in lists |
What this means for you: Minification is safe and reversible. If you need to debug, use the HTML Beautifier to re-format. Most build tools (Vite, webpack) can minify HTML automatically during production builds.
Performance Optimisation Beyond Minification
Enable Gzip/Brotli compression
Server-side compression reduces HTML by 60-80%. Minification + Brotli together can reduce a 100KB page to under 10KB over the wire. Most CDNs and web servers support this with one config line.
Inline critical CSS
Put above-the-fold CSS directly in <style> tags to avoid render-blocking requests. The page renders instantly while the full stylesheet loads asynchronously. This is the #1 LCP optimisation.
Defer non-critical scripts
Add defer or async to <script> tags that aren't needed for initial render. Analytics, chat widgets, and social media embeds can all load after the page is interactive.
Remove unused code
Unused CSS and JavaScript are a bigger problem than unminified HTML. A single unused 50KB JS bundle dwarfs any HTML whitespace savings. Audit with Chrome DevTools Coverage tab.
Typical HTML Page Sizes
| Page Type | Raw HTML | Minified | Minified + Gzip |
|---|---|---|---|
| Simple landing page | 15 KB | 11 KB | 3 KB |
| Blog article | 30 KB | 22 KB | 7 KB |
| E-commerce product page | 80 KB | 55 KB | 15 KB |
| Dashboard (heavy tables) | 200 KB | 140 KB | 30 KB |
| Average web page | 50 KB | 35 KB (30%) | 10 KB (80%) |
HTML is rarely the performance bottleneck, images and JavaScript are far larger. But minification is free savings with zero risk, and it's standard practice in every production build pipeline.
Related Tools
How to use this tool
Paste your HTML into the input area
Click Minify HTML to compress
Copy the result or download as a .min.html file
Common uses
- Reducing HTML file size for production deployment
- Stripping comments from HTML before going live
- Preparing HTML email templates for sending
- Optimising static HTML pages for faster load times
Share this tool
Frequently Asked Questions
What does HTML minification do?
Will minification break my page?
Is my HTML sent to a server?
Should I minify HTML for production?
What's the difference between minification and compression?
Does minification remove my CSS and JavaScript?
Can I undo minification?
How much space will I save?
Should I minify HTML or just rely on Gzip?
Does Google care about minified HTML?
What about whitespace in pre tags?
Can I minify HTML automatically in my build?
Results are for general informational purposes only and should be checked before use. They are not professional advice. See our Disclaimer and Terms of Service.