Tailwind CSS End of Life (EOL) Dates & Support Timeline
Complete end-of-life dates, support windows, and security status for all Tailwind CSS versions. Data sourced from endoflife.date and official vendor documentation. Updated at every deploy.
| Version | Latest Release | Release Date | EOL Date | Days | Status |
|---|---|---|---|---|---|
| 1.0 | 1.0.6 | May 13, 2019 | Aug 6, 2019 | 2513 days past EOL | EOL |
| 1.1 | 1.1.4 | Aug 6, 2019 | Feb 5, 2020 | 2330 days past EOL | EOL |
| 1.2 | 1.2.0 | Feb 5, 2020 | Apr 20, 2020 | 2255 days past EOL | EOL |
| 1.3 | 1.3.5 | Apr 20, 2020 | Apr 29, 2020 | 2246 days past EOL | EOL |
| 1.4 | 1.4.6 | Apr 29, 2020 | Jul 15, 2020 | 2169 days past EOL | EOL |
| 1.5 | 1.5.2 | Jul 15, 2020 | Jul 28, 2020 | 2156 days past EOL | EOL |
| 1.6 | 1.6.3 | Jul 28, 2020 | Aug 18, 2020 | 2135 days past EOL | EOL |
| 1.7 | 1.7.6 | Aug 18, 2020 | Sep 4, 2020 | 2118 days past EOL | EOL |
| 1.8 | 1.8.13 | Sep 4, 2020 | Oct 12, 2020 | 2080 days past EOL | EOL |
| 1.9 | 1.9.6 | Oct 12, 2020 | Nov 18, 2020 | 2043 days past EOL | EOL |
| 2.0 | 2.0.5 | Nov 18, 2020 | Apr 5, 2021 | 1905 days past EOL | EOL |
| 2.1 | 2.1.4 | Apr 5, 2021 | Jun 17, 2021 | 1832 days past EOL | EOL |
| 2.2 | 2.2.19 | Jun 17, 2021 | Dec 9, 2021 | 1657 days past EOL | EOL |
| 3.0 | 3.0.24 | Dec 9, 2021 | Jun 8, 2022 | 1476 days past EOL | EOL |
| 3.1 | 3.1.8 | Jun 8, 2022 | Oct 19, 2022 | 1343 days past EOL | EOL |
| 3.2 | 3.2.7 | Oct 19, 2022 | Mar 28, 2023 | 1183 days past EOL | EOL |
| 3.3 | 3.3.7 | Mar 28, 2023 | Dec 18, 2023 | 918 days past EOL | EOL |
| 3.4 | 3.4.19 | Dec 18, 2023 | Feb 28, 2027 | 250 days remaining | Active |
| 4.0 | 4.0.17 | Jan 21, 2025 | Apr 1, 2025 | 448 days past EOL | EOL |
| 4.1 | 4.1.18 | Apr 1, 2025 | Feb 18, 2026 | 125 days past EOL | EOL |
| 4.2 | 4.2.4 | Feb 18, 2026 | May 8, 2026 | 46 days past EOL | EOL |
| 4.3 | 4.3.1 | May 8, 2026 | TBD | Supported | Active |
What does Tailwind CSS end of life mean for your organization?
When a version of Tailwind CSS reaches end of life, the maintainers stop issuing security patches. Vulnerabilities discovered after this date are publicly disclosed on the National Vulnerability Database, exploit code appears on GitHub, and your systems remain permanently exposed.
The CVE blind spot: Most vulnerability scanners check for known CVEs but do not flag the accumulation of unpatched vulnerabilities in EOL software. With a zero-day, nobody knows about the vulnerability. With EOL software, the vulnerability is public — listed, rated, and often weaponized — but no patch will ever exist. This is the most dangerous gap in enterprise security posture.
Organizations running EOL Tailwind CSS should treat it as a vulnerability class in their risk register, apply compensating controls (network segmentation, enhanced monitoring, access restriction), and prioritize migration to a supported version.
Extended Support Options
If you cannot migrate immediately, extended support vendors provide continued security patches for EOL Tailwind CSS versions. This is a bridge, not a permanent solution — plan your migration in parallel.
We work with vetted extended support vendors. Tell us what you need and we'll connect you with the right provider.
Contact Us →