HTML Minifier — Compress HTML Code Online

HTML documents contain several categories of content that are purely for human readability and have no effect on browser rendering. Indentation whitespace between elements — the spaces and newlines used to make markup readable — is ignored by the browser when rendering block elements. HTML comments (<!-- ... -->) are not rendered and serve no purpose in production builds. Optional attribute quotes are permitted by the HTML5 specification: attributes whose values contain no spaces or special characters can be written without quotes, saving two characters per attribute. Optional closing tags (e.g., </li>, </td>, </tr>) are defined by the HTML specification as optional, meaning the browser infers them. Removing these elements can reduce HTML file size by 10–30% for markup-heavy pages.

Not all whitespace is safe to remove. Whitespace inside inline elements like <span>, <a>, <strong>, and <em> can affect text rendering. A space between two adjacent inline elements (e.g., <span>hello</span> <span>world</span>) creates the visible space between the words — removing it collapses them into "helloworld". Whitespace inside <pre> and <textarea> elements is semantically significant and must never be removed. JavaScript string literals inside <script> tags may contain intentional whitespace. This minifier preserves pre-formatted content and only removes whitespace in safe contexts, but always review the output when minifying templates with complex inline element structures.

Modern frontend build tools have HTML minification built in or available as plugins. Webpack uses html-webpack-plugin with minification options. Vite minifies HTML automatically in production builds. For server-rendered applications, libraries like html-minifier-terser (Node.js) can be integrated as middleware or a build step. In CI/CD pipelines, running HTML minification as a post-build step ensures the deployed artifact is always optimized without requiring developers to manually minify files. Commit unminified HTML to source control for readability and generate the minified version during the build — never commit minified HTML as source code.

HTML minification provides file size reductions, but its impact is amplified when combined with HTTP-level compression. Gzip and Brotli compression — applied by web servers like Nginx and Apache or CDNs like Cloudflare — typically achieve 60–80% compression ratios on text content. Minification before compression improves compression efficiency because it removes repetitive whitespace patterns that compression algorithms handle less efficiently than meaningful text. To measure the actual benefit, compare the transferred size (after compression) in browser DevTools before and after minification. For pages with large amounts of whitespace, minification can meaningfully reduce both uncompressed and compressed transfer sizes, improving Time to First Byte (TTFB) and overall page load performance.