Get Advice Icon

Need advice about which tool to choose?Ask the StackShare community!

PostCSS
PostCSS

396
329
+ 1
46
Sass
Sass

15.1K
11K
+ 1
3K
Add tool

PostCSS vs Sass: What are the differences?

PostCSS: Transform CSS with JS plugins. PostCSS is a tool for transforming CSS with JS plugins. These plugins can support variables and mixins, transpile future CSS syntax, inline images, and more; Sass: Syntactically Awesome Style Sheets. Sass is an extension of CSS3, adding nested rules, variables, mixins, selector inheritance, and more. It's translated to well-formatted, standard CSS using the command line tool or a web-framework plugin.

PostCSS and Sass can be categorized as "CSS Pre-processors / Extensions" tools.

"The "babel" of CSS" is the primary reason why developers consider PostCSS over the competitors, whereas "Variables" was stated as the key factor in picking Sass.

PostCSS and Sass are both open source tools. PostCSS with 21K GitHub stars and 1.15K forks on GitHub appears to be more popular than Sass with 12K GitHub stars and 1.93K GitHub forks.

According to the StackShare community, Sass has a broader approval, being mentioned in 2082 company stacks & 1445 developers stacks; compared to PostCSS, which is listed in 62 company stacks and 47 developer stacks.

What is PostCSS?

PostCSS is a tool for transforming CSS with JS plugins. These plugins can support variables and mixins, transpile future CSS syntax, inline images, and more.

What is Sass?

Sass is an extension of CSS3, adding nested rules, variables, mixins, selector inheritance, and more. It's translated to well-formatted, standard CSS using the command line tool or a web-framework plugin.
Get Advice Icon

Need advice about which tool to choose?Ask the StackShare community!

Why do developers choose PostCSS?
Why do developers choose Sass?

