Breakpoints: Shared Screen Widths Where Layouts Change Shape
Learn what a breakpoint is, why a design system names a small shared set, how to choose them from content, and how to record what changes at each one.
In short
A breakpoint is a shared screen width where a layout changes shape, and a design system names a small set of them and records what changes at each.
15 min readFree
What you will learn
A screen does not stay the same width. A phone is narrow, a laptop is wide, and many people rotate a tablet or resize a browser window. A design has to work at all of these widths. This lesson explains breakpoints, the points where a layout changes shape to fit the space it has. You will learn why a design system sets a small group of shared breakpoints, how to pick them, and how to write them down so every designer and builder uses them the same way.
Key words
- Breakpoint
- A screen width at which a layout changes. Below it, the layout looks one way. At or above it, the layout looks another way.
- Layout
- The way content and parts of a screen are placed: where the menu sits, how many columns there are, and what goes next to what.
- Design system
- A shared set of parts, rules, and values that a team uses to build many screens in the same way.
- Shared value
- A single agreed number or name that everyone uses, instead of each person picking their own.
- Column
- A vertical strip that content sits inside. Two columns means two side-by-side blocks of content.
- Navigation
- The parts of a screen that help people move around, such as a top menu or a side menu.
- Responsive
- A layout that changes its size or shape as the screen changes size.
- Viewport
- The visible area of the screen that a product can use. Designers often mean its width when they say screen width.
What is a breakpoint?
A breakpoint is a width where something has to change. Think of a card list on a website. When the screen is very narrow, one card fits on each row, and the cards stack from top to bottom. When the screen gets wider, two cards can sit side by side without squeezing. At some width, the squeeze begins to hurt, so the layout switches. That switching width is the breakpoint.
Put simply, a breakpoint is the window size at which a layout needs to change to match the available space, the device conventions, and how people use the product.
Changes the columns
A breakpoint can move content from one column to two, or from two to three. Columns are the main thing that changes first.
Changes the navigation
A breakpoint can turn a full menu into a smaller one, or show a side menu that was hidden. Navigation often changes at the same width as the columns.
Changes the arrangement of parts
A breakpoint can move a box below another box, place a panel beside the main content, or hide a part that is not needed at that width.
Tip
A breakpoint is not a rule that the screen must look different. It is a place where the design is allowed to change. Between two breakpoints, the layout should still flex and stretch smoothly.
How do you choose breakpoints?
A good breakpoint sits where the design begins to fail. It is not picked by looking up a list of phone sizes. Many guides agree on this point. One guide says the first rule is to start with the content, not the device. Another says to pick the place where the design actually breaks visually. You find that place by testing the design at many widths.
Content first
Look at what the content needs: titles, pictures, buttons, and text blocks. The breakpoint is where that content starts to need more or less room.
Device models last
A list of popular phone or tablet widths changes over time, and new devices arrive all the time. A breakpoint built on one model can leave gaps for the others.
Few and useful
Each breakpoint should trigger a real, meaningful change. If a change does not help the reader, it is probably not needed.
Some common values are published by large systems. These values are a starting point, not a rule. Your product may need different edges because your content is different.
Find where the design breaks
The best way to find a breakpoint is to test the real design. You do not need a fancy tool for this. Most browsers and design tools let you change the width of the window and watch what happens.
- 1
Start narrow
Begin at the smallest width your product must support. Look at the layout as it is.
- 2
Widen slowly
Make the screen wider by small steps. Watch for cramped text, squeezed pictures, and wrapped buttons.
- 3
Mark the break
When the layout starts to look awkward, mark that width. It is a candidate breakpoint.
- 4
Check whether it repeats
If the same problem appears on many pages, the breakpoint belongs in the shared set. If it only affects one card on one page, fix that card first.
- 5
Stop when the content looks right
Stop adding breakpoints when the content looks right at every width you tested.
Tip
Do not add a breakpoint just because a device has a width you like. Ask this question instead: what does the content need at this width, and will this change help people on many screens?
Keep the number small
More breakpoints mean more layouts to design, build, and test. Each one is another place where the design can go wrong. For a design system, the cost is the same: each extra breakpoint is one more set of rules that every team must learn.
Three to four is common
Many designs work well with three or four named breakpoints. The four-name set in this lesson is a common shape.
Add one only with a reason
Add a breakpoint when a real layout change would help, and when the change applies across the product, not just one screen.
Let parts flex in between
Between breakpoints, parts can stretch or shrink. You do not need a new breakpoint for every small change in width.
Tip
Before you add a breakpoint, ask whether the existing breakpoints can handle the problem with a small flexible change. If they can, do not add a new one.
What changes at a breakpoint?
At each breakpoint, the team decides a few things. Most of them fall into three groups. Write these down for each named breakpoint so that designers and builders can check the same rules.
Columns
How many columns the content uses. Phones often use one column. Wider screens can use two, three, or more.
Navigation pattern
Whether the menu is a short bar, a full top bar, a side panel, or hidden behind a button. Material 3's guidance groups navigation and content into regions that can change at each size.
Component arrangement
Where cards, forms, images, and buttons sit. A component can move below another one, sit beside it, or hide when it is not needed.
Material 3 also describes panes, which are containers that hold content in a layout. Panes are a useful way to think about layout changes, even outside Material.
Some changes are about visibility. Material notes that components and elements can change visibility at larger breakpoints. A part that is too much for a phone screen can appear only when there is room for it.
Worked example: a news homepage
Here is one way a team could use breakpoints on a news site homepage. The example is an illustration of the idea, and the numbers are chosen for teaching. The article list is the main content, so it is the part that changes most. Walk through the steps below and notice how each named breakpoint changes the layout.
- 1
Phone (mobile)
The article list shows as one column of cards. Each card has a picture, a headline, and a short summary. The cards stack from top to bottom, so a reader can scroll one story at a time. The navigation stays compact so it does not take up the top of the screen.
- 2
Tablet
At the tablet breakpoint, the same cards move into a two-column grid. Two stories sit side by side. The cards still have the same parts, so the design feels familiar. The reader gets more stories on one screen without the text becoming cramped.
- 3
Desktop
At the desktop breakpoint, the layout adds a sidebar beside the article list. The sidebar can hold related links or a list of sections. The full top navigation also appears, so the main sections are visible at once.
- 4
Between the breakpoints
Between the tablet and desktop ranges, the cards grow or shrink a little, and the spacing stays steady. There is no sudden change until the next breakpoint is reached.
- 5
Record the result
The team writes down, for each named breakpoint, the number of columns, the navigation pattern, and the parts that appear or move. Now a designer building a new section knows what to expect at each width.
Tip
Notice what did not change. The card design, the headline style, and the picture ratio stayed the same at each breakpoint. A breakpoint changes the arrangement. It does not need to change every detail.
How do you document each breakpoint?
A breakpoint that is not written down is easy to forget. A written record is what keeps the whole team aligned. The record should be short, clear, and easy to find. It should cover the name, the range, and the changes that happen inside that range.
- 1
Give it a plain name
Use a name that describes the space, such as tablet or desktop. Avoid naming it after a product or a device model.
- 2
Write its range
Write where the range starts and where it ends. For example, the tablet range starts at its edge and stops just before the desktop range begins. Make sure the ranges do not overlap or leave gaps.
- 3
List the columns
Say how many columns the content uses in that range, and say where the content sits.
- 4
Describe the navigation
Say which navigation pattern appears in that range, and what it looks like when someone taps or clicks it.
- 5
Describe the arrangement
List the components that move, hide, or appear, so builders know what to build.
- 6
Add examples
Include a screenshot or a sketch at the start and end of the range so people can see the change.
- 7
Keep a history
When the team changes an edge or a rule, note the date, the reason, and the people who agreed. This is part of governance, which has its own lesson.
The same list works for every named breakpoint. When a designer and a builder both read the same record, the product will change shape in the same way on every page.
Tip
Write the record for someone who has never seen the product. If a new designer can read it and build a page correctly, the record is good enough.
Common mistakes to avoid
Picking widths for one screen
A breakpoint made for one page often causes problems on other pages. Check whether the change should apply across the product before you add it.
Copying device widths
A list of phone and tablet widths goes out of date. Use the content as the guide.
Too many names
Many names are hard to remember and hard to maintain. A short set is easier for everyone.
No written record
If the ranges and changes are not written down, each team will guess. Write them down early.
Skipping the test
A breakpoint that looks right on your large monitor may fail on a narrow window. Test at the smallest and largest widths you support.
Check your understanding
Quick check
Your team's product page looks fine at 1440 pixels wide and at 375 pixels wide. At 800 pixels, the product cards are squeezed and the text wraps in awkward places. A designer suggests adding a new breakpoint at 800 pixels that only applies to one popular tablet model. What is the best response?
Next, read a short scenario about the names and ranges in a shared record.
Quick check
Your design system defines a tablet range and a desktop range. A designer wants the two-column grid to start at a width that is slightly lower than the current tablet edge. She has tested the change on one page, and it looks better there. What should she do?
Summary
A breakpoint is a width
It is the place where a layout changes shape, such as columns, navigation, or arrangement of parts.
A design system shares them
A small set of named breakpoints keeps every screen consistent and makes handoff easier.
Content decides the edges
Find breakpoints by testing where the content breaks, not by copying device widths.
Keep the number small
Use few breakpoints, and add one only when a real change helps the reader.
Write it down
Record each name, its range, and what changes inside it, so designers and builders work from the same rules.
Next, you can read how grids, flexible sizing, and units work inside these ranges. Those lessons build on the breakpoints you have learned here.
Sources
- Material Design 3: Breakpoints (applying layout)
- Material Design 3: Layout overview, adaptive design
- Material Design 3: Scaffold and panes
- Android Developers: Use window size classes
- Carbon Design System: 2x Grid overview
- Webflow blog: How to use breakpoints to create responsive websites
- BrowserStack: A Complete Guide to CSS Media Query Breakpoints
- 1440px: How to Choose Responsive Breakpoints
- 1440px: Material Design 3 Breakpoints
- DEV Community: Responsive Web Design Breakpoints, Layouts and Real Testing Guide
- Peasy Math: Responsive Design Breakpoints, Modern Best Practices
- aamax: Responsive Web Design Common Breakpoints
- DevToolsHub: Responsive Breakpoints Guide
Last updated on 17 November 2026
Related lessons
Learn with me
Every lesson is free. I add new ones as I learn. Have a question, or want help with your own work? Book a short call.