Slant is a new Q&A site that makes it easy to choose what to use.
Get recommendations
Ask a Question and our community will recommend the best Options that meet your actual needs.
Choose the best
Slant crowdsources research to save hours of work. All the information you need to choose is now in one place.
Join the Community
Slant works like a wiki anyone can edit. Help people find the right Option for them by sharing your knowledge.

CSS preprocessors are extension languages that compile into CSS. They add functionalities to CSS such as variables, mixins and nested inheritance. The added features depend on that specific preprocessor.

CSS preprocessors result in cleaner, easier to read code that’s faster to edit than pure CSS. Another major benefit is that preprocessors feature ways to write reusable code blocks, helping developers adhere to the principle of DRY (don’t repeat yourself) programming.

CSS postprocessors parse plain CSS (for example: to include vendor prefixes).

When choosing the best option for your project, consider the community. A large, active community will make it easier to get support and will provide more learning resources. Consider how detailed and well-written the documentation is. Is the information organized well and are enough examples provided? Check to see if it’s actively developed for bug fixes and new features.


openWhy do you recommend Sass?

openWhy don't you recommend Sass?

Sass provides two syntax options - Sass, which omits the use of semicolons and brackets, and SCSS, which is written like vanilla CSS with added featu...

Powerful advanced function features

You are able to declare custom functions with Sass (for example, converting units) which can be easily invoked, even when using shorthand properties....

Compass framework provides added features

Sass can be used with a framework called Compass, which provides additional functions and mixins which can reduce the amount of code you have to writ...

Requires Ruby or libSass

Sass compiles in Ruby. To run the code locally, the use of a library (libSass) is requires.


openWhy do you recommend Less?

openWhy don't you recommend Less?

Less is a great choice if you want the majority of the benefits of a CSS preprocessor without having to learn a new syntax and advanced features.Less...

Easy to learn

Because Less has a lightweight feature set, is syntactically similar to CSS and can be run client side with file conversion on a page reload, it is...

Familiar CSS style syntax

The LESS syntax is essentially the same as CSS with extensions for dynamic behavior such as variables, mixins, operations and functions.Variables:@co...

No custom functions

Less does not offer custom functions and instead requires the use of mixins. This is limiting in many ways - Functions cannot be called on shorthand...


openWhy do you recommend Stylus?

openWhy don't you recommend Stylus?

Compared to its competition, Stylus has a superior feature set and an optional, incredibly terse syntax.

Clean, flexible syntax

Stylus has an extremely terse syntax. Colons, semicons and braces are all optional allowing you to write Stylus code however you want. hover-darken(...

Powerful feature set

Not only does Stylus support all the features from Less and Sass, it provides features not found anywhere else: You can get properties from paren...

Not as popular as Less and Sass

Stylus is younger than both Less and Sass, and not yet at the same level of popularity. As a result, Stylus currently has a smaller and less active c...

openWhy do you recommend PostCSS?

openWhy don't you recommend PostCSS?

PostCSS is compilation step for your CSS that supports a variety of plugins for everything from CSS4 syntax support to minification and fallback gene...


PostCSS is 3-30 times faster than Sass (including libsass), Less, and Stylus


PostCSS allows you to opt-in to the features you need with plugins. This allows you to set it up to behave exactly like Sass, with nesting, mixing, e...

Lack of support in IDEs

Currently there is very little support for syntax highlighting when writing PostCSS plugins.


openWhy do you recommend Stylecow?

openWhy don't you recommend Stylecow?

Stylecow is a post-processor that allows to write in pure CSS, so you don't need to learn another syntax. It provides a lot of plugins to bring s...

Advanced API and parser

The parser detects any CSS syntax error found. The output code can be customized to follow your own code style rules (indentation, spaces, string quo...

Easy to install and use

It's written in node, so you can install it with npm. All available plugins are installed by default and include some development tools like a wa...

Young project, small community

Stylecow doesn't have a very large community. This can make it difficult to find answers and increases the risk of the project being abandoned.

openWhy do you recommend Rework?

openWhy don't you recommend Rework?

Rework is designed to extend the functionality of vanilla CSS.

Unrestricted potential

Because Rework plugins are done in code, there are no limits to what they can do, and they tend to provide more advanced functionality that would be...

Built around plugins

Rework isn't a language for compiling to CSS but rather a library around parsing it and transforming it. For example, a vendor prefix plugin will...

Difficult for beginners

Rework has a more involved setup that can make it an intimidating first option for beginners to css processing. As Rework is built around plugins, t...

openWhy do you recommend Pleeease?

openWhy don't you recommend Pleeease?

Pleeease is a Node.js application that easily process your CSS. It simplifies the use of preprocessors and combines them with best postprocessors. It...

Combines media queries into single rules

If you have repeated media queries in your stylesheet, Pleeease will pack them into a single media query when compiled.

Rem fallback

Rem unites are not supported in IE8 and below, so Pleeease provides a pixel fallback.

No cons added yet

openWhy do you recommend CSS-Crush?

openWhy don't you recommend CSS-Crush?

Implemented in PHP

PHP is used in common platforms such as Drupal and Wordpress, which results in CSS-Crush being easy to integrate with most development stacks.

Out of the box vendor prefixing

Rather than require a plugin, CSS-Crush will automatically add vendor prefixes.

Not widely used

CSS-Crush is not a widely used option. The small community of users results in a harder time finding answers to any questions you may have.

openWhy do you recommend CSS-On-Diet?

openWhy don't you recommend CSS-On-Diet?

CSS-On-Diet is a preprocessor created with designers in mind. It's main feature is shortened keywords to make writing CSS more efficient.

Easy to learn and use

Doesn't require programming skill to work with variables, mixins, media breakpoints

Fast to read and write CSS

Works like Emmet, shorting CSS keywords, but it's not limited only to writing. Also modifying and reading COD(CSS-On-Diet) files is faster.

It's difficult adjusting to different keywords

The keywords are shortened to 3 letters. For example, "background-color" becomes "bac" and "max-width" becomes "ma...