Code Minifier

Every byte of whitespace and every comment ships to the browser unless you strip it first. Code Minifier removes the comments, redundant spacing, and line breaks from JavaScript, CSS, and HTML, then shows you exactly how many bytes you saved.

It suits the quick optimization pass: shrinking an inline script or stylesheet before pasting it into a template, trimming a snippet for an embed, or just seeing how much fat a file is carrying. It works on three languages, and for JavaScript it is careful to preserve URLs while removing comments, so a // inside an http:// link does not accidentally eat the rest of the line.

Smaller files mean fewer bytes over the wire and faster page loads, which is why minification is a standard step before code ships to production — and seeing the byte count drop makes the benefit concrete.

Minification here removes line and block comments, collapses runs of whitespace, and tightens the spacing around punctuation such as braces, parentheses, semicolons, and operators. Protocol-bearing URLs are protected before comment removal, since the double slash in a URL would otherwise be mistaken for the start of a comment.

That protection hints at the broader caveat: this works by pattern matching rather than by parsing the language, so it cannot always distinguish code from things that merely look like code. A string containing what appears to be a comment, a regular expression literal containing a slash, or a template literal whose whitespace is significant are all cases where a pattern-based pass can damage meaning.

Use it for a quick size reduction on a self-contained snippet, and check the output. For anything being shipped, use a real build-time minifier — those parse to a syntax tree and are safe by construction.

Whitespace removal is the smallest part of a production minifier's work. The substantial gains come from renaming local variables to single characters, eliminating unreachable code, inlining trivial functions, and dropping exports nothing imports — tree shaking. Those require understanding scope and references, which is only possible with a parsed representation.

Compression matters more than minification for transfer size, and the two compound. Gzip and Brotli both exploit repetition, and Brotli's built-in dictionary of common web text does well on markup and script; serving compressed assets is usually a larger win than any minification step, and it is a server configuration rather than a build change.

Two final points. Always generate source maps for minified production code, or every stack trace becomes unreadable. And minification is not obfuscation — variable names are gone, but the logic is entirely recoverable, so nothing secret should ever be shipped to a client on the assumption that minifying hides it.