Minify CSS with csso, a real parser that keeps calc() spacing and string contents intact. An optional restructure pass merges rules for an even smaller file.
Your files are processed in your browser, on your own device. Nothing is uploaded to a server.
A CSS Minifier removes the comments, spaces and line breaks that make a stylesheet readable, and ships the compact version to the browser. ToolPeko builds its CSS Minifier on csso, a real CSS parser, and it runs free in your browser with no upload. Before and after sizes sit under the output.
Paste your CSS and csso parses it into a real syntax tree before changing a single character. Working from the tree, instead of hunting through raw text with patterns, is what keeps selectors, strings and values safe while the padding around them disappears.
The restructure option is the aggressive one. It can merge rules that share declarations and tidy the order of the sheet in the hunt for a smaller file. Most sites ship the plain pass. Reach for restructure when you want the last few percent and you can test the pages the sheet styles.
Production stylesheets are the main case. A hand-written sheet grows comments, blank lines and breathing room over months of edits, all of it useful while you work and all of it dead weight on the live site. Minifying at deploy time keeps the working file friendly and the shipped file lean.
Inline styles are the second case. Critical CSS pasted into a page head, a style block dropped into a theme settings field, or CSS stored inside a CMS template all carry size limits or size costs that a compact sheet handles better. A few kilobytes saved in the head of every page adds up across a site.
Trust is the third case, and it is the one this page is built around. A parser-based minifier shrinks the file without rewriting what your selectors mean, which is the difference between a routine deploy and a layout that quietly changed overnight. When a sheet has to become readable again, the CSS Beautifier reverses the trip, and the HTML Minifier and JS Minifier handle the rest of the page.
The danger with CSS is that the naive approach actively breaks things. A pattern tool that strips spaces on sight will wreck a sheet: calc(100% – 10px) with its spaces removed is a syntax error, not a style. A selector like div :first-child means something different from div:first-child, and text inside strings or url() values can be altered without anyone noticing. A real parser knows which spaces the spec demands and leaves string contents byte for byte alone.
Comments are removed during minification, so keep your readable original as the file you edit. The minified sheet is a build product, not a source file. Sheets that lean on very old browser hacks deserve a test run too, because hacks that depend on broken parsing can fail under any parser that reads CSS correctly.
Restructure deserves its own warning. Merging and reordering rules can change which declaration wins in rare tie cases where two rules carry the same weight. Test the styled pages after a restructure pass before it ships. And one last point: minified CSS is still plain CSS that anyone can open and read. Minification is a size tool, never a way to hide code.
csso runs inside your browser tab. Your CSS is never sent to a ToolPeko server, never stored and never read by anyone here. That includes stylesheets from client projects and unreleased redesigns, which take the same code path as a test snippet. There is no account, no sign-up and no per-file cap. Paste a component sheet or a full design system and the terms stay the same.
It is a real parser. The tool is built on csso, which reads your CSS into a syntax tree before changing anything. That is what keeps selectors, strings and calc() spacing safe during minification.
No. The spaces around the minus and plus signs in calc() are part of the syntax, and the parser keeps the spaces the spec demands. Pattern tools that strip spaces blindly are the ones that break calc().
It lets csso merge rules and reorganize the sheet for a smaller result, on top of removing whitespace and comments. Because reordering can change which declaration wins in a rare tie, test the styled pages after using it.
Comments are stripped during minification. Keep your original file as the editable source, and ship the minified output as the build product.
It depends on how much padding and commentary your source carries. The page shows the before and after sizes for your actual file, which is a better answer than any general promise.
No upload happens. Minification runs in your browser tab, and nothing is sent to or stored on a ToolPeko server.
Same rules as this one: free, in your browser, with nothing uploaded.
Paste messy JSON, get it neat and valid.
Check JSON and find the exact line that breaks it.
Squeeze JSON down to one tight line.
Open JSON as a tree you can fold and explore.
JSON rows turned into a CSV a spreadsheet can open.
A CSV file turned into clean JSON objects.
JSON rewritten as YAML for config files.
YAML config turned into JSON you can use in code.