Maintained by the EverydayTools Design Systems Team · Tailwind v3.4 + v4 reference · Last updated July 2026

Skip to Tailwind reference tool

Tailwind CSS Reference & Class Composer

Search mapped utilities, compose class strings, preview responsive and dark states, and copy HTML, CSS, or Tailwind Play links.

By Muhammad Abdullah Rauf · Founder, EverydayTools.proUpdated 2026-07-05· Reviewed by EverydayTools Design Systems Team

What is the EverydayTools Tailwind reference and class composer?

A searchable Tailwind CSS utility map with CSS property mappings, a live class composer, responsive/dark preview, flex/grid playgrounds, and one-click export to HTML, CSS, or Tailwind Play.

This page combines two workflows developers actually need: a fast utility lookup (class → CSS property → value) and a composition workspace where you stack classes, preview the result, and copy production-ready output.

Unlike static cheat-sheet PDFs, every utility row is filterable, copyable, and linkable. The composer persists favorites and recent picks in localStorage, encodes selections into shareable URLs, and maps composed classes to approximate CSS for handoff.

Coverage spans layout, flex, grid, spacing, typography, color scales, effects, filters, transitions, transforms, accessibility helpers, responsive/dark/state variants, container queries, and Tailwind v4 at-rules. Official Tailwind documentation remains the source of truth for plugin edge cases—this tool optimizes day-to-day lookup and prototyping.

How to use Tailwind CSS reference guide

  1. Search or browse categories

    Type in the search bar (press / to focus) or tap a category pill—Layout, Flexbox, Colors, State Variants, Tailwind v4, and more.

  2. Add utilities to the composer

    Click a class row to toggle it in the composer, or use the Copy button for a single utility. Star rows to save favorites.

  3. Preview and tune output

    Open the Composer tab, toggle dark preview and sm/md/lg viewports, and inspect generated HTML and CSS mapping panels.

  4. Export or share

    Copy the class string, HTML snippet, or CSS block—or open Tailwind Play. Share links encode your selection in the URL query string.

Who uses Tailwind CSS reference guide?

Common real-world scenarios where this tool saves time.

Day-to-day utility lookup

Find the exact class for a CSS property—gap vs space, ring vs shadow, col-span vs grid-cols—without leaving your browser tab.

Prototype layout in meetings

Compose flex/grid stacks live, share a URL with teammates, and paste the class string into your codebase or Tailwind Play.

Design-system handoff

Export CSS mappings alongside class strings when documenting tokens for engineers who do not live in Tailwind docs.

Learn Tailwind v4 syntax

Browse @theme, @source, @utility, and @variant entries alongside v3 utilities to compare migration paths.

Workflow guides

Step-by-step chains that connect related tools for common tasks.

Spacing tokens → Tailwind classes

  1. Pick consistent spacing steps in the Spacing Scale Assistant , then search matching p-*, gap-*, and m-* utilities here.
  2. Load a pattern preset or flex/grid playground output into the composer and copy the class string into your component.

Shadow polish → utility lookup

  1. Generate layered shadows in the Box Shadow Generator , then map arbitrary shadow values to shadow-* or ring-* utilities.
  2. Cross-check border radius tokens with the Border Radius Generator when rounding cards that use composed utilities.

Tailwind CSS reference guide examples

Responsive card layout

Input

grid grid-cols-1 sm:grid-cols-2 lg:grid-cols-3 gap-6

Output

grid-template-columns responsive breakpoints with gap-6 (1.5rem)

Mobile-first grid that grows from one column to three without custom media queries in your CSS file.

Accessible focus button

Input

inline-flex … focus-visible:ring-2 focus-visible:ring-blue-500 focus-visible:ring-offset-2

Output

Visible keyboard focus ring without styling mouse :focus

Pair focus-visible utilities with ring-offset for WCAG-friendly keyboard navigation.

When to use Tailwind CSS reference guide vs related tools

