Latest in branch 1.0
1.0.6
Released 31 Jul 2019
(6 years ago)
SoftwareTailwind CSS
Branch1.0
Initial release1.0.0
13 May 2019
(7 years ago)
Latest release1.0.6
31 Jul 2019
(6 years ago)
Support status06 Aug 2019
(Ended 6 years, 9 months ago)
Release noteshttps://github.com/tailwindlabs/tailwindcss/releases/tag/v1.0.6
Source codehttps://github.com/tailwindlabs/tailwindcss/tree/v1.0.6
Downloadhttps://github.com/tailwindlabs/tailwindcss/releases/tag/v1.0.6
Tailwind CSS 1.0 ReleasesView full list

What Is New in Tailwind CSS 1.0

CategoryHighlights
New FeaturesFirst production-ready version of the utility-first CSS framework (v1.0.0)

Is Tailwind CSS 1.0 the first stable release?

Yes, v1.0.0 marks the inaugural production-ready release of Tailwind CSS.

In practice this means you can now rely on a stable API, official documentation, and long-term support without worrying about experimental flags. The release consolidates the utilities that were previously available only in beta builds, giving teams a solid foundation for rapid UI development.

What programming language powers Tailwind CSS 1.0?

Tailwind CSS 1.0 is written in TypeScript.

This matters if your build pipeline already uses TypeScript because the source maps and type definitions integrate seamlessly, reducing friction when extending the framework or writing custom plugins.

// tailwind.config.ts
export default {
  theme: {
    extend: {},
  },
  plugins: [],
}

Who created Tailwind CSS 1.0 and what is its core philosophy?

Adam Wathan authored Tailwind CSS 1.0, championing a utility-first approach for rapid UI development.

Watch out for the shift from component-centric CSS to composable utility classes; this reduces stylesheet bloat and encourages design consistency across large codebases.

How does Tailwind CSS 1.0 affect existing projects that were using pre-release builds?

There are no breaking changes because v1.0 is the first official stable version.

Most teams can upgrade by replacing the pre-release package with the v1.0 package and keeping the same configuration file, which simplifies migration and eliminates the need for extensive refactoring.

Frequently Asked Questions

Does Tailwind CSS 1.0 require a build step?
Yes, you need to run a PostCSS build to generate the final CSS file.

Can I use Tailwind CSS 1.0 with PostCSS?
Yes, Tailwind CSS 1.0 is distributed as a PostCSS plugin and works with any PostCSS setup.

Is the JIT mode available in Tailwind CSS 1.0?
No, the Just-In-Time compiler was introduced in later major versions.

How do I install Tailwind CSS 1.0 via npm?
Run npm install [email protected] to add the stable release to your project.

What is the default color palette in Tailwind CSS 1.0?
The default palette includes shades like gray-100, gray-200, blue-500, and red-600.

Are there any breaking changes from pre-release to 1.0?
No, because 1.0 is the first stable release, existing pre-release configurations continue to work unchanged.

Releases In Branch 1.0

VersionRelease date
1.0.631 Jul 2019
(6 years ago)
1.0.511 Jul 2019
(6 years ago)
1.0.411 Jun 2019
(6 years ago)
1.0.301 Jun 2019
(6 years ago)
1.0.227 May 2019
(6 years ago)
1.0.113 May 2019
(7 years ago)
1.0.013 May 2019
(7 years ago)
1.0.0-beta.1012 May 2019
(7 years ago)
1.0.0-beta.912 May 2019
(7 years ago)
1.0.0-beta.828 Apr 2019
(7 years ago)
1.0.0-beta.727 Apr 2019
(7 years ago)
1.0.0-beta.627 Apr 2019
(7 years ago)
1.0.0-beta.518 Apr 2019
(7 years ago)
1.0.0-beta.429 Mar 2019
(7 years ago)
1.0.0-beta.318 Mar 2019
(7 years ago)
1.0.0-beta.216 Mar 2019
(7 years ago)
1.0.0-beta.115 Mar 2019
(7 years ago)