Tailwind CSSReleasedpatch

Tailwind CSS 4.3.3 is out: highlights and upgrade guide

At a glance

Tailwind CSS 4.3.3 is a patch release published on Jul 16, 2026. It follows Tailwind CSS 4.3.2 by 17 days. It includes 15 listed changes.

  • Support --watch --poll[=ms] in @tailwindcss/cli when filesystem events are unreliable or unavailable
  • Canonicalization: match arbitrary hex colors against theme colors case-insensitively (e.g. bg-[#fff] and bg-[#FFF] → bg-white
  • Prevent Preflight from overriding Firefox's native iframe:focus-visible outline styles
  • Ensure theme('colors.foo') in JS plugins resolves correctly when both --color-foo and --color-foo-bar exist
  • Ensure fractional opacity modifiers work with named shadow sizes like shadow-sm/12.5, text-shadow-sm/12.5, drop-shadow-sm/12.5, and inset-shadow-sm/12.5
Version
4.3.3
Released
Jul 16, 2026
Release type
Patch
Previous
4.3.2
Changes listed
15
License
MIT

How to upgrade to Tailwind CSS 4.3.3

This is a patch release, normally bug fixes only. It is usually safe to upgrade after your tests pass.

npm
npm install [email protected]
pnpm
pnpm add [email protected]

What's included in Tailwind CSS 4.3.3

Details from the official release page.

Fixed

  • Support --watch --poll[=ms] in @tailwindcss/cli when filesystem events are unreliable or unavailable (#20297)
  • Canonicalization: match arbitrary hex colors against theme colors case-insensitively (e.g. bg-[#fff] and bg-[#FFF] → bg-white) (#20298)
  • Prevent Preflight from overriding Firefox's native iframe:focus-visible outline styles (#20292)
  • Ensure theme('colors.foo') in JS plugins resolves correctly when both --color-foo and --color-foo-bar exist (#20299)
  • Ensure fractional opacity modifiers work with named shadow sizes like shadow-sm/12.5, text-shadow-sm/12.5, drop-shadow-sm/12.5, and inset-shadow-sm/12.5 (#20302)
  • Parse selectors like [data-foo]div as two selectors instead of one (#20303)
  • Ensure @tailwindcss/postcss rebuilds when a preprocessor like Sass changes the input CSS without changing the input file on disk (#20310)
  • Ensure CSS nesting is handled even when Lightning CSS isn't run, such as in @tailwindcss/browser and Tailwind Play (#20124)
  • Prevent achromatic theme colors from shifting hue when mixed in polar color spaces like oklch (#20314)
  • Ensure --spacing(0) is optimized to 0px instead of 0 so it remains a ` when used incalc(…)` (#20319)
  • Load @parcel/watcher only when needed in @tailwindcss/cli --watch mode, so one-off builds and --watch --poll work when @parcel/watcher can't be loaded (#20325)
  • Use explicit platform fonts instead of system-ui and ui-sans-serif so CJK text respects the page's lang attribute on Windows (#20318)
  • Prevent @tailwindcss/upgrade from rewriting ignored files when run from a subdirectory (#20329)
  • Ensure earlier @source rules pointing to nested files are scanned when later @source rules point to files in parent folders (#20335)
  • Prevent @tailwindcss/vite from triggering full page reloads when scanned files are processed by Vite but haven't been loaded as modules yet (#20336)

Tailwind CSS 4.3.3 FAQ

When was Tailwind CSS 4.3.3 released?

Tailwind CSS 4.3.3 was published on Jul 16, 2026.

Is Tailwind CSS 4.3.3 a major update?

No. It is a patch release, mainly bug fixes.

How do I upgrade to Tailwind CSS 4.3.3?

Use the commands in the “How to upgrade” section, then run your test suite.

Where are the official Tailwind CSS 4.3.3 notes?

On the project's official release page: https://github.com/tailwindlabs/tailwindcss/releases/tag/v4.3.3

Source: official Tailwind CSS v4.3.3 release. Spotted an error? Tell us.