Related toolUse this tool whenUse related tool when
Spacing Scale AssistantYou need Tailwind class names, CSS mappings, and a composer with export.You are choosing which spacing tokens belong in your design system before writing classes.
Typography Scale GeneratorLooking up font-size, leading, and tracking utilities.Building a modular type scale with CSS variables or JSON tokens.
CSS Button GeneratorBrowsing focus-visible and hover utilities for interactive elements.Exporting full button pseudo-class CSS with gradients and shadows.

Best practices

Mobile-first responsive prefixes

Start with base layout classes, then add sm:/md:/lg: overrides sparingly—preview at each viewport in the composer.

Dark mode pairs

When using dark:, mirror light tokens (bg-white dark:bg-slate-900) and test with the dark preview toggle.

Composer before commit

Paste real content into the HTML preview mentally—verify truncation, wrapping, and min-height before shipping.

Common mistakes to avoid

Using margin between siblings instead of gap

Prefer gap-* on flex/grid parents—margin collapses and breaks with wrapping; gap stays predictable.

Removing focus styles without a replacement

Use focus-visible:ring-* utilities rather than outline-none alone; preview keyboard focus in the Composer tab.

Arbitrary values for every spacing decision

Stay on the spacing scale when possible—use the Spacing Scale Assistant to pick consistent tokens first.

Stacking conflicting display utilities

Only one display utility wins—avoid combining hidden and flex without responsive prefixes.

Troubleshooting

A class does not appear to change the live preview

Likely cause: Utilities apply to the preview container, but sample child elements keep their own fixed classes.

Fix: Test layout utilities (flex, grid, gap) first—they affect the container. For text color or font-size, imagine the class on the element that actually needs it in your component.

Share link does not restore my composed classes

Likely cause: The ?c= query parameter was truncated, stripped by a messenger app, or the URL was opened without the full string.

Fix: Copy the class string directly from the Composer tab. Keep share URLs under ~2,000 characters; split very long stacks into multiple copies.

CSS export does not match my production build

Likely cause: This panel maps utilities to approximate declarations. Preflight, CSS variables, minification, and custom @theme tokens change final output.

Fix: Treat the CSS block as documentation. Verify in your app with DevTools computed styles or the Tailwind build output.

Search returns no results for a class I use daily

Likely cause: Custom plugin utilities, @apply component classes, and project-specific theme extensions are not in the default dataset.

Fix: Check tailwindcss.com/docs for plugin classes. Filter by category or version (v3 / v4) in case the utility is listed under a variant row (e.g. md:flex).

Dark mode or responsive classes look wrong in preview

Likely cause: The preview simulates viewport width and a dark background wrapper—it does not run your app's full dark-mode strategy (class vs media).

Fix: Toggle dark preview and sm/md/lg widths to sanity-check tokens, then confirm in your app with the same darkMode setting from tailwind.config or v4 @variant.

CSS → Tailwind matcher suggests the wrong utility

Likely cause: Multiple utilities can map to similar CSS values (e.g. p-4 vs px-4 py-4). Arbitrary values and theme extensions are not always exact matches.

Fix: Pick the utility that matches your design system scale. Prefer gap over margin, theme colors over arbitrary hex, and verify in Tailwind Play before committing.

Favorites or recent history disappeared

Likely cause: localStorage was cleared, private browsing ended, or browser storage quota blocked a save.

Fix: Re-star utilities as needed. Share URLs (?c=) do not depend on localStorage—use them for cross-device handoff.

Clipboard copy fails on mobile or Safari

Likely cause: Clipboard API requires a secure context (HTTPS) and a direct user gesture; some browsers block programmatic copy.

Fix: Tap the copy button again after interacting with the page, or long-press the code block to copy manually.

When this tool isn't the right choice

Configuring Tailwind for production (content paths, safelist, plugins)

Use tailwind.config.js or v4 @theme / @source in your repo. This page is a lookup and composer—not a build pipeline.

Plugin-only utilities (@tailwindcss/forms, typography, aspect-ratio plugins, etc.)

Official Tailwind docs and plugin READMEs list form resets, prose classes, and third-party utilities not generated in this dataset.

Learning Tailwind from scratch with tutorials and examples

