Tailwind v4 marks an architectural break from previous versions. CSS-first configuration, new compilation engine, native custom properties integration — what it changes in practice.
Tailwind CSS v4 abandons the JavaScript configuration file (tailwind.config.js) in favor of configuration directly in
CSS. This is an important paradigm shift. Design tokens are now defined with native CSS custom properties in a @theme
directive, making configuration readable in any editor without special tooling. Integration with design tools (Figma
tokens, Style Dictionary) becomes more natural.
The new Oxide engine, rewritten in Rust, delivers considerable performance gains. Compilation times are divided by 5 to 10 depending on project size. In development, HMR is near-instantaneous even on large codebases. Class detection is also smarter — it analyzes generated CSS rather than simply scanning text files.
Other notable additions: CSS Cascade Layers used natively to avoid specificity conflicts, native support for
@starting-style for entry animations, and prefix removal from many utilities. Migration from v3 is facilitated by an
automatic codemod tool, but some manual adjustments remain necessary, especially for color configuration and custom
plugins. A major version worth adopting on new projects today.