PostCSS Guides
Eight in-depth articles on how PostCSS works, its name and history, configuration, webpack and Tailwind integration, the latest version and security.
Start here · BasicsWhat Does PostCSS Stand For?
PostCSS is not an acronym. Learn where the name came from, why “post” was chosen, how the project began with Autoprefixer, and what PostCSS means today.
Read the guide
ReleasesWhat Is the Latest Version of PostCSS?
The latest PostCSS version is 8.5.32, released October 26, 2026. See how to check your installed version, update safely and read official release notes.
Read guide →
ConceptsHow Does PostCSS Work?
A clear walkthrough of how PostCSS works: tokenizer, parser, the CSS AST, the plugin visitor API, the stringifier, source maps and how build tools run it.
Read guide →
ConceptsWhat Is the Meaning of “Post” in CSS?
“Post” in CSS tooling means work done after CSS is written. Learn pre- vs post-processing, where PostCSS fits, and why the line between them has blurred.
Read guide →
ConfigurationPostCSS Config File: A Complete Guide
How to write a PostCSS config: postcss.config.js, .cjs, .mjs, .ts, .postcssrc and package.json formats, plugin options, environment-based configs and fixes.
Read guide →
Build toolsPostcss-loader: Using PostCSS with webpack
Set up postcss-loader 8 with webpack 5: install, loader order, postcssOptions, Sass, CSS Modules, source maps, requirements and common error fixes.
Read guide →
IntegrationsPostCSS and Tailwind CSS: Setup Guide
How to use Tailwind CSS with PostCSS: install @tailwindcss/postcss, write the config, import Tailwind, migrate from v3 and fix the most common errors.
Read guide →
SecurityPostCSS Vulnerability: CVE-2023-44270 Explained
CVE-2023-44270 is a medium-severity PostCSS line-return parsing issue fixed in 8.4.31. Learn who is affected, how to check your project and how to fix it.
Read guide →