CSS and JavaScript Minification Libraries Comparison
csso vs clean-css vs cssnano vs uglifycss vs minify vs postcss-clean
1 Year
cssoclean-csscssnanouglifycssminifypostcss-cleanSimilar Packages:
What's CSS and JavaScript Minification Libraries?

Minification libraries are essential tools in web development that reduce the size of CSS and JavaScript files by removing unnecessary characters, comments, and whitespace. This process improves load times and enhances overall performance of web applications. Each of these libraries offers unique features and optimizations, catering to different use cases and preferences among developers.

NPM Package Downloads Trend
Github Stars Ranking
Stat Detail
Package
Downloads
Stars
Size
Issues
Publish
License
csso15,226,2443,764606 kB99-MIT
clean-css15,085,2034,174493 kB32a year agoMIT
cssnano11,082,0534,8087.33 kB963 months agoMIT
uglifycss82,957284-107 years agoMIT
minify42,01623038.4 kB2a month agoMIT
postcss-clean12,04941-124 years agoMIT
Feature Comparison: csso vs clean-css vs cssnano vs uglifycss vs minify vs postcss-clean

Optimization Techniques

  • csso:

    csso focuses on both minification and optimization by restructuring CSS rules for better performance. It analyzes the stylesheet and applies techniques like merging selectors and removing unused styles, which can lead to significant size reductions.

  • clean-css:

    clean-css employs various optimization techniques such as merging rules, removing duplicate properties, and optimizing color values. It also allows for advanced options like restructuring stylesheets to improve performance further.

  • cssnano:

    cssnano utilizes a modular approach with multiple optimization plugins that can be configured based on the project's needs. It includes features like reducing CSS specificity and optimizing media queries, making it highly flexible.

  • uglifycss:

    uglifycss aggressively minifies CSS by removing all whitespace, comments, and unnecessary characters. It focuses solely on reducing file size, making it suitable for projects where performance is critical.

  • minify:

    minify uses a straightforward approach to remove whitespace, comments, and unnecessary characters from CSS and JavaScript files. It is less configurable but effective for basic minification needs.

  • postcss-clean:

    postcss-clean integrates with PostCSS to provide a simple cleaning process that removes whitespace and comments. It is designed for users who prefer a minimalistic approach to CSS processing without extensive configuration.

Integration

  • csso:

    csso can be integrated into build systems like Gulp and Webpack, providing a simple way to optimize and minify CSS files during the build process without additional overhead.

  • clean-css:

    clean-css can be easily integrated into various build tools and task runners like Gulp and Grunt, allowing for seamless automation of the minification process in your development workflow.

  • cssnano:

    cssnano is designed to work as a PostCSS plugin, making it an excellent choice for projects that already utilize PostCSS for processing CSS. Its integration is straightforward and enhances existing workflows.

  • uglifycss:

    uglifycss can be used as a command-line tool or integrated into build systems, providing flexibility for developers who want a quick and effective way to minify CSS.

  • minify:

    minify is a standalone tool that can be used in various environments, making it easy to incorporate into any project without requiring complex setup or configuration.

  • postcss-clean:

    postcss-clean is a PostCSS plugin, which means it fits naturally into workflows that already use PostCSS. This allows developers to maintain a consistent processing pipeline without introducing new tools.

Ease of Use

  • csso:

    csso is relatively easy to use, with a clear API that allows developers to quickly implement it in their projects. Its focus on both optimization and minification makes it a versatile choice.

  • clean-css:

    clean-css offers a user-friendly API with straightforward options for customization, making it accessible for developers of all skill levels who want to optimize their CSS efficiently.

  • cssnano:

    cssnano's configuration can be complex due to its modular nature, but it provides extensive documentation to help users navigate its features. It may require a learning curve for those unfamiliar with PostCSS.

  • uglifycss:

    uglifycss is simple to use, providing a command-line interface that allows developers to quickly minify CSS files with minimal configuration.

  • minify:

    minify is designed for simplicity, making it an excellent choice for beginners or those looking for a quick solution without the need for extensive configuration or setup.

  • postcss-clean:

    postcss-clean is straightforward to use as a PostCSS plugin, making it easy to add to existing workflows without requiring additional setup or learning new tools.

