Tailwind CSS v4: What's New and Should You Migrate?

Tailwind CSS v4 is faster, leaner, and configured differently. Here's whether the migration is worth it.

Tailwind CSS v4 was a significant release — a rewritten engine, a new configuration approach, and a closer alignment with modern CSS. If you're on v3 and weighing an upgrade, or choosing a CSS approach for a new project, you need to know what actually changed, what breaks, and whether the migration earns the effort. Having worked with Tailwind across this transition, here's the practical breakdown.

What's new in Tailwind CSS v4

The headline change is the engine: v4 is dramatically faster at building your styles, which matters for developer experience on large projects where the old build step could drag. Alongside that, the biggest structural shift is configuration. Tailwind v4 moves toward a CSS-first configuration model — you configure your design tokens and theme directly in CSS using native custom properties, rather than primarily through a JavaScript config file.

This aligns Tailwind with where the web platform has gone. It leans on native CSS custom properties, cascade layers, and modern features that browsers now support well, rather than reimplementing them in tooling. The result is a system that feels more like writing modern CSS and less like a separate abstraction layer sitting on top of it. For developers comfortable with CSS custom properties, it's a more natural fit.

What breaks when you migrate

The move from JavaScript-based config to CSS-first config is the main migration work. If you have an extensively customised v3 config — custom colours, spacing scales, plugins, and theme extensions — you'll need to translate those into the new approach. For a lightly customised project, this is quick; for a heavily themed one, it's a focused piece of work, not a five-minute upgrade.

Beyond config, expect some class-name and behaviour changes that the upgrade tooling helps with but won't catch entirely, and check any plugins you depend on for v4 compatibility. As with any major version, the safe approach is to upgrade on a branch, run the official upgrade tooling, then visually review the site across breakpoints and themes — automated tools handle the mechanical changes, but a human needs to confirm nothing shifted visually.

Should you migrate?

For new projects in 2026, start on v4 — there's no reason to begin on the older version, and you get the faster engine and the cleaner config model from day one. The CSS-first approach also pairs well with a design-token strategy, since your tokens live as native CSS custom properties.

For existing v3 projects, the calculus is the usual one for major upgrades. If your project is actively developed and you'll benefit from the faster builds and modern config, migrate — but schedule it deliberately, on a branch, with time to review. If your project is stable, lightly maintained, and v3 is serving you fine, there's no urgency; upgrade when you're next doing significant work on it rather than as a standalone task. Don't migrate purely to be current — migrate when the benefits apply to your situation.

Key takeaways for businesses

• Tailwind v4 brings a much faster build engine and a CSS-first configuration model that aligns with modern, native CSS features.
• The main migration work is translating JavaScript config into the new CSS-first approach — quick for lightly customised projects, a focused task for heavily themed ones.
• Use v4 for new projects; for existing v3 apps, migrate deliberately when you'll benefit from it, not just to stay current.

Frequently Asked Questions

What's new in Tailwind CSS v4?

Tailwind v4 features a rewritten, much faster build engine and a CSS-first configuration model where you define your theme and tokens in CSS using native custom properties, rather than primarily in a JavaScript config file. It aligns closely with modern CSS features like cascade layers.

Is it hard to migrate from Tailwind v3 to v4?

The main work is translating your JavaScript-based configuration into the new CSS-first approach. For lightly customised projects it's quick; for heavily themed ones it's a focused task. Use the official upgrade tooling on a branch and review the site visually afterwards.

Should I use Tailwind v4 for a new project?

Yes. For new projects there's no reason to start on an older version — you get the faster engine and cleaner configuration immediately, and the CSS-first model pairs well with a design-token approach using native custom properties.

Modernising your styling or starting fresh?

I build maintainable, token-driven front-ends with Tailwind and modern CSS. If you want your styling done right, let's talk.