Zellio.io

CSS Minifier

Strip whitespace and comments to ship smaller stylesheets.

Runs locallyWorks offlineShare link carries settings, never your data
Send output toBase64 Encode / DecodeRegex Tester & BuilderSlug / URL EncoderBuild a workflow from thisOutput stays on this page until you send it.

Frequently asked questions

How much smaller will my CSS get?

It depends entirely on how the source is written. Heavily commented, generously indented stylesheets often shrink substantially, while output from a build tool that already strips whitespace may barely change. Minification removes comments, indentation and line breaks — it does not rewrite your selectors.

Will minifying break my stylesheet?

No. Only characters CSS treats as insignificant are removed, so the parsed rules are identical. The one thing to watch is that comments are gone, including licence headers you may be required to keep — preserve those separately.

Should I minify if my server already uses gzip or Brotli?

The gain is smaller, because compression already handles repeated whitespace well, but it is not zero — minified CSS is smaller both on the wire and in memory after decompression. For most sites the real win is compression; treat minification as the cheap extra.

Pro tips

  • Paste unformatted JSON, HTML, CSS, or SQL code and apply consistent indentation (2, 4, or tab spaces) in one click.
  • Use minification toggle to reduce code size by 30-50% for production deployment or email constraints.
  • Export formatted code directly to clipboard to paste into documentation, emails, or config files instantly.
  • Compare formatted vs minified side-by-side to verify code compression doesn't break syntax.

About Code Formatter

Useful for making a minified payload readable again, for checking that a config parses before you ship it, or for stripping a file down for production. Switching language keeps whatever you have already pasted.

Strip the comments, whitespace and line breaks out of a stylesheet to ship a smaller CSS file that downloads and parses faster. Paste your CSS and copy the minified output — it is compressed in your browser and never uploaded.

Paste messy or minified code and instantly beautify, minify or validate JSON, HTML, CSS, SQL, XML and YAML. Beautifying re-indents your source with consistent spacing so it is easy to read and review; minifying strips whitespace and comments to ship smaller files; validating surfaces syntax errors with the exact location so you can fix them fast.

It also doubles as a converter between common data formats — JSON to CSV, CSV to JSON, YAML to JSON and back — which is handy when wiring up APIs, configs or spreadsheets. Converting is where structure mismatches surface: CSV has no nesting, so a nested JSON object has to be flattened or dropped.

Validation errors cluster into a small set worth recognising by shape, because the parser's message often points at the end of the file rather than the mistake. A trailing comma after the last item is legal in JavaScript and illegal in JSON, and is by far the most common cause. Single-quoted strings and unquoted keys are valid JavaScript object literals and invalid JSON, which is why pasting a console-logged object into a config file so reliably fails. NaN, Infinity and undefined have no JSON representation at all, yet serialisers emit them anyway.

Minifying deserves a moment of scepticism. Stripping whitespace shrinks a file, but gzip and Brotli already compress repeated whitespace to almost nothing over the wire, so the real-world saving on a text asset is far smaller than the byte count suggests. Minify what ships to a browser; leave configuration and fixtures readable, since a diff on a minified file is unreviewable and that costs more than the bytes.

Indentation width is worth deciding once and applying everywhere rather than per file. Mixed indentation is invisible until a diff shows every line as changed because someone's editor expanded tabs differently, at which point a one-line fix becomes an unreviewable pull request. Two spaces is the common default for JSON, YAML and web languages, and YAML in particular forbids tabs outright — a tab in a YAML file is a parse error, not a style preference.

Common use cases

  • Shrinking a hand-written stylesheet before uploading it to a site with no build step
  • Trimming critical CSS that gets inlined into the document head
  • Checking how much of a stylesheet's size is comments and formatting
How it comparesWhile Prettier and VS Code extensions require installation and configuration, our web-based formatter works instantly on any device without setup, offering broader language support (HTML, CSS, SQL) in a single tool compared to language-specific formatters like Beautifier.io.