Preflight

    An opinionated set of base styles for Tailwind projects.

    Built on top of , Preflight is a set of base styles for Tailwind projects that are designed to smooth over cross-browser inconsistencies and make it easier for you to work within the constraints of your design system.

    Tailwind automatically injects these styles when you include in your CSS:

    While most of the styles in Preflight are meant to go unnoticed — they simply make things behave more like you’d expect them to — some are more opinionated and can be surprising when you first encounter them.

    For a complete reference of all the styles applied by Preflight, see the stylesheet.


    Default margins are removed

    Preflight removes all of the default margins from elements like headings, blockquotes, paragraphs, etc.

    1. blockquote,
    2. dl,
    3. dd,
    4. h1,
    5. h2,
    6. h3,
    7. h4,
    8. h5,
    9. h6,
    10. hr,
    11. figure,
    12. p,
    13. pre {
    14. margin: 0;

    This makes it harder to accidentally rely on margin values applied by the user-agent stylesheet that are not part of your spacing scale.


    Headings are unstyled

    All heading elements are completely unstyled by default, and have the same font-size and font-weight as normal text.

    1. h1,
    2. h2,
    3. h3,
    4. h4,
    5. h5,
    6. h6 {
    7. font-size: inherit;
    8. font-weight: inherit;
    9. }

    The reason for this is two-fold:

    • It helps you avoid accidentally deviating from your type scale. By default, browsers assign sizes to headings that don’t exist in Tailwind’s default type scale, and aren’t guaranteed to exist in your own type scale.
    • In UI development, headings should often be visually de-emphasized. Making headings unstyled by default means any styling you apply to headings happens consciously and deliberately.

    If you’d like to selectively introduce sensible default heading styles into article-style parts of a page, we recommend the .


    Ordered and unordered lists are unstyled by default, with no bullets/numbers and no margin or padding.

    1. ol,
    2. ul {
    3. margin: 0;
    4. padding: 0;
    5. }

    If you’d like to style a list, you can do so using the and list-style-position utilities:

    You can always add default list styles to your project by .

    If you’d like to selectively introduce default list styles into article-style parts of a page, we recommend the @tailwindcss/typography plugin.

    Unstyled lists are not announced as lists by VoiceOver. If your content is truly a list but you would like to keep it unstyled, to the element:

    1. <ul role="list">
    2. <li>One</li>
    3. <li>Two</li>
    4. <li>Three</li>
    5. </ul>

    Images are block-level

    Images and other replaced elements (like svg, video, canvas, and others) are display: block by default.

    1. img,
    2. svg,
    3. canvas,
    4. audio,
    5. iframe,
    6. embed,
    7. object {
    8. display: block;
    9. vertical-align: middle;
    10. }

    This helps to avoid unexpected alignment issues that you often run into using the browser default of display: inline.

    If you ever need to make one of these elements inline instead of block, simply use the utility:

    1. <img class="inline" src="..." alt="...">

    Images are constrained to the parent width

    This prevents them from overflowing their containers and makes them responsive by default. If you ever need to override this behavior, use the max-w-none utility:

    1. <img class="max-w-none" src="..." alt="...">

    In order to make it easy to add a border by simply adding the border class, Tailwind overrides the default border styles for all elements with the following rules:

    1. *,
    2. ::before,
    3. ::after {
    4. border-width: 0;
    5. border-style: solid;
    6. border-color: theme('borderColor.DEFAULT', currentColor);
    7. }

    Since the border class only sets the border-width property, this reset ensures that adding that class always adds a solid 1px border using your configured default border color.

    This can cause some unexpected results when integrating certain third-party libraries, like for example.

    When you run into situations like this, you can work around them by overriding the Preflight styles with your own custom CSS:

    1. .google-map * {
    2. border-style: none;
    3. }

    Extending Preflight

    If you’d like to add your own base styles on top of Preflight, simply add them to your CSS using the @layer base directive:

    Learn more in the .


    Disabling Preflight

    If you’d like to completely disable Preflight — perhaps because you’re integrating Tailwind into an existing project or because you’d like to provide your own base styles — all you need to do is set preflight to false in the corePlugins section of your tailwind.config.js file:

    tailwind.config.js

    1. module.exports = {
    2. corePlugins: {
    3. preflight: false,
    4. }