Tailwind CSS License, Explained: One Free Framework, Two Paid Products

Tailwind CSS itself is MIT-licensed: free for commercial use, with no purchase and no attribution page required beyond keeping copyright notices in code you redistribute. The confusion "Tailwind license" searches for usually isn't about the framework — it's about telling apart three separate things sharing the name: the free open-source engine, Tailwind Labs' own paid component marketplace, and a third party's commercial template license for code built with the free framework.

Three products, one name

"Tailwind" resolves to three different licenses depending on which product a search actually lands on — and the top organic result for this exact query is Tailwind Labs' own commercial pricing page, not the framework's license file, which is the collision this post exists to untangle.

Only the first row is what "Tailwind CSS license" is technically asking about. Tailwind Labs' GitHub repository states it plainly: the framework is MIT, full stop. The permission is unconditional — no revenue threshold, no field-of-use limit, no requirement to credit Tailwind Labs anywhere a visitor can see. The obligation, as with any MIT dependency, is to keep the copyright notice in copies of the software itself (the compiled CSS engine's own source), not in every website that uses it.

What this codebase actually ships

This storefront is a real test case, not a hypothetical one. package.json pins the dependency directly:

"tailwindcss": "^4"

and the committed lockfile resolves that to an exact, auditable version:

"node_modules/tailwindcss": {
  "version": "4.3.1",
  "resolved": "https://registry.npmjs.org/tailwindcss/-/tailwindcss-4.3.1.tgz"
}

Tailwind v4 moved configuration out of a tailwind.config.js file and into CSS itself, via an @theme block. This site's actual token definitions, unedited, from src/app/globals.css:

@import "tailwindcss";

@theme {
  --font-sans: var(--font-outfit), ui-sans-serif, system-ui, sans-serif;

  /* Brand / primary scale */
  --color-primary: #465fff;
  --color-primary-25: #f2f7ff;
  --color-primary-50: #ecf3ff;
  /* … full primary-25…950 scale, then the TailAdmin gray-25…950 scale … */
}

That whole block — the entire visual identity of a commercial product sold under a paid tiered license (below) — is Tailwind CSS doing exactly what its MIT grant permits: being used, modified and shipped inside software the modifier charges money for.

The second row of the table above is the one this codebase does not touch. None of ASoc's 111 catalog products import a Tailwind UI or Tailwind Plus component — every component here is hand-built against the @theme tokens, which is why the "pixel-faithful port" convention this repo runs on (preserving exact utility classes from a source design) is possible at all: there's no Plus license boundary to stay inside, because there's no Plus code in the tree to begin with.

There is exactly one file in this repository that imports the framework — src/app/globals.css, all 133 lines of it — and every one of the 97 component files under src/components and src/app that use a className prop draws from the tokens that single file defines. One import point, one license (MIT), no per-component licensing question to ask.

That single-file design has a real cost the license question doesn't cover but is worth flagging alongside it: Tailwind v4's CSS-first @theme config does not hot-reload under this project's Turbopack dev server. Every edit to a color or token variable in globals.css needs a manual npm run dev restart, or new utility classes like bg-primary silently fail to generate — a defect real enough that it's called out as a standing warning in this repo's own CLAUDE.md. It has nothing to do with what the license permits; it's the operational tax of the same CSS-first architecture that makes the license question this simple in the first place.

Why the ASoc EULA fee has nothing to do with Tailwind

The third row is where buyer confusion actually lands, and it's worth stating precisely because it resolves a real refund-request pattern: paying for a template is not paying for Tailwind CSS. ASoc's own tiered license — Single ($39), All-Access ($129), Full Stack ($249), read in full in Template Licenses Explained — governs the original design and code a buyer downloads: the components, the layout decisions, the copy, the assembled product. Tailwind CSS underneath that code stays exactly as free and exactly as MIT as it was before the purchase. A buyer could, with zero payment to anyone, write the identical @theme block above and start from a blank Next.js project. What the EULA fee buys is the hundreds of hours of markup, states and content someone already built on top of that free foundation — the same "sublicensing is explicitly permitted" logic covered for the full 111-product catalog's entire dependency tree in MIT License, Audited.

Mistakes and how they show up

Frequently asked questions

Is Tailwind CSS free to use in a commercial project? Yes, unconditionally. MIT grants the right to use, modify, merge, publish, distribute, sublicense and sell software built with it, with no royalty and no revenue threshold.

Do I need to buy Tailwind UI or Tailwind Plus to use Tailwind CSS? No. They're separate, optional products — a paid library of prebuilt components and page templates sold by Tailwind Labs. The framework itself works, and is fully licensed for commercial use, with zero Plus components installed.

If I buy a template built with Tailwind CSS, does that also license Tailwind CSS to me? Tailwind CSS was already licensed to everyone, for free, before the purchase. Buying a template licenses the seller's original code under the seller's own terms; it doesn't change anything about Tailwind's MIT grant one way or the other.

What do I actually owe if I redistribute a Tailwind CSS-based build? The same thing every MIT dependency asks for: keep the copyright notice and license text with copies of the software. In practice, that's a third-party-licenses page or attribution file generated from your installed dependency tree — the mechanics are covered in full in MIT License, Audited.

Does upgrading Tailwind CSS versions change what I'm licensed to do? No — every published version of the open-source framework ships under the same MIT terms; a major-version bump (like v3's config-file model to v4's CSS-first @theme) changes the API surface, never the license. This codebase pins "tailwindcss": "^4" in package.json, currently resolving to 4.3.1 in the committed lockfile, and none of that version range changes what's permitted.

Templates in this post

Every one of ASoc's landing-page templates — including ASoc Surge, ASoc Synth and ASoc Tempo — is built on the same MIT-licensed Tailwind CSS v4 stack measured above, sold under the tiered commercial EULA rather than Tailwind's own license. Browse the full sets: Next.js landing page templates and Tailwind landing page templates.