Compress CSS by removing comments, redundant whitespace and empty rules. Nothing is reordered, merged or rewritten, because all three can change rendering.
Waiting for a stylesheet
Comments, redundant whitespace and empty rules. Nothing is reordered or merged.
Minified CSS appears here
The space in calc() stays, because removing it makes the expression invalid. So does the inside of an unquoted url().
CSS Minifier runs entirely on your device — nothing is uploaded.
You’re on the Free plan. Compare plans
This minifier removes what is provably redundant and stops there: comments, whitespace no value depends on, the final semicolon in each block, the space around >, + and ~ in selectors, and rules whose body is empty.
What it will not do is the interesting part. It does not shorten colours, merge duplicate selectors, reorder declarations, or drop declarations it believes are overridden. Each of those is a real optimisation and each has a case where it changes what a page looks like. Merging two rules changes their position relative to a third. Dropping an 'overridden' declaration ignores every other stylesheet on the page, and the inline styles, and the cascade layer the rule sits in. Those transformations belong in a build step that can be tested against a real page, not in a paste box with no page to test against.
Two kinds of whitespace are load-bearing and are left alone. The descendant combinator — the space in .a .b — means something entirely different from .a.b, so only the whitespace around explicit combinators is removed. And the contents of an unquoted url() are the URL itself: compressing url(a, b.png) changes which file the browser asks for, so that span is stepped over entirely.
Banner comments, the /*! … */ form, are kept by default because they usually carry a licence that is supposed to survive minification.
As with HTML, gzip or brotli will do more for transfer size than minification will. Minifying CSS is most worthwhile when it is going somewhere uncompressed — inlined into a page's <style> block, embedded in an email, or stored as a string.
Because colour rewriting is where minifiers get it wrong. #ff0000 to red is safe; many other conversions are not, particularly once colour functions and custom properties are involved. The bytes saved are small and the failure mode is a page that renders the wrong colour, so the trade is not worth it here.
Because merging changes order. Two rules with the same selector in different places are not equivalent to one rule, if anything between them also matches those elements. Doing it correctly means understanding the whole cascade, which needs the page.
For the transformations it performs, yes — each only removes characters that the CSS grammar treats as insignificant at that position. That is precisely why the list of transformations is short.
It stays. That space is the descendant combinator, and .a.b means something completely different. Only whitespace around the explicit combinators > + and ~ and around commas is removed.
Because an unquoted url() contains the URL literally, spaces and all. Compressing it would change which file the browser requests, which is a far worse outcome than a few extra bytes.
For a project with a build, use the build — a tool like cssnano can do the riskier optimisations safely because it runs against your actual output and you can test the result. This is for the cases where there is no build: a snippet to inline, an email, a string in code.