porro

End of life  /  Tailwind CSS

Release cycles

Tailwind CSS end of life

2 cycles are supported, 4.3 to 3.4. 3.4 gets security fixes until 28 Feb 2027. Active support means bug fixes and security fixes; after it, security fixes only.

  1. 4.3
  2. 4.2
  3. 4.1
  4. 4.0
  5. 3.4
  • Active support
  • Security fixes only
  • Supported
  • Ends within 90 days
  • Ended
4.3 Supported no date yet 4.3.3 4.2 Ended until 8 May 2026 4.2.4 4.1 Ended until 18 Feb 2026 4.1.18 4.0 Ended until 1 Apr 2025 4.0.17 3.4 Supported until 28 Feb 2027 3.4.19 3.3 Ended until 18 Dec 2023 3.3.7 3.2 Ended until 28 Mar 2023 3.2.7 3.1 Ended until 19 Oct 2022 3.1.8 3.0 Ended until 8 Jun 2022 3.0.24 2.2 Ended until 9 Dec 2021 2.2.19 2.1 Ended until 17 Jun 2021 2.1.4 2.0 Ended until 5 Apr 2021 2.0.5 1.9 Ended until 18 Nov 2020 1.9.6 1.8 Ended until 12 Oct 2020 1.8.13 1.7 Ended until 4 Sep 2020 1.7.6 1.6 Ended until 18 Aug 2020 1.6.3 1.5 Ended until 28 Jul 2020 1.5.2 1.4 Ended until 15 Jul 2020 1.4.6 1.3 Ended until 29 Apr 2020 1.3.5 1.2 Ended until 20 Apr 2020 1.2.0 1.1 Ended until 5 Feb 2020 1.1.4 1.0 Ended until 6 Aug 2019 1.0.6

How to check your version

Which Tailwind CSS is this site on?

In the lock file

$ npm ls tailwindcss
# package-lock.json is what deploys

In the built CSS

$ head -c 120 public/build/assets/app-*.css
/*! tailwindcss v4.3.3 | MIT License | https://tailwindcss.com */
# the banner names the version that built it

Know before support ends.

Porro reads the PHP, framework and database version from every site and tells you 90 days before support runs out.

Start your free trial →

Dates from endoflife.date/tailwind-css, checked daily · data as of 29 Oct 2026.