← ← Back to all products
All badges & lifecycle API →
Tailwind CSSEnd of Life (EOL) Dates & Support Status
Active
Libraries & SDKsLatest Version: 4.3.3Latest Release: Jul 16, 2026
Tailwind CSS is a utility-first CSS framework for rapidly building custom user interfaces.
Support summary
Tailwind CSS currently has supported cycles. Track the next EOL date and validate upgrades before your change window.
What do EOL and support statuses mean?Next EOL
Feb 28, 2027
Tailwind CSS 3.4 · 154 days left
Supported cycles
2
0 lts
Versions
22
Latest Version
4.3.3
Active Support
2
EOL
20
Lifecycle Timeline
Jun 17, 2021As of Sep 27, 2026
4.3Active · Date not announced
4.2EOL · May 8, 2026
4.1EOL · Feb 18, 2026
4.0EOL · Apr 1, 2025
3.4Active · Feb 28, 2027
3.3EOL · Dec 18, 2023
3.2EOL · Mar 28, 2023
3.1EOL · Oct 19, 2022
3.0EOL · Jun 8, 2022
2.2EOL · Dec 9, 2021
ActiveSecurityEOLHistorical phase unknown
Bars show history up to the snapshot date. Gray intervals lack dated support boundaries; arrows indicate an unannounced EOL date, not a support guarantee.
Versions
| Release | Release Date | Active Support | EOL | Latest Version | LTS | Status |
|---|---|---|---|---|---|---|
| 4.3 | May 8, 2026 | Maintained | Date not announced | 4.3.3 | No | Active |
| 4.2 | Feb 18, 2026 | Ended | May 8, 2026 | 4.2.4 | No | EOL |
| 4.1 | Apr 1, 2025 | Ended | Feb 18, 2026 | 4.1.18 | No | EOL |
| 4.0 | Jan 21, 2025 | Ended | Apr 1, 2025 | 4.0.17 | No | EOL |
| 3.4 | Dec 18, 2023 | Maintained | Feb 28, 2027 | 3.4.19 | No | Active |
| 3.3 | Mar 28, 2023 | Ended | Dec 18, 2023 | 3.3.7 | No | EOL |
| 3.2 | Oct 19, 2022 | Ended | Mar 28, 2023 | 3.2.7 | No | EOL |
| 3.1 | Jun 8, 2022 | Ended | Oct 19, 2022 | 3.1.8 | No | EOL |
| 3.0 | Dec 9, 2021 | Ended | Jun 8, 2022 | 3.0.24 | No | EOL |
| 2.2 | Jun 17, 2021 | Ended | Dec 9, 2021 | 2.2.19 | No | EOL |
| 2.1 | Apr 5, 2021 | Ended | Jun 17, 2021 | 2.1.4 | No | EOL |
| 2.0 | Nov 18, 2020 | Ended | Apr 5, 2021 | 2.0.5 | No | EOL |
| 1.9 | Oct 12, 2020 | Ended | Nov 18, 2020 | 1.9.6 | No | EOL |
| 1.8 | Sep 4, 2020 | Ended | Oct 12, 2020 | 1.8.13 | No | EOL |
| 1.7 | Aug 18, 2020 | Ended | Sep 4, 2020 | 1.7.6 | No | EOL |
| 1.6 | Jul 28, 2020 | Ended | Aug 18, 2020 | 1.6.3 | No | EOL |
| 1.5 | Jul 15, 2020 | Ended | Jul 28, 2020 | 1.5.2 | No | EOL |
| 1.4 | Apr 29, 2020 | Ended | Jul 15, 2020 | 1.4.6 | No | EOL |
| 1.3 | Apr 20, 2020 | Ended | Apr 29, 2020 | 1.3.5 | No | EOL |
| 1.2 | Feb 5, 2020 | Ended | Apr 20, 2020 | 1.2.0 | No | EOL |
| 1.1 | Aug 6, 2019 | Ended | Feb 5, 2020 | 1.1.4 | No | EOL |
| 1.0 | May 13, 2019 | Ended | Aug 6, 2019 | 1.0.6 | No | EOL |
Data sources
Sources
Embed this badge
Show Tailwind CSS's live support status in your README, docs, or dashboard. The badge is a static SVG served from eol.wiki and follows the lifecycle data above.
Markdown
[](https://eol.wiki/tailwind-css/)HTML
<a href="https://eol.wiki/tailwind-css/"><img src="https://eol.wiki/badge/tailwind-css.svg" alt="Tailwind CSS end-of-life status" height="20"></a>Frequently Asked Questions
Which versions of Tailwind CSS have reached end of life?
The following Tailwind CSS versions have reached end of life and no longer receive security updates: 4.2, 4.1, 4.0, 3.3, 3.2, 3.1, 3.0, 2.2 (and 12 more). It is recommended to upgrade to a supported version.
Is it safe to continue using Tailwind CSS 4.2?
Tailwind CSS 4.2 has reached end of life and no longer receives security patches or bug fixes. Continuing to use it may expose your systems to known vulnerabilities. We strongly recommend upgrading to a supported version.
What is the latest version of Tailwind CSS?
The latest version of Tailwind CSS is 4.3.3, released in the 4.3 release cycle.
How many versions of Tailwind CSS are currently supported?
Tailwind CSS currently has 2 actively supported version(s): 4.3, 3.4.
When does Tailwind CSS 4.3 reach end of life?
Tailwind CSS 4.3 does not have a specific end-of-life date announced yet.
What should I do when Tailwind CSS reaches end of life?
When a Tailwind CSS version reaches end of life, you should: 1) Plan your migration to a supported version as soon as possible. 2) Review the release notes for breaking changes. 3) Test your applications thoroughly in a staging environment. 4) Update your dependencies to ensure compatibility with the new version.