Performance

  • csso:

    csso is designed to optimize CSS not only for size but also for performance. Its restructuring capabilities can lead to faster loading times by reducing the number of selectors and rules that the browser needs to process.

  • clean-css:

    clean-css is optimized for performance, capable of handling large stylesheets efficiently without significant slowdowns during the minification process. It is suitable for high-traffic websites where speed is crucial.

  • cssnano:

    cssnano's performance depends on the configuration of its plugins, but it is generally efficient and can handle complex stylesheets with ease, making it a good choice for modern web applications.

  • uglifycss:

    uglifycss focuses on aggressive minification, which can lead to significant reductions in file size. However, its performance may vary based on the complexity of the CSS being processed.

  • minify:

    minify provides decent performance for basic minification tasks, but it may not be as fast or efficient as some of the more advanced tools when dealing with larger files or complex stylesheets.

  • postcss-clean:

    postcss-clean is lightweight and performs well in cleaning up CSS files, making it a good choice for projects that prioritize speed and efficiency in their build processes.

Community and Support

  • csso:

    csso has a growing community and is well-documented, offering users the resources they need to implement it effectively in their projects. It is actively maintained with regular updates.

  • clean-css:

    clean-css has a strong community and is actively maintained, providing users with regular updates and support. Its documentation is comprehensive, making it easy to find help when needed.

  • cssnano:

    cssnano benefits from the large PostCSS community, ensuring that users have access to a wealth of resources, plugins, and support. Its documentation is extensive, aiding in the learning process.

  • uglifycss:

    uglifycss has a dedicated user base and is maintained actively, providing users with the necessary support and documentation to effectively use the tool.

  • minify:

    minify has a smaller community compared to others but is straightforward enough that users can find help through general web development forums and resources.

  • postcss-clean:

    postcss-clean is part of the PostCSS ecosystem, benefiting from the community and support available for PostCSS users. Its integration with PostCSS means users can find help in a broader context.

How to Choose: csso vs clean-css vs cssnano vs uglifycss vs minify vs postcss-clean
  • csso:

    Select csso if you are looking for a CSS optimizer that focuses on restructuring and compressing stylesheets while maintaining their functionality. It is particularly beneficial for projects that prioritize both size reduction and code readability.

  • clean-css:

    Choose clean-css if you need a fast and efficient CSS minifier that offers a variety of optimization options and can handle large stylesheets effectively. It is particularly useful for projects where performance is critical and you want granular control over the minification process.

  • cssnano:

    Opt for cssnano if you are using PostCSS and want a highly configurable CSS minification tool that integrates seamlessly into your build process. It offers a wide range of optimization plugins and is ideal for projects that require advanced CSS processing capabilities.

  • uglifycss:

    Opt for uglifycss if you specifically need a CSS minifier that focuses on reducing file size through aggressive minification techniques. It is ideal for projects where minimizing CSS file size is the top priority.

  • minify:

    Use minify if you need a simple and straightforward tool for minifying both CSS and JavaScript files. It is best suited for smaller projects or when you want a quick solution without extensive configuration options.

  • postcss-clean:

    Choose postcss-clean if you are already using PostCSS and want a lightweight solution for cleaning up your CSS. It is designed to work as a PostCSS plugin, making it easy to integrate into existing workflows without adding complexity.

README for csso

NPM version Build Status Coverage Status NPM Downloads Twitter

CSSO (CSS Optimizer) is a CSS minifier. It performs three sort of transformations: cleaning (removing redundants), compression (replacement for the shorter forms) and restructuring (merge of declarations, rules and so on). As a result an output CSS becomes much smaller in size.

Install

npm install csso

Usage

import { minify } from 'csso';
// CommonJS is also supported
// const { minify } = require('csso');

const minifiedCss = minify('.test { color: #ff0000; }').css;

console.log(minifiedCss);
// .test{color:red}

Bundles are also available for use in a browser:

  • dist/csso.js – minified IIFE with csso as global
<script src="node_modules/csso/dist/csso.js"></script>
<script>
  csso.minify('.example { color: green }');
</script>
  • dist/csso.esm.js – minified ES module
<script type="module">
  import { minify } from 'node_modules/csso/dist/csso.esm.js'

  minify('.example { color: green }');
</script>

One of CDN services like unpkg or jsDelivr can be used. By default (for short path) a ESM version is exposing. For IIFE version a full path to a bundle should be specified:

<!-- ESM -->
<script type="module">
  import * as csstree from 'https://cdn.jsdelivr.net/npm/csso';
  import * as csstree from 'https://unpkg.com/csso';
</script>

<!-- IIFE with an export to global -->
<script src="https://cdn.jsdelivr.net/npm/csso/dist/csso.js"></script>
<script src="https://unpkg.com/csso/dist/csso.js"></script>

