Tailwind CSS had only 6 months left to survive, yet it's one of the most successful styling frameworks in web development history.
The irony isn't lost on me. AI has been quietly disrupting businesses left and right, and I was among the first casualties. My blog, which pulled 1 million views a year, took a nosedive to barely 10,000 views since most of the code snippets I shared would now be readily generated by AI in seconds.
Now in 2025 through to 2026, we're watching the same pattern play out.
But this post isn't about my AI woes. It's about Tailwind, which is facing something far more devastating than what hit my content site.
Adam Wathan, Tailwind's creator, dropped a bombshell recently on X.
Despite the framework seeing explosive growth, his company had to lay off 75% of its engineering team. Three out of four engineers are gone since the revenue has gone down 80%.
Tailwind's npm downloads hit 75 million per month in early 2025. The framework is more popular than it's ever been.
AI coding assistants like Cursor, v0, and Claude default to Tailwind for every project.
If you're building anything with AI right now, there's a near-guarantee you're using Tailwind CSS.
You have probably seen most of my AI coding projects. I often use Tailwind CSS and Typescript.
So how does the most successful CSS framework in the world end up with only six months of runway?
The answer reveals something far bigger than Tailwind's survival.
It exposes a fundamental problem in how the entire web ecosystem works, and why the AI might destroy the very tools that make it possible.
AI is both Tailwind's biggest success driver and its killer.
In 2025, AI coding assistants exploded.
Tools like Cursor, Claude, ChatGPT, and specialized builders like v0 and Lovable became the default way developers write code.
And these AI tools have a favorite stack: TypeScript, React, Next.js, and Tailwind.
Every time you prompt an AI to "build a landing page" or "create a dashboard," it reaches for Tailwind. The framework's utility-first approach translates to how AI thinks about styling. It's predictable, well-documented, and produces consistent results.
This pushed Tailwind's downloads from 6 million to 32 million per month in 2024 alone. Usage skyrocketed.
But on the contrary, AI is destroying the business model that funds its development.
If you prefer to listen to the original podcas,t here is the post below but the article summarizes what you should know.
Tailwind Business Problems Created By AI
- Documentation traffic disappeared
Before AI, the flow was simple. You needed to know how to use Tailwind classes or set up theming, so you'd Google it and land on Tailwind's docs.
You'd bookmark it, return constantly, and while there, you'd notice Tailwind UI, their paid component library.
Traffic to the docs is down 40% from early 2023 despite the framework being more popular than ever — the usage up, visitors down.
2. AI writes the code directly
Developers don't even need to understand Tailwind anymore.
You describe what you want, and Cursor or v0 generates complete components with proper Tailwind classes, responsive breakpoints, and dark mode variants.
The AI already consumed all of Tailwind's documentation during training. It knows the framework inside out. When developers get stuck, they don't visit tailwindcss.com, they ask their AI assistant.
The old business model was: free framework drives traffic to paid products. Developers learn Tailwind through the docs, discover Tailwind UI and Catalyst, and some percentage converts to customers.
AI severed that connection completely. Developers use Tailwind more than ever, but never see the products that fund its development. The funnel is broken, and with it, 80% of Tailwind Labs' revenue vanished.
Tailwind Business Model
To understand this disruption, you need to understand how Tailwind made money.
Tailwind CSS itself is free and open source. Always has been. But the company behind it, Tailwind Labs, sells premium products: Tailwind UI (pre-built components), Catalyst (their official component library), and Refactoring UI (a design book).
The strategy was brilliant in the pre-AI era.
Developers would visit the docs to learn Tailwind, and while browsing, they'd discover these paid products.
Some percentage would convert. The framework was the marketing engine for the commercial products.
The llms.txt Controversy
Last November, a contributor opened a pull request to add an llms.txt endpoint to Tailwind's documentation.
This would make it even easier for AI agents to read and understand Tailwind's docs, improving the code they generate.
Adam declined it with brutal honesty: "I have more important things to do like figure out how to make enough money for the business to be sustainable right now."
He explained that making it easier for LLMs to read their docs means less traffic to their website, which means fewer people discovering their paid products. The business becomes even less sustainable.
Adam remarked : "75% of the people on our engineering team lost their jobs yesterday because of the brutal impact AI has had on our business."
Free Alternative Problem
Another problem is that free component libraries like shadcn/ui, daisyUI, and HyperUI have exploded in popularity.
These offer what Tailwind UI sells, except completely free and open source. Shadcn/ui in particular has become the default choice for developers building with AI.
It's built on Tailwind, offers beautiful components, and costs nothing.
For many developers who couldn't afford Tailwind UI's subscription, Shadcn became the obvious alternative.
This is Not Just Tailwind's Problem
If you think this is just about one CSS framework, you're missing the bigger picture.
This same pattern is playing out across every business that depends on people visiting their content.
Think about all the tools and frameworks you use. React, Vue, Angular, Node.js, Python libraries, AWS services. Every single one has documentation that developers used to visit.
Now? We ask ChatGPT or Claude. We prompt Cursor to explain an API. We let AI generate the implementation without ever reading the source docs.
I use Context7 MCP, among others, to ensure my AI coding stays up to date without ever reading the docs.
AI companies scraped the entire internet to train their models.
They consumed documentation, tutorials, Stack Overflow answers, blog posts, and GitHub repos without asking permission or paying anyone.
Now they sell access to that knowledge through $20/month ChatGPT subscriptions, $200/month Claude Pro plans, and enterprise contracts worth millions.
Meanwhile, the people who created the original content watch their traffic collapse.
I can feel the same pains. I deleted a blog that was 10 years old, with nearly 2000 coding tutorials, since it was no longer useful, I could not keep up maintaining it and chatting with AI bots in the comments.
Bootstrap, once powering 27% of all websites, is facing the same decline.
Material UI, Chakra UI, and every CSS framework company should be preparing for the same reality.
This isn't limited to dev tools. News sites, educational platforms, recipe blogs, how-to guides — any business that relied on search traffic to drive discovery is watching AI demolish their funnel.
What "Abandonware" Means
When Adam mentioned that Tailwind could become "abandonware," he wasn't being dramatic.
Without sustainable revenue, open source projects die. Not immediately, but gradually. First, new features stop shipping. Then bug fixes slow down. Security updates get delayed. Eventually, the maintainers move on to jobs that pay their bills.
The irony is that the more successful an open source project becomes, the more expensive it is to maintain.
Tailwind's 75 million monthly downloads mean millions of developers depending on it, which means more support requests, more edge cases, more complexity, and more hours needed to keep it running.
You can't sustain that with GitHub sponsors and good vibes.
The AI companies building billion-dollar businesses on top of free tools aren't going to fix this problem. They've already extracted the value they need.
They trained their models on Tailwind's documentation, and they'll keep generating Tailwind code whether Tailwind Labs exists or not.
Final Thoughts
I wish I had a clean solution to offer here. I don't.
What I do have is a reality check: the web ecosystem we've relied on for the past two decades is breaking, and we're all going to feel it.
The business model of "free content drives traffic to paid products" is dead. AI killed it.
We're going to see more paywalls, more subscription services, and more tools that simply shut down because they can't figure out monetization in the AI era. The open source ecosystem that gave us incredible tools for free was subsidized by a traffic economy that no longer exists.
Tailwind might be first, but it won't be last.
Let's Connect!
If you are new to my content, my name is Joe Njenga
Join thousands of other software engineers, AI engineers, and solopreneurs who read my content daily on Medium and on YouTube where I review the latest AI engineering tools and trends. If you are more curious about my projects and want to receive detailed guides and tutorials, join thousands of other AI enthusiasts in my weekly AI Software engineer newsletter
If you would like to connect directly, you can reach out here:
Follow me on Medium | YouTube Channel | X | LinkedIn