Skip to main content

    HTML Minifier

    Minify HTML online. Strip comments, whitespace, and reduce file size for faster page loads.

    Free to use. Runs in your browser.

    Paste HTML and click Minify to strip comments and collapse whitespace. Reduces page weight and improves Core Web Vitals.

    Use it to create a smaller deploy copy while keeping your readable source HTML unchanged.

    Input HTML

    Minified Output

    Why Minify HTML?

    HTML minification removes whitespace and comments 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 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 and collapses whitespace while preserving your tags, attributes, and links. For most pages the output renders identically, just smaller.

    What Minification Removes

    ElementBeforeAfterSavings
    Whitespace <p> Hello </p><p>Hello</p>Usually 15-25% of file size
    Comments<!-- Navigation -->(removed)Varies, can be significant
    NewlinesMultiple line breaksCollapsed to single space5-10% typical

    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 TypeRaw HTMLMinifiedMinified + Gzip
    Simple landing page15 KB11 KB3 KB
    Blog article30 KB22 KB7 KB
    E-commerce product page80 KB55 KB15 KB
    Dashboard (heavy tables)200 KB140 KB30 KB
    Average web page50 KB35 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.

    Worked Example: Shipping a Static HTML Page

    Priya has a static product page with hand-written HTML. The readable source is 42 KB because it has comments, indentation, and clear sections for header, features, FAQ, and footer.

    1. Keep source readable

    She keeps index.html readable in version control so future edits are easy to review.

    2. Create a deploy copy

    She pastes the HTML into the minifier and saves the output as the published file. Comments and indentation are removed from that copy only.

    3. Test whitespace-sensitive blocks

    The page has a small code example inside pre. She checks that it still displays correctly after minification.

    4. Check the network panel

    In DevTools, the minified HTML is smaller before compression and smaller again after brotli or gzip is applied by the host.

    HTML Minification Edge Cases

    pre and code blocks

    Whitespace can be meaningful inside code examples, poetry, command output, and ASCII diagrams. Test those areas after minifying a content-heavy page.

    textarea defaults

    Textarea content is visible to the user and may preserve spacing. Avoid collapsing intentional spaces inside form examples or templates.

    Email conditional comments

    Old Outlook email templates can rely on conditional comments. If you are minifying HTML email, test the output in the clients you support.

    Inline scripts and styles

    This page focuses on HTML whitespace. Minify complex inline CSS and JavaScript with tools made for those languages when size matters.

    What to Test After Minifying

    AreaCheckWhy
    LayoutHeader, nav, main content, and footer still renderA pasted partial document can lose context when reused
    LinksInternal anchors and external links still workHTML minification should not change href values
    FormsLabels, required fields, and submit buttons still behaveForms often expose subtle markup errors quickly
    Structured dataJSON-LD script blocks remain valid JSONWhitespace is safe, but broken script tags are not
    Analytics and embedsThird-party snippets still load in the browser consoleSome snippets are sensitive to copied or trimmed code

    Safe HTML Minification Workflow

    • Keep a readable source file. Comments and indentation help future edits, so treat minified HTML as output.
    • Minify after template rendering. If a CMS or build step injects content, minify the final output rather than a half-rendered template.
    • Check generated source in a browser. Use View Source or DevTools to confirm the minified file is the one being served.
    • Pair it with compression. Minification reduces source bytes. Gzip or brotli reduces transfer bytes.
    • Avoid editing the minified copy. If you need a change, edit the readable source and create a fresh minified output.

    Related Tools

    How to use this tool

    1

    Paste your HTML into the input area

    2

    Click Minify HTML to compress

    3

    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?
    It removes comments, collapses whitespace, and eliminates unnecessary line breaks. The result is smaller HTML that renders identically for most pages, though whitespace-sensitive regions such as pre and code blocks can be affected. A typical page shrinks 15-30%.
    Will minification break my page?
    For most pages, rendering is unchanged because browsers collapse whitespace anyway. However, this minifier collapses all whitespace uniformly, so whitespace-sensitive regions (pre, code, textarea, and inline scripts) can be altered. Tags, attributes, and links are preserved. Test pages that rely on preformatted content before deploying.
    Is my HTML sent to a server?
    No. Everything runs in your browser using JavaScript regex operations. Nothing is uploaded, stored, or transmitted. Safe for production HTML containing sensitive data.
    Should I minify HTML for production?
    Yes, it's free performance. Minified HTML loads faster, parses quicker, and uses less bandwidth. Combined with Gzip/Brotli compression, a 100KB page can shrink to under 10KB over the wire.
    What's the difference between minification and compression?
    Minification removes unnecessary characters from the source code itself. Compression (Gzip, Brotli) encodes the file more efficiently for transfer. They're complementary, minify first, then compress. Together they reduce size by 70-90%.
    Does minification remove my CSS and JavaScript?
    No. Inline styles, embedded CSS, and JavaScript within the HTML are preserved. Only HTML comments and whitespace between tags are removed. For CSS and JS minification, use dedicated tools.
    Can I undo minification?
    Not exactly, comments are permanently removed. But you can re-format the structure using an HTML beautifier to restore readable indentation. That's why you should always keep your source files unminified and only minify for production.
    How much space will I save?
    Typically 15-30% depending on how much whitespace and comments your HTML contains. Heavily commented HTML with generous indentation saves more. Already-compact HTML saves less. The tool shows exact before/after sizes.
    Should I minify HTML or just rely on Gzip?
    Both. Gzip compresses what's there, but it still has to process every byte. Fewer bytes in means fewer bytes to compress, so minification before compression usually gives a smaller output.
    Does Google care about minified HTML?
    Google doesn't directly rank minified vs unminified HTML. But minification improves page load speed, which is a ranking factor via Core Web Vitals. Faster pages also get better user engagement, which indirectly helps rankings.
    What about whitespace in pre tags?
    This tool collapses all whitespace uniformly. If your HTML contains <pre> or <code> blocks where whitespace matters, review those sections after minifying. Most production build tools have options to preserve whitespace in specific tags.
    Can I minify HTML automatically in my build?
    Yes. Vite uses html-minifier-terser by default in production builds. Webpack has HtmlWebpackPlugin with minify options. Most current build tools handle this automatically, this online tool is for quick one-off jobs.
    Should I minify HTML email?
    You can, but test the email after minifying. Some email clients are sensitive to table layout and conditional comments, so keep a readable source template and only send the tested minified copy.
    Does minification remove analytics scripts?
    No. Script tags and inline JavaScript stay in the document. This tool removes comments and whitespace around markup, not the functional code inside a script tag.
    Can minified HTML still be crawled?
    Yes. Search engines and browsers parse minified HTML normally. Minification changes the text layout in the source file, not the elements, links, headings, or structured data the crawler reads.
    What should I preserve before minifying?
    Keep the original source file, especially if it contains comments, template hints, or readable spacing around email tables. Minified output is a deploy artefact, not the file you should edit later.
    Can I minify a single HTML component?
    Yes. You can paste a full document, a component fragment, or a single repeated block. Just make sure the result is used in the same context as the original snippet.
    What happens to conditional comments?
    This tool removes HTML comments. If you are working with old Outlook email conditional comments, keep the readable source and test before removing them.

    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.