CSSO is based on CSSTree to parse CSS into AST, AST traversal and to generate AST back to CSS. All CSSTree API is available behind syntax field extended with compress() method. You may minify CSS step by step:

import { syntax } from 'csso';

const ast = syntax.parse('.test { color: #ff0000; }');
const compressedAst = syntax.compress(ast).ast;
const minifiedCss = syntax.generate(compressedAst);

console.log(minifiedCss);
// .test{color:red}

Also syntax can be imported using csso/syntax entry point:

import { parse, compress, generate } from 'csso/syntax';

const ast = parse('.test { color: #ff0000; }');
const compressedAst = compress(ast).ast;
const minifiedCss = generate(compressedAst);

console.log(minifiedCss);
// .test{color:red}

Warning: CSSO doesn't guarantee API behind a syntax field as well as AST format. Both might be changed with changes in CSSTree. If you rely heavily on syntax API, a better option might be to use CSSTree directly.

Related projects

API

minify(source[, options])

Minify source CSS passed as String.

const result = csso.minify('.test { color: #ff0000; }', {
    restructure: false,   // don't change CSS structure, i.e. don't merge declarations, rulesets etc
    debug: true           // show additional debug information:
                          // true or number from 1 to 3 (greater number - more details)
});

console.log(result.css);
// > .test{color:red}

Returns an object with properties:

Options:

  • sourceMap

    Type: Boolean
    Default: false

    Generate a source map when true.

  • filename

    Type: String
    Default: '<unknown>'

    Filename of input CSS, uses for source map generation.

  • debug

    Type: Boolean
    Default: false

    Output debug information to stderr.

  • beforeCompress

    Type: function(ast, options) or Array<function(ast, options)> or null
    Default: null

    Called right after parse is run.

  • afterCompress

    Type: function(compressResult, options) or Array<function(compressResult, options)> or null
    Default: null

    Called right after syntax.compress() is run.

  • Other options are the same as for syntax.compress() function.

minifyBlock(source[, options])

The same as minify() but for list of declarations. Usually it's a style attribute value.

const result = csso.minifyBlock('color: rgba(255, 0, 0, 1); color: #ff0000');

console.log(result.css);
// > color:red

syntax.compress(ast[, options])

Does the main task – compress an AST. This is CSSO's extension in CSSTree syntax API.

NOTE: syntax.compress() performs AST compression by transforming input AST by default (since AST cloning is expensive and needed in rare cases). Use clone option with truthy value in case you want to keep input AST untouched.

Returns an object with properties:

  • ast Object – resulting AST

Options:

  • restructure

    Type: Boolean
    Default: true

    Disable or enable a structure optimisations.

  • forceMediaMerge

    Type: Boolean
    Default: false

    Enables merging of @media rules with the same media query by splitted by other rules. The optimisation is unsafe in general, but should work fine in most cases. Use it on your own risk.

  • clone

    Type: Boolean
    Default: false

    Transform a copy of input AST if true. Useful in case of AST reuse.

  • comments

    Type: String or Boolean
    Default: true

    Specify what comments to leave:

    • 'exclamation' or true – leave all exclamation comments (i.e. /*! .. */)
    • 'first-exclamation' – remove every comment except first one
    • false – remove all comments
  • usage

    Type: Object or null
    Default: null

    Usage data for advanced optimisations (see Usage data for details)

  • logger

    Type: Function or null
    Default: null

    Function to track every step of transformation.

Source maps

To get a source map set true for sourceMap option. Additianaly filename option can be passed to specify source file. When sourceMap option is true, map field of result object will contain a SourceMapGenerator instance. This object can be mixed with another source map or translated to string.

const csso = require('csso');
const css = fs.readFileSync('path/to/my.css', 'utf8');
const result = csso.minify(css, {
  filename: 'path/to/my.css', // will be added to source map as reference to source file
  sourceMap: true             // generate source map
});

console.log(result);
// { css: '...minified...', map: SourceMapGenerator {} }

console.log(result.map.toString());
// '{ .. source map content .. }'

Example of generating source map with respect of source map from input CSS:

import { SourceMapConsumer } from 'source-map';
import * as csso from 'csso';

