What Are Breakpoints in Web Design? A Beginner-Friendly Guide

By Seahawk September 24, 2026 5 min read

A site that looks great on a laptop can fall apart on a phone, and breakpoints are usually the reason. They are the widths at which your layout changes. In this Seahawk Learn video, Toeer shows breakpoints firing live in the browser inspector, compares what Tailwind CSS and Bootstrap do by default, and explains why designing for individual devices is a losing game.

Seahawk Learn · What Are Breakpoints in Web Design? A Beginner-Friendly Guide · 12:06

Here is the same material in written form, with practical advice on setting your own.

What a breakpoint is

A breakpoint is a screen width at which the design adapts. Below the breakpoint the layout might stack in one column, above it the same content might sit in three. You do not move to a different page. The browser applies different CSS rules based on the width of the viewport.

You can see this yourself, and the video starts with exactly that: open your browser's developer tools, drag the page width narrower or wider, and watch the layout shift at certain points.

How media queries work

Breakpoints are written with CSS media queries. A typical rule reads @media (min-width: 768px) { .card-grid { display: grid; grid-template-columns: repeat(3, 1fr); } }, which says that when the viewport is at least 768 pixels wide, the grid appears. Below that width, the styles outside the query apply. Writing the base styles for small screens and adding rules with min-width as the screen grows is known as mobile-first, and it keeps CSS shorter and easier to reason about.

If a rule in your theme does not seem to apply, our guide to fixing media queries that do not work in WordPress covers the common causes.

Why coding for each device does not work

It is tempting to build for a specific phone: one size for the iPhone SE, another for a tablet. The video argues against this, and the reasons are practical. New devices appear constantly, screen sizes vary widely, and people resize browser windows, split screens and rotate their devices. A layout built around named devices will always be out of date.

Content is a better guide than devices. Build the layout, then widen or narrow the window until something looks wrong, such as a line that is too long or a column that is too cramped. That is where a breakpoint belongs.

Default breakpoints in Tailwind CSS and Bootstrap

Frameworks ship with sensible defaults so you do not start from nothing. The video compares Tailwind CSS and Bootstrap and notes that they differ. In current versions:

  • Tailwind CSS uses 640, 768, 1024, 1280 and 1536 pixels as its small to 2xl breakpoints.
  • Bootstrap uses 576, 768, 992, 1200 and 1400 pixels for its small to xxl breakpoints.

Both start from small screens and apply min-width rules as the viewport grows. That the numbers do not match is itself the lesson: there is no universal standard, only conventions. Check each framework's documentation for the current values, as they can change between versions.

How WordPress themes and builders handle breakpoints

If you build with WordPress, you often never write a media query yourself. The video looks at how Cadence, Elementor, Divi, GeneratePress and Neve manage breakpoints. Each theme or builder gives you device previews and settings, and they apply the right CSS behind the scenes. Elementor, for instance, lets you adjust the layout per device and enable more breakpoints, which we cover in best practices for Elementor breakpoints.

The catch is that each tool uses its own values, so a section that switches at one width in one builder may switch at another width elsewhere. When you move between tools, test again instead of assuming the same result.

How to decide your own breakpoints

The video's closing advice is about thinking, not numbers. Use this process:

  1. Start with the smallest screen and make the content readable and the buttons easy to tap.
  2. Widen the browser slowly and note where the layout starts to look stretched or too empty.
  3. Add a breakpoint at that point, not at a device width.
  4. Repeat until the design works at large sizes too.
  5. Keep the number of breakpoints low. Fewer breakpoints mean less CSS and fewer places for bugs.

Flexible layout methods reduce how many breakpoints you need. Our article on using CSS Grid and Flexbox explains how layouts can adapt without a rule at every width.

Testing without owning every device

Testing on real devices matters, but nobody owns them all. The video covers practical, low-cost ways to check your work, and you can watch breakpoints fire in DevTools as you resize. The device toolbar in browser developer tools is the quickest start, and an old phone or tablet adds a real check. Real devices still catch problems that emulation misses, such as touch behavior and font rendering, so check at least one phone and one tablet before launch.

What the video covers

  • 0:00 What this video covers
  • 0:27 Live demo: breakpoints in the browser inspector
  • 4:05 Why coding per device is unsustainable
  • 5:29 How media queries are written
  • 6:12 Tailwind CSS default breakpoints
  • 7:00 Bootstrap default breakpoints
  • 7:50 WordPress theme breakpoints (Cadence, Elementor, Divi, Neve)
  • 9:00 Testing on real devices without owning them all
  • 10:25 Watching breakpoints fire in DevTools
  • 11:10 How to decide your own breakpoints

Responsive design is broader than width alone. If you are comparing approaches, see how a reactive website differs from a responsive one, and how a mobile site differs from a responsive site.

What to take away

Let your content set the breakpoints, keep them few, and test on real screens. Rely on your theme's defaults unless something looks wrong, and when it does, adjust the layout at that width instead of chasing devices.

FAQs

What is a breakpoint in CSS?

A breakpoint is a viewport width at which your CSS rules change, usually written with a media query. It lets the same page adapt to small and large screens.

What are the default breakpoints in Tailwind and Bootstrap?

In current versions, Tailwind uses 640, 768, 1024, 1280 and 1536 pixels, and Bootstrap uses 576, 768, 992, 1200 and 1400 pixels. They differ, so check each framework's documentation.

Should I set breakpoints for specific devices?

No. The video explains that device-specific coding is unsustainable. Set breakpoints where your content starts to look wrong as the width changes.

Do I need to write media queries in WordPress?

Often not. Themes and builders such as Cadence, Elementor, Divi, GeneratePress and Neve handle breakpoints through their own settings, though you can add custom CSS when needed.

Seahawk Learn for brands

Want a deeper dive than a product review?

Product reviews are short write-ups. A Seahawk Learn video goes deeper: a full walkthrough of your product on our YouTube channel and here, with a written step-by-step guide.