Guides · Responsive

Choosing useful responsive breakpoints

A breakpoint should appear when the layout stops working properly, not simply because a width matches a known phone model.

Practical guideResponsive

Start from the narrow layout

A mobile-first approach forces the essential structure to work before extra space is introduced. Media queries then enhance the layout when content can support it.

  • Build a readable single-column base first.
  • Add columns only when they remain comfortably wide.
  • Keep touch targets usable at every stage.

Watch the content, not devices

Resize the viewport gradually and note when lines become too long, cards too narrow or navigation runs out of room.

  • Add a breakpoint at a genuine visual failure point.
  • Avoid one rule for every device model.
  • Test intermediate widths, not only 375 and 1440 pixels.

Keep breakpoints under control

A few coherent breakpoints are often easier to maintain than many small corrections placed close together.

  • Group adaptations that solve the same problem.
  • Use fluid grids before adding another media query.
  • Document the structural thresholds used by the project.

Practical checklist

  • Readable mobile base without complex queries.
  • Breakpoints triggered by content needs.
  • Intermediate widths tested.
  • A limited, coherent set of breakpoints.
  • Navigation and buttons remain touch friendly.

Conclusion

Well-chosen breakpoints make responsive design more robust and prevent the project from chasing an endless list of screen sizes.