What media query breakpoints should I use?

Let's dive into the most common media queries are used in frameworks today

Written by Rico Sta. Cruz
(@rstacruz) · 25 Apr 2019
Image
In this article:
  1. Devices
  2. Common breakpoints in frameworks
  3. So what should I use?
  4. How should I name them?
  5. Thank you!

Devices

Before we can figure out what media query breakpoints to use, we need to look at what devices we’re designing for. I’ve dug into some common device resolutions, and most can be grouped into categories. I’ve listed these categories, along with the resolutions they cater to:

DeviceWidth
Mobile portrait
For devices with 4” to 6.9” screens.
320px414px
Mobile landscape
Same, but landscape.
568px812px
Tablet portrait
For devices 7” to 10”
768px834px
Tablet landscape
Ditto, but also 12” tablets on portrait
1024px1112px
Laptop & desktop displays
Varies a lot, but is usually 1200px and above
1200px+

Viewport widths of common devices

I mostly looked at iOS devices. While Android devices are important too, they have a lot of variance—device DPI’s are adjustable in most phones. Most Android phones ship with defaults that are comparable to iOS’s anyway, so let’s look at those:

CategoryWidthDevice
Mobile, portrait320pxiPhone SE
375pxiPhone 6, 7, 8, X
414pxiPhone 8 Plus
Mobile, landscape568pxiPhone SE
667pxiPhone 6, 7, 8
736pxiPhone 8 Plus
812pxiPhone X
Tablet, portrait768pxiPad Air, iPad Mini, iPad Pro 9”
834pxiPad Pro 10”
Tablet, landscape1024pxiPad Air, iPad Mini, iPad Pro 9”
1024pxiPad Pro 12” (portrait)
1112pxiPad Pro 10”
Laptop displays1366pxHD laptops (768p)
1366pxiPad Pro 12” (landscape)
1440px13” MacBook Pro (2x scaling)
Desktop displays1680px13” MacBook Pro (1.5x scaling)
1920px1080p displays

Common breakpoints in frameworks

I took a look at some of the most popular CSS frameworks on 2019 (and some from the past) to see what breakpoints they use. Most of them use the same points, with a small bit of variance.

FrameworkSmallMediumLargeExtra large
Bulma-min: 769px (“mobile”)min: 1024px (“desktop”)min: 1216px (“fullhd”)
Bootstrap 3-min: 768pxmin: 992pxmin: 1200px
Bootstrap 4min: 576pxmin: 768pxmin: 992pxmin: 1200px
Tailwindmin: 576pxmin: 768pxmin: 992pxmin: 1200px
Zurb Foundation-min: 640pxmin: 1024pxmin: 1200px

768px, 992px, 1200px

Many frameworks use 768px, 992px and 1200px. This has been Bootstrap 3’s default breakpoints, and seems to be considered sensible enough to have been adopted by other projects.

No small breakpoints?

Some opt not to have breakpoints below 700px. This is likely taken from Bootstrap 3, which advocated making the mobile landscape view the same as the portrait view. Bootstrap 4 has since changed their position on this, which I personally agree with—seeing tall headers on a landscape screen is pretty annoying!

Where did 576px come from?

Before Bootstrap 4 added the 576px breakpoint, 480px was a popular choice. 576px was eventually chosen since it was roughly halfway between 320px and 768px (+32px). I personally don’t think choosing 576px over 480px is a big deal (or the other way around); either one should be enough to cover the 414px width of the iPhone 8 Plus. However, I prefer 480px since 576px still covers the iPhone SE landscape view.

640px

Zurb’s 640px breakpoint is an interesting choice. It covers both tablet-portrait and (most of) mobile-landscape.

So what should I use?

This is mostly subjective and may depend on what screens you would design for. I use this set of breakpoints as a starting point, and I can recommend them for most projects.

BreakpointPurpose
(default)Mobile-portrait
min-width: 480pxMobile-landscape (and larger)
min-width: 768pxTablet-portrait (and larger)
min-width: 992pxTablet-landscape (and larger)
min-width: 1200pxLaptops (and langer)

Avoid max-width

I prefer only using min-width and avoiding max-width as much as possible. Mixing min-width and max-width can make CSS code shorter, but much more difficult to read.

Offset your max-widths

If you must you max-width, be sure to offset it by at least 0.02px. That is, use max-width: 479.98px instead of max-width: 480px, since the latter will have a small overlap with min-width: 480px.

480px or 576px?

I suggest using 480px instead of 576px simply because it would cover smaller phones as well (eg, iPhone SE).

Should I use 768px?

The min-width: 768px might not be as useful as most would think. If you’re designing for tablet-portrait, consider using min-width: 480px, it might look good on mobile-landscape as well. Zurb Foundation seems to promote this idea of co-designing for mobile-landscape + tablet-portrait too, considering they use 640px as a breakpoint.

The mystery of 768px

The min-width: 768px breakpoint is often described in guides as “tablet landscape”. This is misleading, because it also matches tablet-portrait mode as well. Use min-width: 992px if you need to target tablet-landscape. (You can also use 769px, but that won’t cover iPad Pro 10”.)

How should I name them?

I personally don’t like calling things small, medium and large. These words can be ambiguous; does an iPad Pro 10” count as medium or large? Would the iPhone SE be counted as extra small? These words are relative, and their subjectiveness can cause some confusion.

I’m not a fan of calling them mobile, tablet and so on, either. The iPad Pro 12” is a tablet, but why can you only target it with a desktop media query? The Samsung Note is technically a phone, but why is it covered with tablet? Does tablet account for landscape or portrait? The lines between device classifications are a bit blurry nowadays.

Instead, I propose calling it with more generic names. Most designers are intimately familiar with “how 700px feels like”, so I think that would make a more appropriate name. I like naming them by their closest hundredths like so.

@custom-media --viewport-4 (min-width: 480px);
@custom-media --viewport-7 (min-width: 768px);
@custom-media --viewport-9 (min-width: 992px);
@custom-media --viewport-12 (min-width: 1200px);
@media (--viewport-4) {
/* ... */
}

Thank you!

I hope you’ll find all these helpful. References:

Written by Rico Sta. Cruz

I am a web developer helping make the world a better place through JavaScript, Ruby, and UI design. I write articles like these often. If you'd like to stay in touch, subscribe to my list.

Comments

More articles

← More articles