Sign up to add, upvote and see more prosMake informed product decisions

    Be the first to leave a con
      Be the first to leave a con
      What companies use PostCSS?
      What companies use Sass?

      Sign up to get full access to all the companiesMake informed product decisions

      What tools integrate with PostCSS?
      What tools integrate with Sass?

      Sign up to get full access to all the tool integrationsMake informed product decisions

      What are some alternatives to PostCSS and Sass?
      Stylus
      Stylus is a revolutionary new language, providing an efficient, dynamic, and expressive way to generate CSS. Supporting both an indented syntax and regular CSS style.
      Less
      Less is a CSS pre-processor, meaning that it extends the CSS language, adding features that allow variables, mixins, functions and many other techniques that allow you to make CSS that is more maintainable, themable and extendable.
      CSS Modules
      It is a CSS file in which all class names and animation names are scoped locally by default. The key words here are scoped locally. With this, your CSS class names become similar to local variables in JavaScript. It goes into the compiler, and CSS comes out the other side.
      node-sass
      It is a library that provides binding for Node.js to LibSass, the C version of the popular stylesheet preprocessor, Sass. It allows you to natively compile .scss files to css at incredible speed and automatically via a connect middleware.
      Animate.css
      It is a bunch of cool, fun, and cross-browser animations for you to use in your projects. Great for emphasis, home pages, sliders, and general just-add-water-awesomeness.
      See all alternatives
      Decisions about PostCSS and Sass
      Lee Benson
      Lee Benson
      React
      React
      GraphQL
      GraphQL
      Apollo
      Apollo
      JavaScript
      JavaScript
      TypeScript
      TypeScript
      Webpack
      Webpack
      React Helmet
      React Helmet
      styled-components
      styled-components
      Sass
      Sass
      Less
      Less
      PostCSS
      PostCSS
      Bootstrap
      Bootstrap
      Semantic UI
      Semantic UI
      Foundation
      Foundation
      React Router
      React Router
      Koa
      Koa
      #JSX
      #React.
      #Css
      #StyledComponents.
      #Async
      #HTML
      #GraphQL
      #Apollo

      ReactQL is a React + GraphQL front-end starter kit. #JSX is a natural way to think about building UI, and it renders to pure #HTML in the browser and on the server, making it trivial to build server-rendered Single Page Apps. GraphQL via Apollo was chosen for the data layer; #GraphQL makes it simple to request just the data your app needs, and #Apollo takes care of communicating with your API (written in any language; doesn't have to be JavaScript!), caching, and rendering to #React.

      ReactQL is written in TypeScript to provide full types/Intellisense, and pick up hard-to-diagnose goofs that might later show up at runtime. React makes heavy use of Webpack 4 to handle transforming your code to an optimised client-side bundle, and in throws back just enough code needed for the initial render, while seamlessly handling import statements asynchronously as needed, making the payload your user downloads ultimately much smaller than trying to do it by hand.

      React Helmet was chosen to handle <head> content, because it works universally, making it easy to throw back the correct <title> and other tags on the initial render, as well as inject new tags for subsequent client-side views.

      styled-components, Sass, Less and PostCSS were added to give developers a choice of whether to build styles purely in React / JavaScript, or whether to defer to a #css #preprocessor. This is especially useful for interop with UI frameworks like Bootstrap, Semantic UI, Foundation, etc - ReactQL lets you mix and match #css and renders to both a static .css file during bundling as well as generates per-page <style> tags when using #StyledComponents.

      React Router handles routing, because it works both on the server and in the client. ReactQL customises it further by capturing non-200 responses on the server, redirecting or throwing back custom 404 pages as needed.

      Koa is the web server that handles all incoming HTTP requests, because it's fast (TTFB < 5ms, even after fully rendering React), and its natively #async, making it easy to async/await inside routes and middleware.

      See more
      Hampton Catlin
      Hampton Catlin
      VP of Engineering at Rent The Runway | 4 upvotes 189.4K views
      atRent the RunwayRent the Runway
      Sass
      Sass
      PostCSS
      PostCSS
      styled-components
      styled-components

      We use Sass because I invented it! No, that's not a joke at all! Well, let me explain. So, we used Sass before I started at Rent the Runway because it's the de-facto industry standard for pre-compiled and pre-processed CSS. We do also use PostCSS for stuff like vendor prefixing and various transformations, but Sass (specifically SCSS) is the main developer-focused language for describing our styling. Some internal apps use styled-components and @Aphrodite, but our main website is allllll Sassy. Oh, but the non-joking part is the inventing part. /shrug

      See more
      Interest over time
      Reviews of PostCSS and Sass
      No reviews found
      How developers use PostCSS and Sass
      Avatar of Mick Dekkers
      Mick Dekkers uses PostCSSPostCSS

      PostCSS essentially allows you to set up your own CSS preprocessor with the features that matter to you. It has a modular plugin-based architecture, which means that if someone comes up with a useful new feature, you can easily add it to your stack as a PostCSS plugin. PreCSS and PostCSS-cssnext are some of my go-to plugins.

      Avatar of Kevin Ard
      Kevin Ard uses SassSass

      It was a little awkward building BS3 with LESS, and the rest of the site with SCSS, but it works. SCSS made building the UI elements (ink/flip buttons, img navs, etc) a breeze. It also drives the mobile menu open/close transitions - that would have been much too much with vanilla css.

      Avatar of Tim Lucas
      Tim Lucas uses PostCSSPostCSS

      PostCSS handles compiling node-based CSS libraries, including BassCSS (the whole site is only ~85 lines of custom CSS). It also does auto-vendor-prefixing and support for CSS variables.

      Avatar of Climate CoLab
      Climate CoLab uses SassSass

      Sass helps us write better stylesheets. One major improvement over CSS that we use a lot is variables - it allows for much easier theming to quickly change brand colors for new instances of the xCoLab.

      Avatar of Ujjwal Bhujel
      Ujjwal Bhujel uses SassSass

      When you realise that countless lines of CSS codes could be made countable. And off course, a wonderful and cool way to use the logic behind variables and nesting. Simply love it.

      Avatar of Scrayos UG (haftungsbeschr盲nkt)
      Scrayos UG (haftungsbeschr盲nkt) uses SassSass

      Sass is used as a part of Woltlab Suite Core, which offers to submit/configure own styles via the injection of own Sass-CSS. So we exclusively rely on Sass for our CSS needs.

      Avatar of Refractal
      Refractal uses SassSass

      CSS is a mess. There, we said it. Sass, on the other hand takes CSS and makes it pretty, easy to work with and has stuff like variables which make things seriously awesome.

      Avatar of Virtually(Creative)
      Virtually(Creative) uses PostCSSPostCSS

      Used to minify and extend the CSS markup of the framework.

      Avatar of BookAuthority
      BookAuthority uses PostCSSPostCSS

      We use PostCSS to improve cross-browser compatibility

      Avatar of Sunny Singh
      Sunny Singh uses PostCSSPostCSS

      Compiles future CSS.

      How much does PostCSS cost?
      How much does Sass cost?
      Pricing unavailable
      Pricing unavailable
      News about PostCSS
      More news