Breakpoint

The screen width where a layout rearranges itself: columns stack, the nav collapses, the sidebar drops below the content.

where it goes mobilewhen the columns stackbrakepointscreen size cutoffmedia query widththe width where the layout changespoint where it switches to the phone versionresponsive cutoff

See it

Live demo coming soon

What it is

A breakpoint is a viewport width at which your layout rule changes: three columns collapse to one, the nav folds into a hamburger, the sidebar drops below the article. In CSS it's a media query threshold; in a design file it's the second and third artboard you draw. Most teams inherit a set rather than invent one, and Tailwind's 640 / 768 / 1024 / 1280 / 1536 is the current default vocabulary.

Reach for one when the layout genuinely stops working, not on a schedule. Squeeze the browser window until something looks bad, and that width is your breakpoint. Three or four well-chosen ones cover almost every device; a dozen device-named ones ('iPhone 14 Pro') age badly the moment a new phone ships.

Gotcha: breakpoints react to the window, not to the box the component sits in. A card that looks fine in a wide main column breaks when you drop it into a narrow sidebar, because the window never got smaller. That's what container queries are for. Also pick a direction and stick to it: mobile-first uses min-width and layers complexity on, and mixing min-width with max-width in one project produces overlap bugs nobody can trace.

Ask AI for it

Make this section responsive with a mobile-first breakpoint set: single column by default, two columns from 768px, three columns from 1024px, with the sidebar moving below the main content under 1024px. Use min-width media queries (or Tailwind md: and lg: prefixes) only, no max-width overrides, and keep horizontal padding constant across all breakpoints so nothing touches the screen edge.

You might have meant

responsive layoutmobile first layoutgrid systemcontainer max width wrapperreflow