# Tailwind v4 in production: three months in

What we love, what bit us, and the CSS-first migration we'd recommend.

![Designer color palette](https://images.ctfassets.net/vn734mok6jmo/seed-blog-3/cfe7b24df8b161dd4b908836f5d4479d/seed-blog-3.jpg)

Tailwind v4 removed the JS config and moved theme tokens into CSS via @theme. The migration took us a weekend and reduced our build pipeline complexity meaningfully.

The wins: faster builds, simpler tooling, and design tokens live next to component CSS instead of in a separate config file. The pain: any custom plugin had to be rewritten as a CSS @plugin import.

Three months in, we wouldn't go back. Even our designers like it — they can read globals.css.

**READ MORE**

## Get articles like this in your inbox

Engineering essays on content platforms, React, and the modern web. One email a month.