Companies Using Tailwind CSS

With 10+ years in web crawling and technographic data analysis, I've examined Tailwind CSS's footprint across our dataset of 50M+ domains. This analysis draws on 17,569 enriched company profiles matched to LinkedIn data, plus migration tracking, tech stack overlap, and the fallout from Tailwind Labs' January 2026 crisis. On January 6, 2026, Adam Wathan laid off 3 of the company's 4 engineers after AI tools slashed documentation traffic by 40% and revenue by nearly 80% (source). Within 48 hours, Google AI Studio, Vercel, Lovable, and Supabase stepped in as sponsors. Here's what our independent crawl data reveals as of our March 2026 crawl.

Growth trajectory

Tailwind went from a single detected domain in November 2018 to 215 by end of 2019. Growth then accelerated hard: 974 active domains by December 2020, 4,747 by December 2021, and 9,308 by December 2022. The framework crossed 30,000 in early 2025 and peaked at 34,025 in April 2025.

Our crawl numbers tell only part of the story. Tailwind compiles to plain CSS at build time, so well-optimized production builds strip the utility class patterns our crawler looks for. npm downloads tell a different story: over 30 million weekly as of January 2026, per Rob Mensching. The 2025 State of CSS survey pegged adoption at 51% of surveyed developers. Tailwind v4.0, released January 2025, brought 5x faster full builds and 100x faster incremental builds.

"Our crawl data captures sites where Tailwind classes survive to production HTML. That's the visible fraction. The framework's actual install base, based on npm numbers, is orders of magnitude larger. We're measuring the tip." - Mehmet Suleyman, CEO at TechnologyChecker.io

Sales Signal: The gap between 33,668 detected domains and 30M+ weekly npm downloads means our data captures a subset of real Tailwind users. These are the ones where the framework is detectable in production, making them the most targetable cohort. Use TechnologyChecker.io to find them.

Customer profile

76.68% of Tailwind CSS companies have 1-10 employees. Add the 11-50 range and you hit 88.98%. The age data reinforces this: 40.66% founded in the 2010s, 33.73% in the 2020s. Three-quarters of the user base are companies younger than 15 years.

Enterprise presence is thin but real. We detect 250 companies with 10,001+ employees running Tailwind, including Deloitte, Siemens, JPMorgan Chase, Bloomberg, and the NBA. Tailwind's official showcase at tailwindcss.com/showcase confirms 57 companies, including NASA/JPL, OpenAI, Shopify, Vercel, Supabase, PostHog, and Cursor. Most enterprise detections show up on subdomains (Deloitte's app.disp.deloitte.com, Siemens' status.login-dev.siemens.com), pointing to internal tools rather than org-wide adoption.

Sales Signal: Those 250 companies with 10,001+ employees represent expansion opportunities. They've already approved Tailwind for internal projects. The logical next sell is design systems, component libraries, or developer tooling that builds on their existing Tailwind investment.

Industry and geographic concentration

IT Services (7.51%), Software Development (6.58%), and Technology/Internet (5.81%) together account for nearly 20% of the user base. That's roughly 3x the tech concentration we see for most tracked web technologies, where retail and business services usually dominate. Advertising Services (4.35%) and Business Consulting (3.70%) round out the top five.

The United States leads at 20.8% with 3,654 companies. India at #2 with 1,367 companies isn't a surprise. Large developer workforce, cost-conscious market, strong startup ecosystem. The UK (1,127) is third. Indonesia (243) and Turkey (228) both crack the top 13, flagging fast-growing developer communities that most competitors haven't targeted yet.

Sales Signal: India at #2 with 1,367 companies means strong demand for Tailwind templates, courses, and component libraries priced for that market. The 688 Advertising Services companies are agencies building client work, a segment that buys UI kits at higher rates than solo developers.

Migration patterns

The biggest inbound corridor comes from Materialize CSS: 286 companies switched to Tailwind vs. 115 going the other direction. That's a 2.5:1 gain ratio. Against Semantic UI, the ratio is 1.9:1. Against UIKit, it's nearly 1.1:1, basically a wash.

One sharp outlier: Radix UI. Tailwind gained 47 companies from Radix but lost 189 to it, a 4:1 loss ratio. This looks alarming until you think about it. Radix provides headless, unstyled UI primitives. Developers don't drop Tailwind for Radix. They add Radix to their Tailwind projects. The Shadcn/UI pattern (Radix + Tailwind) is exactly this: behavior from Radix, styling from Tailwind. Chakra UI shows a modest 1.3:1 loss ratio (137 vs 105), pointing to developers who want pre-built styled components.

