Why Tailwind CSS Faces a Growing Problem Developers Didn’t Expect
Explore more reads from Aashish Kumar @ https://hexplain.space/blog
A few engineers losing their jobs does not usually make headlines.
But when a company only has four engineers total and three of them are laid off, something serious is happening.
Adam Wathan, the creator of Tailwind CSS, recently let go of most of his team. Revenue is reportedly down around 80 percent. Not because Tailwind became worse. Not because developers stopped using it.
In fact, the opposite is true.
Tailwind is more popular than ever. Tens of millions of downloads every month. Used by companies like GitHub, Shopify, NASA, and countless startups.
So why are people losing their jobs?
AI.
The Situation Feels Backwards
Imagine building one of the most widely used developer tools in the world. Your framework becomes the default choice for styling modern web apps. Adoption keeps growing.
That should mean stability. It does not.
Traffic to Tailwind’s documentation has dropped sharply since early 2023. Revenue collapsed while usage continued to rise.
Developers used to search for Tailwind solutions online. They would land on the official documentation. They would browse examples. Some would discover Tailwind UI and decide to buy templates.
That discovery funnel paid the people maintaining the framework.
Now developers ask AI tools instead.
Claude, ChatGPT, Cursor, and similar tools generate correct Tailwind code instantly. No documentation visits. No browsing. No template discovery. No purchases.
The framework succeeds. The business behind it shrinks.
Watching the Problem Surface in Public
In early January 2026, someone opened a GitHub pull request suggesting an llms.txt file to make Tailwind documentation easier for AI systems to parse.
Adam closed the request.
He later explained why. Seventy five percent of the engineering team had just lost their jobs due to AI’s impact on the business.
Some accused him of being unfriendly to open source. Others argued that making Tailwind easier for AI would increase adoption.
Adam had to say something uncomfortable out loud.
Making Tailwind easier to consume does not make it easier to sustain.
Every improvement that helps AI tools reduces the remaining connection between usage and revenue.
Why the Numbers No Longer Work
The old model looked like this:
Developer searches for Tailwind components
Lands on the documentation
Discovers Tailwind UI
Buys a lifetime license
That funded development.
The new reality looks like this:
Developer asks an AI to build a dashboard using Tailwind
AI generates production ready code
Developer never visits the docs
Nothing is purchased
The cost of a UI kit now equals the cost of thousands of AI queries.
That is not criticism. It is math.
This Is Bigger Than Tailwind
This problem is not isolated.
Traffic to Stack Overflow continues to decline. Documentation sites across the ecosystem are losing visitors. Projects that relied on tutorials, templates, or paid add ons are seeing the same pattern.
Some tools survive only because a large company or AI lab acquires them. Others scramble to introduce subscriptions users resent.
Next.js survived because Vercel built a hosting business around it. Many projects do not have that option.
AI powered website builders generate massive revenue using open source tools without contributing anything back.
That is not malicious. It is how incentives work today.
Free Components Plus AI Change Everything
There are now many free Tailwind component libraries.
Shadcn UI
daisyUI
HyperUI
Preline
Flowbite
Combined with AI assistants, these are good enough for most products.
The gap between paid templates and AI generated UI is small, and most users do not notice the difference.
The CSS framework ecosystem is not collapsing because the tools are bad.
It is collapsing because the business model no longer works.
The Human Cost
Three engineers lost their jobs in a single day.
Not because they failed.
Not because the product failed.
Because AI became too good at using the thing they built.
The decision was made early so severance and time to recover were possible. Waiting would have meant missing payroll entirely.
It was responsible. It was still painful.
What Happens If This Continues
If projects like Tailwind cannot sustain teams, who builds the next generation of tools?
Open source does not maintain itself. It needs people focused on performance, security, documentation, and community.
Without funding, projects stagnate. Bugs accumulate. Security issues linger. Innovation slows.
AI companies will keep making money.
The tools they rely on will decay.
What You Can Do
If you rely on Tailwind, consider supporting the people behind it. Buy their books. Subscribe to their paid offerings. Ask your company to sponsor the project.
If you run a business, audit your dependencies and support the open source tools you rely on.
Stop assuming open source will always be there.
It is infrastructure. Infrastructure needs funding.
The Reality We Need to Face
AI has removed the conversion path that once supported many developer tools.
People no longer browse. They no longer discover products organically. AI answers questions without sending traffic back.
This is not about hating AI. Most of us use it daily.
It is about acknowledging that when one industry grows rapidly, another can collapse quietly.
Tailwind’s situation is an early warning.
If we do not find new ways to support open source in an AI driven world, many of the tools we depend on will disappear.
Rebuilding them will not be easy.
