{"course":{"slug":"design-foundations","title":"Design, before Any Software","url":"https://addaly.com/learn/design-foundations","level":"beginner","track":"create"},"lesson":{"slug":"breakpoints-from-content","title":"Breakpoints come from the content, not from devices","url":"https://addaly.com/learn/design-foundations/breakpoints-from-content","position":58,"of":74,"minutes":8,"answer":"Put breakpoints where your content measurably breaks rather than where devices sit, prefer intrinsic rules and container queries over enumerated cases.","keyIdea":"Put breakpoints where your content measurably breaks rather than where devices sit, prefer intrinsic rules and container queries over enumerated cases, and design the small screen first because a narrow column forces the hierarchy decisions a wide one lets you avoid."},"body":{"format":"markdown","text":"## Naming breakpoints after phones ages badly\n\nA stylesheet with `$tablet: 768px` was written when there was a tablet at 768 pixels. There are now devices at every width from 320 to 3840, foldables that change width mid-session, split-screen multitasking, and browser windows people resize for no reason.\n\nThe method that does not age: **widen and narrow the browser slowly, and put a breakpoint wherever the layout stops working.** Not where a device sits. Where your content breaks.\n\nThis produces breakpoints at odd numbers (540, 720, 960, 1180) and that is the sign you did it right. Round numbers usually mean somebody copied them.\n\n## What breaking looks like\n\nThe specific failures to watch for as you resize:\n\n- **The measure exceeds 75 characters.** Time to cap the column or add a second one.\n- **The measure drops below about 35 characters.** Time to drop a column.\n- **A heading breaks into a bad shape**: one word on the second line, or a wrap mid-phrase.\n- **A horizontal layout has less than about 200 pixels per item.** Cards stop working somewhere around there.\n- **Navigation runs out of room.** Usually the first thing to break on the way down.\n- **A table starts scrolling horizontally.** Which means it needs a different presentation, not a smaller font.\n\nEach of these is a measurement you can take, which is what makes this a technique rather than an aesthetic judgement.\n\n## Container queries change the unit of the question\n\nA media query asks how wide is the window. That is the wrong question for a component, because the same card might appear in a wide main column, a narrow sidebar and a three-across grid, all on the same page at the same viewport width.\n\nContainer queries ask how wide is the space this component has been given:\n\n```css\n.card-wrap { container-type: inline-size; }\n\n@container (min-width: 28rem) {\n  .card { display: grid; grid-template-columns: 8rem 1fr; }\n}\n```\n\nThe card becomes horizontal when its own container is wide enough, wherever that container happens to be. This has been available across the major browsers since 2023, and it is the most significant change to responsive layout in a decade, because it means a component can carry its own responsive behaviour and be reused without the page having to know.\n\n## Many layouts need no breakpoints at all\n\nBefore reaching for a query, check whether the layout can be intrinsic:\n\n```css\n.grid {\n  display: grid;\n  grid-template-columns: repeat(auto-fit, minmax(16rem, 1fr));\n  gap: var(--space-4);\n}\n```\n\nThat reads: as many columns as fit, each at least 16rem, sharing the space equally. One declaration, no breakpoints, correct at every width including ones that do not exist yet. Combined with `clamp()` for type sizes from the type block, a surprising amount of responsive design needs no media queries whatsoever.\n\nThe general principle: prefer a rule that describes the constraint over a rule that enumerates the cases.\n\n## Small first, for a design reason\n\nMobile-first and desktop-first are code organisation preferences and neither is meaningfully better as CSS. What is not merely a preference is designing the small version first, and the reason is nothing to do with implementation.\n\nA 360-pixel column forces prioritisation. There is room for one thing at a time, so you have to decide what comes first, second and third, which is the hierarchy work from the first block, made unavoidable. A 1440-pixel canvas lets you avoid the decision by putting four things side by side, and the resulting design has no hierarchy because nobody ever had to choose.\n\nGoing small to large is therefore addition: you have a working priority order and you are deciding what can now sit beside what. Going large to small is subtraction under pressure, usually the afternoon before a deadline, and it is where features get hidden behind a menu because nobody can face rethinking the order.\n\n## The honest limit\n\nSome content does not fit a phone. A complex comparison table, a dense schematic, a spreadsheet, a seat map.\n\nThe answer there is not a clever responsive trick; it is a different presentation for the small screen: a card per row instead of a table, a filtered subset with a link to the full version, a pinch-zoomable image with explicit controls. Pretending otherwise produces a table at 9 pixels that nobody can read, which is worse than admitting the constraint and designing for it."},"check":{"question":"A card component switches to a horizontal layout at a 768px media query. In the main column it looks right; in a 300px sidebar on a wide desktop it also goes horizontal and becomes cramped. What is the correct fix?","options":[{"text":"Add a more specific media query for the sidebar context, so the card stays vertical when it appears there.","correct":false,"tempting":"Enumerates one more case in a system that will need a new case for every context the card is placed in."},{"text":"Use a container query so the card responds to its own available width rather than to the window's.","correct":true},{"text":"Raise the breakpoint above 768px so the card only goes horizontal on genuinely wide screens where sidebars are not used.","correct":false,"tempting":"Moves the threshold without changing the quantity being measured, so the same mismatch reappears at a different width."},{"text":"Replace the media query with an intrinsic grid using auto-fit and minmax, so the card's internal layout adapts without any query being needed at all.","correct":false,"tempting":"Reaches for the right general preference, but auto-fit governs how many items sit in a track rather than how one component arranges its own parts."}]},"prev":{"slug":"the-numbers-real-devices-have","title":"What a pixel is, and how wide phones actually are","url":"https://addaly.com/learn/design-foundations/the-numbers-real-devices-have"},"next":{"slug":"thumb-reach-and-one-handed-use","title":"Where a thumb can actually go","url":"https://addaly.com/learn/design-foundations/thumb-reach-and-one-handed-use"},"authorship":"Founder and series editor: Dr Mustafa Mun. Written by AI models to a written standard. Source and assessment review continues. Academic review invited.","review":{"status":"Draft, open for academic review"},"cite":"Addaly (2026) 'Breakpoints come from the content, not from devices', in Design, before Any Software. Edited by M. Mun. Addaly. Available at: https://addaly.com/learn/design-foundations/breakpoints-from-content (Accessed: 21 November 2026).","licence":{"name":"CC BY-NC-SA 4.0","url":"https://creativecommons.org/licenses/by-nc-sa/4.0/"},"reader":{"schema":1,"title":"Breakpoints come from the content, not from devices","courseTitle":"Design, before Any Software","module":{"index":6,"slug":"real-screens-and-surfaces","title":"Real screens, real thumbs, real paper"},"answer":null,"keyIdea":"Put breakpoints where your content measurably breaks rather than where devices sit, prefer intrinsic rules and container queries over enumerated cases, and design the small screen first because a narrow column forces the hierarchy decisions a wide one lets you avoid.","hero":{"kind":"plate","image":null,"alt":null,"caption":null},"blocks":[{"t":"h2","id":"naming-breakpoints-after-phones-ages-badly","runs":[{"text":"Naming breakpoints after phones ages badly"}]},{"t":"p","runs":[{"text":"A stylesheet with "},{"text":"$tablet: 768px","code":true},{"text":" was written when there was a tablet at 768 pixels. There are now devices at every width from 320 to 3840, foldables that change width mid-session, split-screen multitasking, and browser windows people resize for no reason."}]},{"t":"p","runs":[{"text":"The method that does not age: "},{"text":"widen and narrow the browser slowly, and put a breakpoint wherever the layout stops working.","b":true},{"text":" Not where a device sits. Where your content breaks."}]},{"t":"p","runs":[{"text":"This produces breakpoints at odd numbers (540, 720, 960, 1180) and that is the sign you did it right. Round numbers usually mean somebody copied them."}]},{"t":"h2","id":"what-breaking-looks-like","runs":[{"text":"What breaking looks like"}]},{"t":"p","runs":[{"text":"The specific failures to watch for as you resize:"}]},{"t":"ul","items":[[{"text":"The measure exceeds 75 characters.","b":true},{"text":" Time to cap the column or add a second one."}],[{"text":"The measure drops below about 35 characters.","b":true},{"text":" Time to drop a column."}],[{"text":"A heading breaks into a bad shape","b":true},{"text":": one word on the second line, or a wrap mid-phrase."}],[{"text":"A horizontal layout has less than about 200 pixels per item.","b":true},{"text":" Cards stop working somewhere around there."}],[{"text":"Navigation runs out of room.","b":true},{"text":" Usually the first thing to break on the way down."}],[{"text":"A table starts scrolling horizontally.","b":true},{"text":" Which means it needs a different presentation, not a smaller font."}]]},{"t":"p","runs":[{"text":"Each of these is a measurement you can take, which is what makes this a technique rather than an aesthetic judgement."}]},{"t":"h2","id":"container-queries-change-the-unit-of-the-question","runs":[{"text":"Container queries change the unit of the question"}]},{"t":"p","runs":[{"text":"A media query asks how wide is the window. That is the wrong question for a component, because the same card might appear in a wide main column, a narrow sidebar and a three-across grid, all on the same page at the same viewport width."}]},{"t":"p","runs":[{"text":"Container queries ask how wide is the space this component has been given:"}]},{"t":"code","lang":"css","label":"CSS","text":".card-wrap { container-type: inline-size; }\n\n@container (min-width: 28rem) {\n  .card { display: grid; grid-template-columns: 8rem 1fr; }\n}"},{"t":"p","runs":[{"text":"The card becomes horizontal when its own container is wide enough, wherever that container happens to be. This has been available across the major browsers since 2023, and it is the most significant change to responsive layout in a decade, because it means a component can carry its own responsive behaviour and be reused without the page having to know."}]},{"t":"h2","id":"many-layouts-need-no-breakpoints-at-all","runs":[{"text":"Many layouts need no breakpoints at all"}]},{"t":"p","runs":[{"text":"Before reaching for a query, check whether the layout can be intrinsic:"}]},{"t":"code","lang":"css","label":"CSS","text":".grid {\n  display: grid;\n  grid-template-columns: repeat(auto-fit, minmax(16rem, 1fr));\n  gap: var(--space-4);\n}"},{"t":"p","runs":[{"text":"That reads: as many columns as fit, each at least 16rem, sharing the space equally. One declaration, no breakpoints, correct at every width including ones that do not exist yet. Combined with "},{"text":"clamp()","code":true},{"text":" for type sizes from the type block, a surprising amount of responsive design needs no media queries whatsoever."}]},{"t":"p","runs":[{"text":"The general principle: prefer a rule that describes the constraint over a rule that enumerates the cases."}]},{"t":"h2","id":"small-first-for-a-design-reason","runs":[{"text":"Small first, for a design reason"}]},{"t":"p","runs":[{"text":"Mobile-first and desktop-first are code organisation preferences and neither is meaningfully better as CSS. What is not merely a preference is designing the small version first, and the reason is nothing to do with implementation."}]},{"t":"p","runs":[{"text":"A 360-pixel column forces prioritisation. There is room for one thing at a time, so you have to decide what comes first, second and third, which is the hierarchy work from the first block, made unavoidable. A 1440-pixel canvas lets you avoid the decision by putting four things side by side, and the resulting design has no hierarchy because nobody ever had to choose."}]},{"t":"p","runs":[{"text":"Going small to large is therefore addition: you have a working priority order and you are deciding what can now sit beside what. Going large to small is subtraction under pressure, usually the afternoon before a deadline, and it is where features get hidden behind a menu because nobody can face rethinking the order."}]},{"t":"h2","id":"the-honest-limit","runs":[{"text":"The honest limit"}],"role":"limit"},{"t":"p","runs":[{"text":"Some content does not fit a phone. A complex comparison table, a dense schematic, a spreadsheet, a seat map."}]},{"t":"p","runs":[{"text":"The answer there is not a clever responsive trick; it is a different presentation for the small screen: a card per row instead of a table, a filtered subset with a link to the full version, a pinch-zoomable image with explicit controls. Pretending otherwise produces a table at 9 pixels that nobody can read, which is worse than admitting the constraint and designing for it."}]}],"check":{"question":[{"text":"A card component switches to a horizontal layout at a 768px media query. In the main column it looks right; in a 300px sidebar on a wide desktop it also goes horizontal and becomes cramped. What is the correct fix?"}],"options":[{"text":[{"text":"Add a more specific media query for the sidebar context, so the card stays vertical when it appears there."}],"correct":false,"tempting":[{"text":"Enumerates one more case in a system that will need a new case for every context the card is placed in."}]},{"text":[{"text":"Use a container query so the card responds to its own available width rather than to the window’s."}],"correct":true,"tempting":null},{"text":[{"text":"Raise the breakpoint above 768px so the card only goes horizontal on genuinely wide screens where sidebars are not used."}],"correct":false,"tempting":[{"text":"Moves the threshold without changing the quantity being measured, so the same mismatch reappears at a different width."}]},{"text":[{"text":"Replace the media query with an intrinsic grid using auto-fit and minmax, so the card’s internal layout adapts without any query being needed at all."}],"correct":false,"tempting":[{"text":"Reaches for the right general preference, but auto-fit governs how many items sit in a track rather than how one component arranges its own parts."}]}],"order":[3,1,0,2],"why":null},"prev":{"slug":"the-numbers-real-devices-have","title":"What a pixel is, and how wide phones actually are","minutes":9},"next":{"slug":"thumb-reach-and-one-handed-use","title":"Where a thumb can actually go","minutes":8}}}