"The Radix UI migration flow is the most misread signal in our dataset. It's not competitive displacement. It's ecosystem pairing. Shadcn/UI proved that Tailwind and Radix are complements, not substitutes." - Mehmet Suleyman, CEO at TechnologyChecker.io

Sales Signal: The 286 Materialize-to-Tailwind migrants are actively modernizing their frontend. They've made a bet on utility-first CSS. Target them with tooling that accelerates that transition. The 70 companies that left Chakra for Tailwind in the past year are another high-intent cohort.

Technology ecosystem

Cloudflare Hosting leads at 26.53%, nearly 3x Hostinger (8.01%) and well ahead of OVH (5.51%) and Hetzner (5.14%). Alpine.js leads the JavaScript framework overlap at 5.68%. Both tools share a "write it in the HTML" philosophy, so the pairing makes sense. AngularJS (3.71%) and Vue v2 (3.34%) also appear, likely reflecting legacy projects that added Tailwind incrementally.

CMS usage is strikingly low. Atlassian Cloud leads at just 2.03%, with Drupal at 1.22% and Wix at 1.04%. This confirms the ICP: Tailwind users build custom. They don't customize WordPress themes. They write markup from scratch.

Sales Signal: The Alpine.js overlap (997 companies) flags a specific builder persona: developers who prefer minimal tooling and HTML-centric workflows. Low CMS numbers mean this audience buys starter kits, component libraries, and design systems, not page builders or themes.

The AI paradox

In January 2026, Tailwind Labs cut 75% of its engineering team after documentation traffic fell 40% and revenue dropped nearly 80%. AI coding tools (Cursor, Copilot, ChatGPT) generate Tailwind code directly. Developers get answers without visiting tailwindcss.com, which means they never see the link to Tailwind Plus (the paid product). Usage is at an all-time high. Revenue collapsed.

As Adam Wathan put it: "75% of the people on our engineering team lost their jobs here yesterday because of the brutal impact AI has had on our business." Within 48 hours, 34 corporate partners pledged $5,000/month each, with Google AI Studio, Vercel, Lovable, Gumroad, and Supabase among the sponsors (source).

Sales Signal: This crisis signals a structural change in developer tool monetization. Companies that depend on Tailwind in their stack should now consider sponsorship as infrastructure investment. The 34 corporate partners at $5,000/month represent companies who understand that free tooling isn't free to maintain.

Key takeaways

1. Tailwind holds 33,668 detected active domains, but build-time compilation makes this a floor estimate. npm downloads (30M+ weekly) and the State of CSS survey (51% adoption) suggest far wider real usage.

2. The customer base is 76.68% companies with 1-10 employees and 74.39% founded after 2010. Young, small, developer-led.

3. Enterprise presence is real but niche: 250 companies with 10,001+ employees, including Deloitte, Siemens, and JPMorgan Chase, mostly on subdomains and internal tools.

4. Tailwind Labs' January 2026 crisis (75% layoffs, 80% revenue drop) exposed a new risk: AI tools can grow a framework's usage while destroying the business that maintains it.

5. Migration flows favor Tailwind against older frameworks (2.5:1 vs. Materialize, 1.9:1 vs. Semantic UI). The Radix UI "loss" reflects ecosystem pairing (Shadcn/UI), not competitive displacement.

Sales applications

Outreach template: "Hi [Name], I noticed [Company] runs Tailwind CSS on [detected subdomain]. We track 33,668 domains using Tailwind, and 76% of them are small teams building custom UIs. NASA, OpenAI, and Bloomberg all ship with it. Quick question: how's your team handling [relevant pain point]? Worth 15 minutes?"

Targeting strategy: On TechnologyChecker.io, filter for companies using Tailwind CSS with 11-200 employees in IT Services, Software Development, or Advertising Services. These mid-size teams have budget, active codebases, and buying authority for developer tools.

Competitive angle: The 137 companies that switched from Tailwind to Chakra UI wanted more pre-built components. The 189 that added Radix UI wanted headless primitives. Both groups need something Tailwind alone doesn't provide. Position products as the component layer that sits on top of Tailwind's utility classes.

Explore Tailwind CSS's full company list, migration data, and competitive positioning on TechnologyChecker.io, built from 17,569 enriched company profiles across 33,668 detected domains.