Tailwind CSS Release History & EOL Status

How Does Tailwind CSS Handle Version Support?

In practice, Tailwind follows a rolling support model: when a new minor or patch release ships, the previous one is effectively superseded. There is no official, published end-of-life policy document from Tailwind Labs.

Only the latest release within the current major branch receives active bug fixes and new features. The previous major version has been acknowledged by the team as still maintained -- specifically, the last stable minor in that line continues to receive fixes as long as there is a significant portion of the ecosystem that cannot migrate due to browser compatibility constraints.

The key driver behind this informal exception is the CSS @property rule, which v4 depends on for core behavior. Teams targeting older browsers are effectively unable to upgrade, and Tailwind Labs has recognized this by continuing to ship patches to the previous major. This is not a formal LTS commitment -- it is a pragmatic response to ecosystem reality.

The support status for each branch is shown in the release table above. If the Support status column shows "Active" or "Supported," that branch is receiving updates. Anything marked "End of Life" or "Unsupported" is no longer patched.

References: Tailwind CSS Upgrade Guide -- Tailwind CSS Compatibility Docs

What Can Go Wrong When You Stay on an Unsupported Tailwind Version?

Running an unsupported Tailwind version is a dependency drift problem more than a security problem -- CSS frameworks do not carry CVEs the way server-side runtimes do.

The real risks are toolchain breakage. Tailwind integrates tightly with Vite, PostCSS, and framework-specific plugins. When those tools release major updates, the Tailwind team ships compatibility fixes -- but only for supported versions. If you are pinned to an old release, plugin APIs can silently break, build times can regress, and class detection can produce incorrect output without any warning.

Common friction points on unsupported branches

In practice, teams that freeze Tailwind while upgrading everything else around it accumulate a compounding compatibility debt. The CSS output keeps working in the browser -- but the build pipeline becomes progressively harder to maintain.

What Happens After a Tailwind Version Reaches End of Life?

After a Tailwind version is superseded, the GitHub repository stops accepting bug reports for it, and pull requests targeting old branches are closed without review. There are no backported fixes.

Your existing CSS output does not stop working. Tailwind compiles to static CSS -- there is no runtime, no server, no license server. A build that worked yesterday continues to produce the same output tomorrow. The risk is not that your site breaks immediately; it is that your build toolchain eventually breaks when surrounding dependencies move forward without you.

The community ecosystem -- Tailwind plugins, UI kits, design system packages -- tends to drop old version support quickly because the framework moves fast. Most plugin authors target the latest release within weeks of a new minor landing.

Migration direction

Tailwind Labs ships an official CLI upgrade tool that automates the majority of the migration between major versions. It handles configuration file conversion, utility renames, and deprecated syntax. For teams on the previous major version who cannot adopt the current major due to browser support requirements, the recommended path is to stay on the latest patch of the previous major and track the compatibility roadmap from Tailwind Labs.

Reference: Official Upgrade Guide and automated migration tool

How To Check Your Tailwind CSS Version

Run the following command in your project root to see the installed version:

npx tailwindcss --version

If you are using a package manager, you can also inspect your lockfile or query the installed package directly:

# npm
npm list tailwindcss

# yarn
yarn list --pattern tailwindcss

# pnpm
pnpm list tailwindcss

The version number in your package.json may show a range like ^3.4.0 or ^4.3.0 -- the actual installed version is in package-lock.json or your lockfile. Always compare the installed version against the Support status column in the release table above to confirm you are on a supported branch.

To check which version of the Tailwind CLI is globally installed (if applicable):

tailwindcss --version

If you are using the Vite plugin or PostCSS plugin rather than the CLI, the version is determined by the tailwindcss package in your node_modules -- the npm list command above is the most reliable check.