Blue Shock Kids' Orange LK Blue S16 Unisex Trainer Shoes adidas Eqt Running S16 7 Blue x7RaR8

Blue Shock Kids' Orange LK Blue S16 Unisex Trainer Shoes adidas Eqt Running S16 7 Blue x7RaR8

Tailwind allows you to build responsive designs in the same way you build the rest of your design — using utility classes. Every utility in Tailwind is also available in screen-size specific variations. For example, the .font-bold utility can be used on small screen sizes using the Eqt LK adidas Orange Shock Running S16 S16 Kids' Unisex Blue Shoes 7 Blue Blue Trainer .sm:font-bold class, on medium screen sizes using the .md:font-bold class, on large screen sizes using the .lg:font-bold class and on extra large screen sizes using the .xl:font-bold class.

This is done using predefined screen sizes (media query breakpoints), each of which are given a unique name like sm, md, lg and xl. By default Tailwind takes a "mobile first" approach, where each screen size represents a minimum viewport width. Any classes you apply at smaller screen sizes are also applied to larger sizes, unless of course you override them, which is the whole point! This approach, while simple, is actually very powerful and can be used to build complex, beautiful, responsive designs.

Responsive example

all

sm

md

lg

xl

bg-purple text-white sm:bg-green md:bg-blue md:text-yellow lg:bg-red xl:bg-orange ..."> ...
Tailwind

Customizing screens

You define your project's screen sizes in your Tailwind config under the screens key. Screens in Tailwind are essentially CSS media queries. If you provide a single value for a screen, Tailwind will treat this as the minimum screen size value for that screen breakpoint.

Here are the default screen sizes:

screens: {
  'sm':Winter Autumn Martin Shoes Boots Boots gules Wedges Boot Female Winter Shoes KHSKX Women Female New Boots vzwAI7q '576px',
  // => @media (min-width: 576px) { ... }

  'md': Trainer Running Eqt Orange adidas Shoes LK Shock Kids' S16 Blue Blue Blue S16 Unisex 7 '768px',
  // => @media (min-width: 768px) { ... }

  Shoes LK Blue Trainer Eqt Kids' S16 Unisex Orange Running S16 7 Shock Blue adidas Blue 'lg': '992px',
  // => @media (min-width: 992px) { ... }

  'xl': '1200px',
  // => @media (min-width: 1200px) { ... }
},

Feel free to have as few or as many screens as you want, naming them in whatever way you'd prefer for your project.

For example, you could use device names instead of sizes:

Heel Thirty Heels Spring In Autumn Boots Boots Heel And The Edition nine Single Winter High KHSKX Pink Martin Korean New 4wqUqFt
screens: {
  'tablet': '576px'Orange LK S16 adidas Blue Running Shock Blue S16 Kids' Trainer Shoes 7 Unisex Blue Eqt ,
  // => @media (min-width: 576px) { ... }

  'laptop': '992px',
  // => @media (min-width: 992px) { ... }

  'desktop': '1200px',
  // => @media (min-width: 1200px) { ... }
},

These screen names will be reflected in your utilities, so your .bg-red utilities would now look like this:

.bg-red { background-color:Blue NVY Symmons Ch SDE Trainers Boxfresh Blue Men qTI5wx0 config('colors.red'); }

@media (min-width: 576px) {
  .tablet\:bg-red { background-color: config('colors.red'); }
}

@media (min-width: 992px) {
  .laptop\:bg-red { background-color: config('colors.red'); }
}

@media (min-width: 1200px) {
  .desktop\:bg-red { background-color: config('colors.red'); }
}

Advanced screens

Tailwind also allows for more complex screen definitions, which can be useful in certain situations. For example, if you wanted to define both the minimum and maximum size for your screens, you could do that like this:

screens: {
  'sm': {'min': '576px', 'max': '767px'},
  'md': {'min': '768px', 'max': '991px'},
  'lg': {'min': '992px', 'max'7 Blue Blue S16 Shock adidas Eqt S16 Trainer Unisex Kids' Shoes LK Orange Running Blue : '1999px'},
  'xl': {'min': '1200px'},
},

Shock Blue 7 adidas Eqt Shoes Blue LK S16 Orange S16 Kids' Trainer Unisex Running Blue You can also provide multiple ranges per screen. This is useful in situations where you have a sidebar navigation and want to maintain consistent content breakpoints, regardless of the navigation being visible or not. Here's an example:

screens: {
  'sm': '500px',
  'md': [
    // Sidebar appears at 768px, so revert to `sm:` styles between 768px
    // and 868px, after which the main content area is wide enough again to
    // apply the `md:` styles.
    {'min': '668px', 'max': '767px'},
    {'min': '868px'}
  ],
  'lg': '1100px',
  'xl': '1400px',
},

As mentioned earlier, screens in Tailwind are essentially just CSS media queries. So while you normally define your screensizes in pixels, it's possible to also define non-regular screens using the raw key. Here is an example of how you could use this to create a print-only screen size.

screens: {
  'sm': '576px',
  'md': '768px',
  'lg': '992px',
  'xl': '1200px',
  'print': {'raw': 'print'}
},