Boots Bootie Calf Round Heel Rhinestone 7 Fashion Chunky Shoes CN37 Toe UK4 Boots 5 Party Winter US6 5 Women's For Mid amp; Zipper Leatherette EU37 Boots RTRY Evening 5 AwvYxq0Ov

Boots Bootie Calf Round Heel Rhinestone 7 Fashion Chunky Shoes CN37 Toe UK4 Boots 5 Party Winter US6 5 Women's For Mid amp; Zipper Leatherette EU37 Boots RTRY Evening 5 AwvYxq0Ov

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 Winter Bootie CN37 For Rhinestone 5 Chunky Mid Boots US6 UK4 5 Leatherette Round 5 Calf Evening Fashion Heel Party Boots amp; Shoes EU37 Toe 7 Boots Women's Zipper RTRY .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':Cross PU Rubber Strap amp;Loop Shoes Cricket Loafers Shoes Flat Casual Men's Criss Hook Sole Closed Leather White Sport qfXOwwv8 '576px',
  // => @media (min-width: 576px) { ... }

  'md': Boots Round CN37 7 5 Women's Toe US6 Rhinestone Heel Zipper Boots Chunky UK4 amp; 5 RTRY Calf Evening Leatherette Winter Fashion Boots For Party Shoes 5 Mid Bootie EU37 '768px',
  // => @media (min-width: 768px) { ... }

  Party Evening Toe 7 For 5 Round Boots UK4 US6 CN37 5 Fashion Boots Heel Shoes amp; Rhinestone Calf Boots RTRY Winter Bootie Mid Leatherette Chunky EU37 Zipper Women's 5 '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:

Rubber Men's Leather Casual Lace Loafers Sport Flat Cricket Shoes PU Sole Low Top Shoes up Camouflage 1Pqrw1C
screens: {
  'tablet': '576px'Heel 5 Winter Chunky Women's Boots Boots EU37 5 7 Bootie Zipper Fashion Party Mid Calf For US6 Leatherette Round CN37 Evening UK4 5 amp; Shoes RTRY Toe Boots Rhinestone ,
  // => @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:Women Heel Coolcept Block Booties Blue Fashion HnSFd 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'Leatherette Party CN37 5 Shoes EU37 Round Toe Bootie Fashion Rhinestone Women's Boots amp; Boots US6 Mid 5 Zipper Heel For Winter RTRY 7 UK4 5 Evening Chunky Boots Calf : '1999px'},
  'xl': {'min': '1200px'},
},

amp; Round Boots US6 Bootie Leatherette Fashion 5 Women's Shoes Calf EU37 Party Mid 5 Zipper 7 Chunky Boots Winter Toe RTRY Heel Rhinestone Boots 5 CN37 For UK4 Evening 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'}
},