JS Minifier

No — minification preserves runtime behavior exactly. Only whitespace, comments, and unnecessary semicolons or parentheses are stripped, and identifier names inside scopes can be shortened (a, b, c instead of userName, isLoggedIn) without changing logic. The one place developers get burned: code that relies on Function.prototype.toString() or function names for runtime introspection (some old test frameworks, certain DI containers) can break when names are mangled. If you avoid those patterns — which 99% of code does — minified output runs identically to the source.

Typically 30-50% smaller for hand-written code, and up to 60-70% for files with lots of comments, JSDoc blocks, or generous whitespace. After minification, gzip or brotli on the server adds another 60-70% reduction on top — so a 100KB source file might end up as 15-20KB over the wire. The two compressions stack because minification removes information that's already easy to compress (repeated whitespace), while gzip removes redundancy in the remaining tokens. Always serve minified files with gzip/brotli enabled to capture both wins.

Yes. Gzip and minification optimize different things: gzip compresses byte patterns (it's incredibly good at long runs of whitespace, but only on the wire), while minification reduces the actual amount of code the browser has to parse, store, and execute. Even if gzip flattens both files to similar transfer sizes, the minified file uses less memory, parses faster, and tokenizes faster in the JS engine. For modern frameworks where parsing is often the bottleneck, that matters more than transfer size. Bundle minification + gzip + HTTP/2 for the best result.

Terser, esbuild's minifier, and (legacy) UglifyJS are full Node.js build-pipeline minifiers that support advanced features: identifier mangling, dead-code elimination, ES module tree-shaking, source maps, and per-file configuration. They're the right choice when you have a build step (Webpack, Vite, Next.js, esbuild). This browser tool is for the case where you don't — a one-off script, a snippet you want to inline into a CMS, a third-party file you want to compress before re-serving. The output is competitive with terser for whitespace/comment removal, but it doesn't do aggressive identifier mangling. For production builds with bundlers, stick with your bundler's built-in minifier.

Yes. The minifier handles the full modern JavaScript syntax — async/await, optional chaining (?.), nullish coalescing (??), top-level await, class fields, private methods (#name), and BigInt literals all pass through correctly. The output preserves whatever syntax level your input uses; this is a minifier, not a transpiler, so it won't downlevel ES2022 to ES5. If you need to ship to older browsers, run your code through Babel or esbuild's transform first, then minify the output here.