tailwindcss vs postcss downloads
tailwindcss took 1.7B downloads in the last 90 days against postcss's 3.8B — 44% of it. postcss leads over the last twelve months, on 10B. postcss has led for the whole of the two records. npm's record for tailwindcss begins on 2017-10-06, and for postcss on 2015-02-27.
| tailwindcss | postcss | |
|---|---|---|
| Last 90 days | 1.7B | 3.8B |
| Last 12 months | 4.1B | 10B |
| All time | 6.1B | 30B |
| Record begins | 2017-10-06 | 2015-02-27 |
| Last 12 months vs the 12 before | 4.72× | 2.20× |
Granularity
Scale
Range
Custom range
Mar 2015 → Sep 2026
| Package | Total | Latest | Peak | |
|---|---|---|---|---|
tailwindcss | 5.8B | 609M | 609M | |
postcss | 30B | 1.4B | 1.4B |
107 monthly periods
Monthly downloads for both, each line starting where that package's own record does.
tailwindcss downloads · postcss downloads · open both in the interactive chart
Also compared
Put this chart in a README
Both series, redrawn from npm's figures whenever the image is fetched, so the comparison stays current on its own.
<img src="https://npmpulse.com/api/svg?q=tailwindcss,postcss&range=5y&granularity=monthly" alt="tailwindcss compared with postcss npm downloads" />Where these numbers come from
Download counts are npm's own, published through its downloads API. They count installs rather than people, so they include CI, mirrors and repeated installs, and a package pulled in as a dependency counts for that package too.
npm's API returns at most 549 days for a single package and 365 when several are compared, and truncates an over-long range rather than refusing it. npmpulse asks for the whole span in 365-day chunks and stitches the answers together, which is what makes a chart that starts in 2015 possible at all.
npm reports 0 for every package from 2015-01-10 until 2015-02-27, when its real records begin; those leading zeros are trimmed rather than charted. Individual days it lost entirely are interpolated, and the most recent day or two, which it has not finalised, is dropped. The monthly figures here are complete calendar months, so a package that started mid-month begins with the following one.
A handful of months are inflated in npm's own figures. svelte's 2022-11-23 records 5.0M downloads against a norm nearer 80K, and November 2022 is a spike in several packages at once; they are left alone here, because they are what the source says, but a one-month jump is treated as a spike rather than as a change of fortune. That is why the comparisons below only call a lead change a lead change when it held for a second month.
A package's record can also begin before the package did: npm names get reused. Where a first day is a handful of downloads, that is what you are looking at — the earlier life of the name rather than a slow launch. Where it is hundreds of thousands, the opposite is true, and what is missing is upstream history rather than usage.
Snapshot of 2026-10-13. Figures run through 2026-10-11.