Plugins

    Extending Tailwind with reusable third-party plugins.

    Plugins let you register new styles for Tailwind to inject into the user’s stylesheet using JavaScript instead of CSS.

    To get started with your first plugin, import Tailwind’s function from tailwindcss/plugin. Then inside your plugins array, call the imported plugin function with an anonymous function as the first argument.

    tailwind.config.js

    Plugin functions receive a single object argument that can be into several helper functions:

    • addUtilities(), for registering new static utility styles
    • matchUtilities(), for registering new dynamic utility styles
    • addComponents(), for registering new static component styles
    • matchComponents(), for registering new dynamic component styles
    • addBase(), for registering new base styles
    • addVariant(), for registering custom static variants
    • matchVariant(), for registering custom dynamic variants
    • theme(), for looking up values in the user’s theme configuration
    • config(), for looking up values in the user’s Tailwind configuration
    • corePlugins(), for checking if a core plugin is enabled
    • e(), for manually escaping strings meant to be used in class names

    Official plugins

    We’ve developed a handful of official plugins for popular features that for one reason or another don’t belong in core yet.

    Plugins can be added to your project by installing them via npm, then adding them to your tailwind.config.js file:

    tailwind.config.js

    1. module.exports = {
    2.   // ...
    3.   plugins: [
    4.     require('@tailwindcss/typography'),
    5.     require('@tailwindcss/forms'),
    6.     require('@tailwindcss/aspect-ratio'),
    7.     require('@tailwindcss/container-queries'),
    8.   ]
    9. }

    The @tailwindcss/typography plugin adds a set of prose classes that can be used to quickly add sensible typographic styles to content blocks that come from sources like markdown or a CMS database.

    1. <article class="prose lg:prose-xl">
    2.   <h1>Garlic bread with cheese: What the science tells us</h1>
    3.   <p>
    4.     For years parents have espoused the health benefits of eating garlic bread with cheese to their
    5.     children, with the food earning such an iconic status in our culture that kids will often dress
    6.     up as warm, cheesy loaf for Halloween.
    7.   </p>
    8.   <p>
    9.     But a recent study shows that the celebrated appetizer may be linked to a series of rabies cases
    10.     springing up around the country.
    11.   </p>
    12.   <!-- ... -->
    13. </article>

    Learn more about the typography plugin →

    Forms

    The @tailwindcss/forms plugin adds an opinionated form reset layer that makes it easier to style form elements with utility classes.

    1. <!-- You can actually customize padding on a select element: -->
    2. <select class="px-4 py-3 rounded-full">
    3.   <!-- ... -->
    4. </select>
    6. <!-- Or change a checkbox color using text color utilities: -->
    7. <input type="checkbox" class="rounded text-pink-500" />

    Learn more about the forms plugin →

    Aspect ratio

    The @tailwindcss/aspect-ratio plugin is an alternative to native aspect-ratio support that works in older browsers, and adds aspect-w-{n} and aspect-h-{n} classes that can be combined to give an element a fixed aspect ratio.

    1. <div class="aspect-w-16 aspect-h-9">
    2.   <iframe src="https://www.youtube.com/embed/dQw4w9WgXcQ" frameborder="0" allow="accelerometer; autoplay; clipboard-write; encrypted-media; gyroscope; picture-in-picture" allowfullscreen></iframe>
    3. </div>

    Learn more about the aspect ratio plugin →

    Container queries

    The @tailwindcss/container-queries plugin adds new @{size} variants like @sm and @md that let you style an element based on the dimensions of a parent marked with @container instead of the viewport.

    1. <div class="@container">
    2.   <div class="@lg:text-sky-400">
    3.     <!-- ... -->
    4.   </div>
    5. </div>

    Learn more about the container queries plugin →

    Adding utilities

    The addUtilities and matchUtilities functions allow you to register new styles in Tailwind’s utilities layer.

    Like with the utilities Tailwind includes by default, utilities added by a plugin will only be included in the generated CSS if they are actually being used in the project.

    Use the addUtilities function to register simple static utilities that don’t support user-provided values:

    tailwind.config.js

    1. const plugin = require('tailwindcss/plugin')
    3. module.exports = {
    4.   plugins: [
    5.     plugin(function({ addUtilities }) {
    6.       addUtilities({
    7.         '.content-auto': {
    8.           'content-visibility': 'auto',
    9.         },
    10.         '.content-hidden': {
    11.           'content-visibility': 'hidden',
    12.         },
    13.         '.content-visible': {
    14.           'content-visibility': 'visible',
    15.         },
    16.       })
    17.     })
    18.   ]
    19. }

    Learn more about how to represent your styles in JavaScript in the reference.

    Dynamic utilities

    Use the matchUtilities function to register utilities that map to values defined in the user’s theme configuration:

    tailwind.config.js

    1. const plugin = require('tailwindcss/plugin')
    3. module.exports = {
    4.   theme: {
    5.     tabSize: {
    6.       1: '1',
    7.       2: '2',
    8.       4: '4',
    9.       8: '8',
    10.     }
    11.   },
    12.   plugins: [
    13.     plugin(function({ matchUtilities, theme }) {
    14.       matchUtilities(
    15.         {
    16.           tab: (value) => ({
    17.             tabSize: value
    18.           }),
    19.         },
    20.         { values: theme('tabSize') }
    21.       )
    22.     })
    23.   ]
    24. }

    Utilities defined this way also support , which means you can use values not present in the theme using square bracket notation:

    1. <div class="tab-[13]">
    2.   <!-- ... -->
    3. </div>

    Prefix and important

    By default, plugin utilities automatically respect the user’s and important preferences.

    That means that given this Tailwind configuration:

    1. module.exports = {
    2.   prefix: 'tw-',
    3.   important: true,
    4.   // ...
    5. }

    …the example plugin above would generate the following CSS:

    1. .tw-content-auto {
    2.   content-visibility: auto !important;
    3. }
    4. .tw-content-hidden {
    5.   content-visibility: hidden !important;
    6. }
    7. .tw-content-visible {
    8.   content-visibility: visible !important;
    9. }

    Using with modifiers

    Any custom utilities added using addUtilities can automatically be used with modifiers:

    1. <div class="content-auto lg:content-visible">
    2.   <!-- ... -->
    3. </div>

    Learn more in the Hover, Focus, and Other States documentation.

    Utility plugins can provide default values by including a configuration object as the second argument to the plugin function:

    ./plugins/tab-size.js

    These values behave just like the values in the default configuration, and can be overridden or extended by the end user.

    The addComponents function allows you to register new styles in Tailwind’s components layer.

    Use it to add more opinionated, complex classes like buttons, form controls, alerts, etc; the sort of pre-built components you often see in other frameworks that you might need to override with utility classes.

    To add new component styles from a plugin, call addComponents, passing in your styles using :

    tailwind.config.js

    2. module.exports = {
    3.   plugins: [
    4.     plugin(function({ addComponents }) {
    5.       addComponents({
    6.         '.btn': {
    7.           padding: '.5rem 1rem',
    8.           borderRadius: '.25rem',
    9.           fontWeight: '600',
    11.         '.btn-blue': {
    12.           backgroundColor: '#3490dc',
    13.           color: '#fff',
    14.           '&:hover': {
    15.             backgroundColor: '#2779bd'
    16.           },
    17.         },
    18.         '.btn-red': {
    19.           backgroundColor: '#e3342f',
    20.           color: '#fff',
    21.           '&:hover': {
    22.             backgroundColor: '#cc1f1a'
    23.           },
    24.         },
    25.       })
    26.     })
    27.   ]
    28. }

    Like with other component classes in Tailwind, component classes added by a plugin will only be included in the generated CSS if they are actually being used in the project.

    Prefix and important

    By default, component classes automatically respect the user’s prefix preference, but they are not affected by the user’s important preference.

    That means that given this Tailwind configuration:

    tailwind.config.js

    1. module.exports = {
    2.   prefix: 'tw-',
    3.   important: true,
    4.   // ...
    5. }

    …the example plugin above would generate the following CSS:

    1. .tw-btn {
    2.   padding: .5rem 1rem;
    3.   border-radius: .25rem;
    4.   font-weight: 600;
    5. }
    6. .tw-btn-blue {
    7.   background-color: #3490dc;
    8.   color: #fff;
    9. }
    10. .tw-btn-blue:hover {
    11.   background-color: #2779bd;
    12. }
    13. .tw-btn-red {
    14.   background-color: #e3342f;
    15.   color: #fff;
    16. }
    17. .tw-btn-red:hover {
    18.   background-color: #cc1f1a;
    19. }

    Although there’s rarely a good reason to make component declarations important, if you really need to do it you can always add !important manually:

    tailwind.config.js

    1. const plugin = require('tailwindcss/plugin')
    3. module.exports = {
    4.   plugins: [
    5.     plugin(function({ addComponents }) {
    6.       addComponents({
    7.         '.btn': {
    8.           padding: '.5rem 1rem !important',
    9.           borderRadius: '.25rem !important',
    10.           fontWeight: '600 !important',
    11.         },
    12.         // ...
    13.       })
    14.     })
    15.   ]
    16. }

    All classes in a selector will be prefixed by default, so if you add a more complex style like:

    tailwind.config.js

    1. const plugin = require('tailwindcss/plugin')
    3. module.exports = {
    4.   prefix: 'tw-',
    5.   plugins: [
    6.     plugin(function({ addComponents }) {
    7.       const components = {
    8.         // ...
    9.         '.navbar-inverse a.nav-link': {
    10.             color: '#fff',
    11.         }
    12.       }
    14.       addComponents(components)
    15.     })
    16.   ]
    17. }

    …the following CSS would be generated:

    1. .tw-navbar-inverse a.tw-nav-link {
    2.     color: #fff;
    3. }

    Using with modifiers

    Any component classes added using addComponents can automatically be used with modifiers:

    1. <div class="btn md:btn-lg">
    2.   <!-- ... -->
    3. </div>

    Learn more in the Hover, Focus, and Other States documentation.

    Adding base styles

    The addBase function allows you to register new styles in Tailwind’s base layer. Use it to add things like base typography styles, opinionated global resets, or @font-face rules.

    To add new base styles from a plugin, call addBase, passing in your styles using CSS-in-JS syntax:

    tailwind.config.js

    1. const plugin = require('tailwindcss/plugin')
    3. module.exports = {
    4.   plugins: [
    5.     plugin(function({ addBase, theme }) {
    6.       addBase({
    7.         'h1': { fontSize: theme('fontSize.2xl') },
    8.         'h2': { fontSize: theme('fontSize.xl') },
    9.         'h3': { fontSize: theme('fontSize.lg') },
    10.       })
    11.     })
    12.   ]
    13. }

    Since base styles are meant to target bare selectors like div or h1, they do not respect the user’s prefix or important configuration.

    Adding variants

    Static variants

    Use the addVariant function for simple custom variants, passing in the name of your custom variant, and a format string that represents how the selector should be modified.

    tailwind.config.js

    1. const plugin = require('tailwindcss/plugin')
    3. module.exports = {
    4.   // ...
    5.   plugins: [
    6.     plugin(function({ addVariant }) {
    7.       addVariant('optional', '&:optional')
    8.       addVariant('hocus', ['&:hover', '&:focus'])
    9.       addVariant('inverted-colors', '@media (inverted-colors: inverted)')
    10.     })
    11.   ]
    12. }

    The first argument is the modifier name that users will use in their HTML, so the above example would make it possible to write classes like these:

    1. <form class="flex inverted-colors:outline ...">
    2.   <input class="optional:border-gray-300 ..." />
    3.   <button class="bg-blue-500 hocus:bg-blue-600">...</button>
    4. </form>

    Use the matchVariant function to register new parameterized variants like the built-in supports-*, data-*, and aria-* variants:

    tailwind.config.js

    1. const plugin = require('tailwindcss/plugin')
    3. module.exports = {
    4.   plugins: [
    5.     plugin(function({ matchVariant }) {
    6.       matchVariant(
    7.         'nth',
    8.         (value) => {
    9.           return `&:nth-child(${value})`;
    10.         },
    11.         {
    12.           values: {
    13.             1: '1',
    14.             2: '2',
    15.           }
    17.       );
    18.     })
    19.   ]
    20. }

    Variants defined with matchVariant also support arbitrary values using square bracket notation:

    Use the sort option to control the source order of the generated CSS if needed to avoid precedence issues with other values that come from the same variant:

    1. matchVariant("min", (value) => `@media (min-width: ${value})`, {
    2.   sort(a, z) {
    3.     return parseInt(a.value) - parseInt(z.value);
    4.   },
    5. });

    Parent and sibling states

    Your custom modifiers won’t automatically work with Tailwind’s and sibling state modifiers.

    To support the group-* and peer-* versions of your own custom modifiers, register them as separate variants using the special :merge directive to ensure the .group and .peer classes only appear once in the final selector.

    tailwind.config.js

    1. const plugin = require('tailwindcss/plugin')
    3. module.exports = {
    4.   // ...
    5.   plugins: [
    6.     plugin(function({ addVariant }) {
    7.       addVariant('optional', '&:optional')
    8.       addVariant('group-optional', ':merge(.group):optional &')
    9.       addVariant('peer-optional', ':merge(.peer):optional ~ &')
    10.     })
    11.   ]
    12. }

    Plugins can merge their own set of configuration values into the user’s tailwind.config.js configuration by providing an object as the second argument to the plugin function:

    ./plugins/tab-size.js

    1. const plugin = require('tailwindcss/plugin')
    3. module.exports = plugin(function({ matchUtilities, theme }) {
    4.   matchUtilities(
    5.     {
    6.       tab: (value) => ({
    7.         tabSize: value
    8.       }),
    9.     },
    10.     { values: theme('tabSize') }
    11.   )
    12. }, {
    13.   theme: {
    14.     tabSize: {
    15.       1: '1',
    16.       2: '2',
    17.       4: '4',
    18.       8: '8',
    19.     }
    20.   }
    21. })

    This can be useful for things like providing default theme values for the classes your plugin generates.

    Exposing options

    Sometimes it makes sense for a plugin to be configurable in a way that doesn’t really belong under theme, like perhaps you want users to be able to customize the class name your plugin uses.

    For cases like this, you can use plugin.withOptions to define a plugin that can be invoked with a configuration object. This API is similar to the regular plugin API, except each argument should be a function that receives the user’s options and returns the value that you would have normally passed in using the regular API:

    ./plugins/markdown.js

    1. const plugin = require('tailwindcss/plugin')
    3. module.exports = plugin.withOptions(function (options = {}) {
    4.   return function({ addComponents }) {
    5.     const className = options.className ?? 'markdown'
    7.     addComponents({
    8.       [`.${className}`]: {
    9.         // ...
    10.       }
    11.     })
    12.   }
    13. }, function (options) {
    14.   return {
    15.     theme: {
    16.       markdown: {
    17.         // ...
    18.       }
    19.     },
    20.   }
    21. })

    The user would invoke your plugin passing along their options when registering it in their plugins configuration:

    tailwind.config.js

    1. module.exports = {
    2.   theme: {
    3.     // ...
    4.   },
    5.   plugins: [
    6.     require('./plugins/markdown.js')({
    7.       className: 'wysiwyg'
    8.     })
    9.   ],
    10. }

    The user can also register plugins created this way normally without invoking them if they don’t need to pass in any custom options:

    tailwind.config.js

    1. module.exports = {
    2.   theme: {
    3.     // ...
    4.   },
    5.   plugins: [
    6.     require('./plugins/markdown.js')
    7.   ],
    8. }

    CSS-in-JS syntax

    Tailwind’s plugin system expects CSS rules written as JavaScript objects, using the same sort of syntax you might recognize from CSS-in-JS libraries like Emotion, powered by under-the-hood.

    Consider this simple CSS rule:

    1. .card {
    2.   background-color: #fff;
    3.   border-radius: .25rem;
    4.   box-shadow: 0 2px 4px rgba(0,0,0,0.2);
    5. }

    Translating this to a CSS-in-JS object would look like this:

    1. addComponents({
    2.   '.card': {
    3.     'background-color': '#fff',
    4.     'border-radius': '.25rem',
    5.     'box-shadow': '0 2px 4px rgba(0,0,0,0.2)',
    6.   }
    7. })

    For convenience, property names can also be written in camelCase and will be automatically translated to dash-case:

    1. addComponents({
    2.   '.card': {
    3.     backgroundColor: '#fff',
    4.     borderRadius: '.25rem',
    5.     boxShadow: '0 2px 4px rgba(0,0,0,0.2)',
    6.   }
    7. })

    Nesting is also supported (powered by postcss-nested), using the same syntax you might be familiar with from Sass or Less:

    1. addComponents({
    2.   '.card': {
    3.     backgroundColor: '#fff',
    4.     borderRadius: '.25rem',
    5.     boxShadow: '0 2px 4px rgba(0,0,0,0.2)',
    6.     '&:hover': {
    7.       boxShadow: '0 10px 15px rgba(0,0,0,0.2)',
    8.     },
    9.     '@media (min-width: 500px)': {
    10.       borderRadius: '.5rem',
    11.     }
    12.   }
    13. })

    Multiple rules can be defined in the same object:

    1. addComponents({
    2.   '.btn': {
    3.     padding: '.5rem 1rem',
    4.     borderRadius: '.25rem',
    5.     fontWeight: '600',
    6.   },
    7.   '.btn-blue': {
    8.     backgroundColor: '#3490dc',
    9.     color: '#fff',
    10.     '&:hover': {
    11.       backgroundColor: '#2779bd'
    12.     },
    13.   },
    14.   '.btn-red': {
    15.     backgroundColor: '#e3342f',
    16.     color: '#fff',
    17.     '&:hover': {
    18.       backgroundColor: '#cc1f1a'
    19.     },