
The current release
The latest stable release of PostCSS is 8.5.32, published to npm on October 26, 2026. We confirmed this on November 9, 2026 in two places: the npm registry entry for the postcss package and the 8.5.32 tag in the official GitHub repository.
| Field | Value |
|---|---|
| Latest version | 8.5.32 |
| Published | October 26, 2026 |
| License | MIT |
| Node.js engines | ^10 || ^12 || >=14 |
| Dependencies | nanoid, picocolors, source-map-js |
| Unpacked size | About 216 KB |
Version numbers change often, so treat this page as a snapshot. The commands below always show the live answer.
Recent release history
PostCSS is in its 8.x major line. Version 8.0 arrived in September 2020, and since then releases have been backwards-compatible minors and patches. The project ships small patch releases frequently. The last few versions on npm were:
| Version | Published |
|---|---|
| 8.5.32 | October 26, 2026 |
| 8.5.31 | October 18, 2026 |
| 8.5.30 | October 12, 2026 |
| 8.5.29 | October 5, 2026 |
| 8.5.28 | September 3, 2026 |
We do not reproduce the changelog here, because the official notes are the only reliable record. Read them on the GitHub releases page.
How to check the latest version yourself
Ask npm directly. This prints the version tagged latest on the registry:
npm view postcss versionTo see every published version with dates:
npm view postcss time --jsonHow to see which version your project uses
Your project can contain more than one copy of PostCSS, because some tools depend on it too. List them all with:
npm ls postcssThe output is a tree. The top-level entry is the version you installed; nested entries belong to other packages. If you use pnpm or Yarn, the equivalents are pnpm why postcss and yarn why postcss.
Inside JavaScript you can also read the version at runtime:
const postcss = require('postcss')
console.log(postcss().version)How to update to the latest version
- Read the release notes between your version and 8.5.32. Patch releases in 8.x are meant to be safe, but it is good practice to look.
- Update the package:
npm install --save-dev postcss@latest- Update your runner too, for example
postcss-loaderorpostcss-cli, so it does not bring its own older copy. - Rebuild and compare the generated CSS. A quick diff of the output file catches unexpected changes.
- Commit the lockfile so every machine and CI job installs the same version.
Downloading the source of the latest release
If you want the source code rather than an npm install, the home page offers the official 8.5.32 archive from GitHub as .zip and .tar.gz downloads. The archive contains the library source, type definitions and tests. It is not an installer; for project use npm is simpler.
Why staying current matters
- Security: versions before 8.4.31 are affected by CVE-2023-44270. See the PostCSS vulnerability guide.
- Plugin compatibility: modern plugins target the PostCSS 8 API. Very old PostCSS 7 setups cause “requires PostCSS 8” errors.
- Bug fixes: parser fixes for edge cases arrive in patch releases.
Quick answers
Is there a PostCSS 9?
Not at the time of checking. The latest tag on npm points to 8.5.32, in the 8.x line.
Is the latest version free?
Yes. Every version is published under the MIT license.
Does the latest version support my Node.js?
The core declares support for Node.js 10, 12 and 14 or newer. Your other tools may need more, for example postcss-cli 12 requires Node.js 22+.
Get PostCSS 8.5.32
Free, MIT licensed, downloaded from the official GitHub repository.


