Bird
Raised Fist0
Tailwindmarkup~5 mins

Custom breakpoints in Tailwind

Choose your learning style10 modes available
Introduction

Custom breakpoints let you control when your website changes layout on different screen sizes. This helps your site look good on phones, tablets, and desktops.

You want your site to look different on a tablet than on a phone or desktop.
You have a special device size that needs a unique layout.
You want to improve readability by changing font sizes at certain widths.
You want to show or hide parts of your page depending on screen size.
You want to create a design that fits your brand's style on all devices.
Syntax
Tailwind
module.exports = {
  theme: {
    extend: {},
    screens: {
      'sm': '480px',
      'md': '768px',
      'lg': '1024px',
      'xl': '1280px',
      '2xl': '1536px',
      'tablet': '640px',
      'laptop': '1024px',
      'desktop': '1280px'
    }
  }
}

Define custom breakpoints inside the screens object in your tailwind.config.js file.

Use the breakpoint names as prefixes in your CSS classes, like tablet:bg-blue-500.

Examples
This example creates three custom breakpoints named phone, tablet, and desktop.
Tailwind
screens: {
  'phone': '375px',
  'tablet': '640px',
  'desktop': '1024px'
}
This box changes background color depending on the screen size using the custom breakpoints.
Tailwind
<div class="phone:bg-red-500 tablet:bg-green-500 desktop:bg-blue-500">
  Responsive box
</div>
Sample Program

This page uses custom breakpoints named phone, tablet, and desktop. The box changes its background color as you resize the browser window.

Tailwind
<!DOCTYPE html>
<html lang="en">
<head>
  <meta charset="UTF-8" />
  <meta name="viewport" content="width=device-width, initial-scale=1" />
  <title>Custom Breakpoints Example</title>
  <script src="https://cdn.tailwindcss.com"></script>
  <script>
    tailwind.config = {
      theme: {
        extend: {},
        screens: {
          'phone': '375px',
          'tablet': '640px',
          'desktop': '1024px'
        }
      }
    }
  </script>
</head>
<body class="p-6">
  <div class="phone:bg-red-300 tablet:bg-green-300 desktop:bg-blue-300 p-6 rounded">
    Resize the browser to see background color change.
  </div>
</body>
</html>
OutputSuccess
Important Notes

After changing tailwind.config.js, restart your build process if you use one.

Use meaningful names for breakpoints that match your design needs.

Test your site on different devices or use browser DevTools to resize and check responsiveness.

Summary

Custom breakpoints let you control layout changes at screen widths you choose.

Define them in the screens section of tailwind.config.js.

Use breakpoint names as prefixes in your Tailwind CSS classes to apply styles conditionally.

Practice

(1/5)
1. What is the main purpose of defining custom breakpoints in Tailwind CSS?
easy
A. To add new colors to the palette
B. To change font sizes globally
C. To create custom animations
D. To control when styles change based on screen width

Solution

  1. Step 1: Understand what breakpoints do

    Breakpoints let you apply different styles depending on screen size.
  2. Step 2: Identify the role of custom breakpoints

    Custom breakpoints let you choose specific screen widths for style changes.
  3. Final Answer:

    To control when styles change based on screen width -> Option D
  4. Quick Check:

    Breakpoints = screen width control [OK]
Hint: Breakpoints control style changes by screen size [OK]
Common Mistakes:
  • Confusing breakpoints with colors or fonts
  • Thinking breakpoints create animations
  • Assuming breakpoints change global styles
2. Which is the correct way to define a custom breakpoint named tablet at 768px in tailwind.config.js?
easy
A. "screens": { "tablet": "768px" }
B. "screens": { "tablet": 768 }
C. "breakpoints": { "tablet": "768px" }
D. "screens": { "tablet": "768" }

Solution

  1. Step 1: Identify the correct config key

    Custom breakpoints go under the "screens" key in tailwind.config.js.
  2. Step 2: Use correct value format

    Breakpoint values must be strings with units, e.g., "768px".
  3. Final Answer:

    "screens": { "tablet": "768px" } -> Option A
  4. Quick Check:

    screens + "768px" string = correct syntax [OK]
Hint: Use "screens" key with pixel string values [OK]
Common Mistakes:
  • Using number without units
  • Using wrong key like "breakpoints"
  • Omitting "px" unit in value
3. Given this config snippet:
module.exports = { theme: { screens: { 'md': '640px', 'lg': '1024px', 'xl': '1280px' } } }

Which class applies padding only on screens 1024px wide or larger?
medium
A. lg:p-4
B. p-lg-4
C. md:p-4
D. xl:p-4

Solution

  1. Step 1: Understand breakpoint prefixes

    Tailwind uses breakpoint names as prefixes followed by a colon, e.g., "lg:".
  2. Step 2: Match breakpoint to screen size

    "lg" is 1024px, so "lg:p-4" applies padding at 1024px and above.
  3. Final Answer:

    lg:p-4 -> Option A
  4. Quick Check:

    Prefix "lg:" = 1024px+ padding [OK]
Hint: Use breakpoint name + colon before class [OK]
Common Mistakes:
  • Using breakpoint name after class (wrong order)
  • Missing colon after breakpoint
  • Confusing md and lg breakpoints
4. You added a custom breakpoint tablet at 768px but your styles using tablet:bg-red-500 don't apply. What is the likely error?
medium
A. You defined tablet under colors instead of screens
B. You used tablet: prefix instead of tablet-
C. You forgot to restart the Tailwind build process after config change
D. You wrote tablet: bg-red-500 with a space

Solution

  1. Step 1: Check config changes effect

    Tailwind requires restarting the build to load new config values.
  2. Step 2: Verify syntax and placement

    Using "tablet:bg-red-500" is correct syntax; spacing or wrong keys cause errors but less likely here.
  3. Final Answer:

    You forgot to restart the Tailwind build process after config change -> Option C
  4. Quick Check:

    Restart build after config edits [OK]
Hint: Restart Tailwind build after config edits [OK]
Common Mistakes:
  • Using dash (-) instead of colon (:) in class prefix
  • Defining breakpoint in wrong config section
  • Adding spaces inside class names
5. You want a layout that shows a sidebar only on screens wider than 900px. You defined a custom breakpoint desktop at 900px. Which Tailwind class setup correctly hides the sidebar on smaller screens and shows it on desktop and larger?
hard
A. block hidden:desktop
B. hidden desktop:block
C. block desktop:hidden
D. desktop:hidden block

Solution

  1. Step 1: Understand default and breakpoint styles

    "hidden" hides element by default (all screens). "desktop:block" shows it at 900px+.
  2. Step 2: Match classes to desired behavior

    Using "hidden desktop:block" hides sidebar on small screens and shows on desktop and larger.
  3. Final Answer:

    hidden desktop:block -> Option B
  4. Quick Check:

    hidden + breakpoint:block = show on breakpoint [OK]
Hint: Use hidden by default, breakpoint:block to show [OK]
Common Mistakes:
  • Reversing hidden and block classes
  • Using breakpoint:hidden instead of breakpoint:block
  • Incorrect class order or syntax
Recommended

Ready to prove it?

Pass the test and this pattern moves unknown strong while earning +1 Grip toward your certificate.

10 questions~5 mineasy hard