Is Tailwind CSS down? User reports show no current problems with Tailwind CSS

Is Tailwind CSS Down Right Now?

No, Tailwind CSS is not down in the hosted sense. It is a CSS framework that builds inside your own project. The reports above show the current Tailwind CSS status from developers whose styles stopped working.

When many developers report broken styling at once, a major version change is often the cause. A Tailwind CSS outage on your site usually means classes are not generated or a build step fails. This page tracks Tailwind CSS down reports and fixes.

Is Tailwind CSS Down for Me or Everyone?

Check the built CSS file for one class you just used. If the class is missing there, the build never saw your content files. If it exists, the problem is caching or a load order issue on the page.

Run the build again and read the first warning. Tailwind quietly skips files it cannot scan. One wrong path in the config can empty the whole output while the build still passes.

Why Are My Tailwind Classes Not Working?

Tailwind only generates classes it finds in your content files. If a template folder is missing from the content paths, its classes never enter the CSS. The page then renders plain and unstyled.

Dynamic class names built in code also get skipped. The scanner reads plain text, not computed strings. Use full class names in your files, or list special cases in the safelist.

Why Did the Version 4 Upgrade Break My Styles?

Version 4 replaced the old directive lines with a single import in CSS. It also moved configuration into CSS first setup. Projects that keep the version 3 setup see unknown rule errors at build time.

The upgrade tool converts most projects automatically. Run it, then check your custom theme values in the new CSS format. The old JavaScript config still loads in compatibility mode for many setups.

Why Do Styles Vanish in the Production Build?

Production builds scan the same content paths, but deploy pipelines sometimes miss files. A template stored outside the scanned folders loses its classes only in production. Dev mode masks this with its wider watch.

Compare the production CSS size with your local build. A much smaller file confirms the scan missed content. Fix the paths for the build environment and rebuild from a clean output folder.

Common Tailwind CSS Problems and Fixes

Classes are not generated at all

Classes are not generated at all: Check every content path in the config against your real folders. Include the file types you actually use. Restart the build watcher after config edits so it rescans all files from zero.

Unknown at rule error for tailwind directives

Unknown at rule error for tailwind directives: Version 4 uses a CSS import instead of the three directives. Update the entry CSS file to the new syntax. Add the PostCSS plugin or the Vite plugin that version 4 expects.

Styles missing only in production

Styles missing only in production: The build scanned fewer files than your dev run. Align the content paths for both environments. Avoid class names built from string pieces. Add needed dynamic classes to the safelist.

Config file seems ignored

Config file seems ignored: Confirm the config sits where the build looks for it. In version 4, most settings live in CSS with the theme directive. Point the old config in through the compatibility directive if you keep it.

Editor hints and autocomplete stopped

Editor hints and autocomplete stopped: The editor extension reads your setup to learn the classes. Restart the editor after big upgrades. Check that the extension matches your major version and the CSS entry file is valid.