Start with tailwindcss.com/docs or the Tailwind Play tutorial. This tool assumes you know what a utility class is and need speed or export.

Generating complete UI components (modals, datatables, nav menus)

Use component libraries (Headless UI, shadcn/ui, Flowbite) or your design system. The pattern presets here are starting points, not accessible production components.

Pixel-perfect conversion from Figma or Sketch specs

Design handoffs often use one-off values. Use arbitrary syntax sparingly; map tokens with Spacing Scale Assistant and Typography Scale Generator first.

Replacing your IDE Tailwind IntelliSense extension

Editor extensions autocomplete inside your project with your exact config. This reference uses default theme scales and cannot see your custom theme.

Auditing accessibility or WCAG compliance of a full page

Individual sr-only and focus-visible utilities are listed, but page-level audits need axe, Lighthouse, or manual keyboard testing—not a class picker.

Offline documentation when you have no network at all

The page requires an initial load. For fully offline use, download official Tailwind docs or use IDE snippets; composer state in localStorage still needs the app cached.

What to do next

Continue the workflow with the right follow-up tool.

  • After composing layout utilities, tune spacing tokens in theSpacing Scale Assistant before locking p-* and gap-* classes.
  • Export typography tokens from theTypography Scale Generator and map them to text-* and leading-* utilities here.
  • Upgrading to v4? Filter the reference table by Tailwind v4 and review @theme, @utility, and @variant rows in the v4 category.

Frequently Asked Questions

Is this a complete replacement for Tailwind documentation?

No—it is an interactive reference and composer optimized for lookup speed and copy/export. Use tailwindcss.com/docs for plugins, configuration, and edge cases.

Which Tailwind versions are supported?

Utility mappings follow Tailwind v3.4 defaults plus v4 at-rule reference entries. Filter by version in the reference table. Verify against your project's config when upgrading.

How do I copy a single utility class?

Click Copy on any reference row, or click the class badge to add it to the composer and copy the combined string from the Composer tab.

How does the live preview work?

Selected classes apply to a preview container. Toggle dark mode and sm/md/lg widths to stress-test responsive and dark: utilities. Child markup is fixed sample content.

Can I share my composed class selection?

Yes—Share URL copies a link with ?c= encoded classes. Favorites and recent picks persist in localStorage on this device.

Does the CSS export match Tailwind's compiled output exactly?

The CSS panel shows property mappings for documentation and handoff. Production builds may differ slightly due to preflight, variables, and minification—always verify in your app build.

How do I open my composition in Tailwind Play?

Use Open in Tailwind Play from the Composer tab—it pre-fills a minimal HTML snippet with your class string.

Is my search or selection uploaded to a server?

No—search, favorites, and composer state run locally in your browser. Share links encode data in the URL only.

What is a Tailwind utility-first workflow?

Utility-first means composing small single-purpose classes in markup (flex, gap-4, text-sm) instead of writing bespoke component CSS—see the glossary-level overview in our methodology section.

What does the dark: variant do?

The dark: prefix applies utilities when dark mode is active—pair light and dark tokens (bg-white dark:bg-slate-900) and test with the composer dark preview.

What is @theme in Tailwind v4?

@theme is a CSS-first directive to define design tokens in v4. Browse v4 category rows for @theme, @utility, and @variant examples.

What are arbitrary values in Tailwind?

Square-bracket classes like w-[347px] escape the default scale for one-off values—use sparingly; prefer theme tokens from the spacing and typography tools linked on this page.

Privacy, accuracy, and trust

Privacy

Utility search, favorites, and composer state are processed locally. Share URLs encode selections in query parameters only—nothing is stored on EverydayTools servers.

Accuracy

Mappings are validated against Tailwind v3.4 default theme and v4 documentation. Re-verify when using custom themes or plugins.

Reference and prototyping tool—not a substitute for your production Tailwind build pipeline.

Advertisement

Reviewed by EverydayTools Design Systems Team on 2026-07-05.

Same workflow or intent — pick the next step without leaving the site.

Frequently opened tools from the same category.

People also use

Cross-category tools others open in the same session.

Explore categories

Browse full tool collections by topic.