Responsive Breakpoint Cheatsheet

Look up common CSS breakpoints and build media queries without second-guessing the syntax. See the breakpoints Tailwind, Bootstrap, Material UI and Foundation use, with your current window width and which one applies right now, and copy a full mobile-first set. The builder writes min-width, max-width or range queries — in px or em, classic or modern range syntax — with orientation, color scheme, reduced motion, hover or container-query options. It's free, runs in your browser, and nothing is sent anywhere.

Framework breakpoints (min-width, px)

FrameworkBreakpoints
Tailwind CSS640, 768, 1024, 1280, 1536
Bootstrap 5576, 768, 992, 1200, 1400
Material UI600, 900, 1200, 1536
Foundation640, 1024, 1200, 1440

When to use it

  1. Look up Tailwind or Bootstrap breakpoints while writing custom CSS.
  2. Write a between-two-widths query without overlapping ranges.
  3. Switch a component to a container query.
  4. Add a dark-mode or reduced-motion variant to a layout.

How to Use

  1. Check your current window width and active breakpoint.
  2. Choose from a width up, below a width, or between two.
  3. Pick syntax, unit and any extra features.
  4. Copy the query, or the full set for your framework.

Features

  1. Tailwind, Bootstrap, Material UI and Foundation sets
  2. Live window width
  3. min-width, max-width and range syntax
  4. px or em
  5. Orientation, color scheme, reduced motion and hover
  6. Container queries
  7. 100% client-side

FAQs

What breakpoints should I use?

Use your framework's if you have one. Otherwise, set breakpoints where your content starts to look wrong, not at specific devices — 640, 768, 1024 and 1280px are common starting points.

Why 767.98px instead of 767px?

Some screens report fractional widths like 767.5px, which fall between 767 and 768. Using .98 below the next breakpoint closes that gap. The range syntax avoids it altogether.

Should breakpoints be in px or em?

em breakpoints scale with the user's browser text size, so layouts adapt when people zoom text. px is simpler and more common.

When should I use a container query?

When a component should adapt to the space it's placed in, not to the whole window — like a card that sits in both a sidebar and a main column.

Is the range syntax safe to use?

Yes, all current browsers support (width >= 768px).

Is anything uploaded?

No. Everything runs in your browser.

Technical Details

Breakpoints are where a layout changes, and the common frameworks disagree on them: Tailwind uses 640, 768, 1024, 1280 and 1536 pixels; Bootstrap 5 uses 576, 768, 992, 1200 and 1400; Material UI 600, 900, 1200 and 1536. The cheatsheet lists each set with its em equivalent and writes a mobile-first set of min-width queries for it. The builder writes a single query from a lower bound, an upper bound or both. A max-width bound is written 0.02px below the breakpoint — 767.98px rather than 767px — which is Bootstrap's convention for avoiding a one-pixel gap or overlap on high-density screens with fractional widths. The newer range syntax, (768px <= width < 1024px), avoids the problem entirely and is supported by all current browsers. Breakpoints can be written in em, which scale with the user's text-size setting. Optional features — orientation, prefers-color-scheme, prefers-reduced-motion and hover/pointer — are joined with and. Container queries use @container and size against a parent element, so media features aren't available there. The page shows your window width live and which breakpoint it falls into.

Web & CSS Tools

Web & CSS Tools

  • Google Fonts Pair Finder
  • CSS Clamp Generator
  • Fluid Type Scale Generator
  • CSS Flexbox Generator
  • CSS Grid Generator
  • CSS Border Radius Generator
  • CSS Box Shadow Generator
  • Cubic Bezier Generator