const inputFile = 'path/to/my.css';
const input = fs.readFileSync(inputFile, 'utf8');
const inputMap = input.match(/\/\*# sourceMappingURL=(\S+)\s*\*\/\s*$/);
const output = csso.minify(input, {
  filename: inputFile,
  sourceMap: true
});

// apply input source map to output
if (inputMap) {
  output.map.applySourceMap(
    new SourceMapConsumer(inputMap[1]),
    inputFile
  )
}

// result CSS with source map
console.log(
  output.css +
  '/*# sourceMappingURL=data:application/json;base64,' +
  Buffer.from(output.map.toString()).toString('base64') +
  ' */'
);

Usage data

CSSO can use data about how CSS is used in a markup for better compression. File with this data (JSON) can be set using usage option. Usage data may contain following sections:

  • blacklist – a set of black lists (see Black list filtering)
  • tags – white list of tags
  • ids – white list of ids
  • classes – white list of classes
  • scopes – groups of classes which never used with classes from other groups on the same element

All sections are optional. Value of tags, ids and classes should be an array of a string, value of scopes should be an array of arrays of strings. Other values are ignoring.

White list filtering

tags, ids and classes are using on clean stage to filter selectors that contain something not in the lists. Selectors are filtering only by those kind of simple selector which white list is specified. For example, if only tags list is specified then type selectors are checking, and if all type selectors in selector present in list or selector has no any type selector it isn't filter.

ids and classes are case sensitive, tags – is not.

Input CSS:

* { color: green; }
ul, ol, li { color: blue; }
UL.foo, span.bar { color: red; }

Usage data:

{
    "tags": ["ul", "LI"]
}

Resulting CSS:

*{color:green}ul,li{color:blue}ul.foo{color:red}

Filtering performs for nested selectors too. :not() pseudos content is ignoring since the result of matching is unpredictable. Example for the same usage data as above:

:nth-child(2n of ul, ol) { color: red }
:nth-child(3n + 1 of img) { color: yellow }
:not(div, ol, ul) { color: green }
:has(:matches(ul, ol), ul, ol) { color: blue }

Turns into:

:nth-child(2n of ul){color:red}:not(div,ol,ul){color:green}:has(:matches(ul),ul){color:blue}

Black list filtering

Black list filtering performs the same as white list filtering, but filters things that mentioned in the lists. blacklist can contain the lists tags, ids and classes.

Black list has a higher priority, so when something mentioned in the white list and in the black list then white list occurrence is ignoring. The :not() pseudos content ignoring as well.

* { color: green; }
ul, ol, li { color: blue; }
UL.foo, li.bar { color: red; }

Usage data:

{
    "blacklist": {
        "tags": ["ul"]
    },
    "tags": ["ul", "LI"]
}

Resulting CSS:

*{color:green}li{color:blue}li.bar{color:red}

Scopes

Scopes is designed for CSS scope isolation solutions such as css-modules. Scopes are similar to namespaces and define lists of class names that exclusively used on some markup. This information allows the optimizer to move rules more agressive. Since it assumes selectors from different scopes don't match for the same element. This can improve rule merging.

Suppose we have a file:

.module1-foo { color: red; }
.module1-bar { font-size: 1.5em; background: yellow; }

.module2-baz { color: red; }
.module2-qux { font-size: 1.5em; background: yellow; width: 50px; }

It can be assumed that first two rules are never used with the second two on the same markup. But we can't say that for sure without a markup review. The optimizer doesn't know it either and will perform safe transformations only. The result will be the same as input but with no spaces and some semicolons:

.module1-foo{color:red}.module1-bar{font-size:1.5em;background:#ff0}.module2-baz{color:red}.module2-qux{font-size:1.5em;background:#ff0;width:50px}

With usage data CSSO can produce better output. If follow usage data is provided:

{
    "scopes": [
        ["module1-foo", "module1-bar"],
        ["module2-baz", "module2-qux"]
    ]
}

The result will be (29 bytes extra saving):

.module1-foo,.module2-baz{color:red}.module1-bar,.module2-qux{font-size:1.5em;background:#ff0}.module2-qux{width:50px}

If class name isn't mentioned in the scopes it belongs to default scope. scopes data doesn't affect classes whitelist. If class name mentioned in scopes but missed in classes (both sections are specified) it will be filtered.

Note that class name can't be set for several scopes. Also a selector can't have class names from different scopes. In both cases an exception will thrown.

Currently the optimizer doesn't care about changing order safety for out-of-bounds selectors (i.e. selectors that match to elements without class name, e.g. .scope div or .scope ~ :last-child). It assumes that scoped CSS modules doesn't relay on it's order. It may be fix in future if to be an issue.