Skip to content
Tutorials Center
My learning

Topics

Lesson 14 of 37 ยท Layout and Design

Responsive Design and Breakpoints

Learn how responsive design works with media queries, mobile-first and desktop-first cascades, Webflow breakpoints and Wix Studio breakpoints, plus fluid sizing and a test plan for every device.

More than half of web traffic for many sites arrives on phones. A page that looks perfect on your desktop monitor and breaks on a phone fails most of its visitors. Responsive design is the practice of making one site adapt to many screen sizes. Both Webflow and Wix Studio build it around breakpoints: widths at which the layout may change.

This lesson explains what a breakpoint really is, how Webflow's cascade and Wix Studio's breakpoint system differ in spirit, how fluid sizing reduces the number of breakpoint fixes you need, and how to test. A resolver stand-in lets you predict which style wins at a given width. Default breakpoint widths in each tool can change, so look at the numbers shown in your editor; we use common values as examples.

What is a breakpoint?

A breakpoint is a viewport width at which a different set of style rules starts to apply. Technically it is a media query:

CSS
/* applies when the viewport is 991px wide or less */
@media (max-width: 991px) {
  .columns { flex-direction: column; }
}

In a builder, you do not write the query. You click a device icon (desktop, tablet, mobile), and changes you make apply from that width downward (or upward), stored as a media query for you.

Two directions of cascade

There are two strategies.

  • Desktop-first (max-width queries): define the large layout as the base, then override for smaller screens. Webflow works this way by default. Its base breakpoint is the desktop view; the tablet, mobile landscape and mobile portrait breakpoints (typically around 991px, 767px and 478px) inherit from larger ones and apply their overrides downward. Webflow also offers larger breakpoints (such as 1280, 1440 and 1920) that apply upward.
  • Mobile-first (min-width queries): define the smallest layout as the base and add rules as the screen grows. Many developers prefer it, because phones load fewer rules.

Because of the downward cascade in Webflow, a style set on the tablet breakpoint also applies on both mobile breakpoints unless a smaller breakpoint overrides it. This is the rule behind countless "why did my mobile change when I edited tablet?" questions.

flowchart LR
  D["Desktop (base)"] --> T["Tablet<br/>inherits desktop"]
  T --> L["Mobile landscape<br/>inherits tablet"]
  L --> P["Mobile portrait<br/>inherits landscape"]

In a desktop-first cascade, a change flows down to smaller screens until something overrides it.

Wix Studio's approach

Wix Studio lets you work on a base breakpoint and then adjust other breakpoints from its breakpoints bar. A change made at the base normally flows to the others unless you override it there, and you can customize layout, size, visibility and some design settings per breakpoint. You can add or edit breakpoint widths. The spirit is the same: define once, override where needed. In the classic Wix Editor, adaptation to phones is handled through a separate mobile view, as discussed in Wix Editor vs Wix Studio Layout.

A breakpoint resolver stand-in

The following simulation stores base styles and overrides for several breakpoints in the desktop-first style, then computes the final style at any width. It makes the cascade explicit.

JS Stand-in: desktop-first breakpoint resolver

Press Run (or Ctrl + Enter) to see the console output here.

No output.

Look at the 600px row: it receives tablet overrides (2 columns, padding 40) and then the mobile-landscape font size, because every breakpoint at or above its width applies. At 400px, mobile portrait overrides columns and padding again.

Reduce breakpoint work with fluid sizing

The fewer overrides you need, the less there is to maintain. Techniques:

  1. Relative widths: percentages and fr units rather than fixed pixel widths.
  2. max-width containers that shrink with the screen.
  3. Wrapping flex rows and auto-fit grids that add or remove columns by available space.
  4. Fluid type and spacing with clamp(): font-size: clamp(1rem, 2vw + 0.5rem, 1.5rem) grows smoothly between a minimum and maximum.
  5. Responsive images that scale to the container (max-width: 100%).
JS Stand-in: how clamp() scales between limits

Press Run (or Ctrl + Enter) to see the console output here.

No output.

The font grows between 16px and 24px with no breakpoint at all. Webflow supports clamp() and other CSS functions in many fields (look for the custom value option), while Wix Studio offers fluid and flexible sizing options in its inspector; check the controls available in your version.

What typically changes at each breakpoint

Breakpoint Typical changes
Large desktop Wider containers, larger spacing
Desktop The base design
Tablet Fewer columns, smaller gaps, simplified navigation
Mobile landscape Stacked sections, smaller headings
Mobile portrait Single column, hamburger menu, larger tap targets, trimmed content

Keep the content the same. Hiding important content on mobile hurts users and can affect SEO, since search engines index the mobile version of your site.

A test plan

  1. Use the builder's breakpoint buttons while designing.
  2. Preview in the builder's preview mode and resize the window slowly: watch for the in-between widths where things break (such as 820px), not just the named devices.
  3. Open the live site on real phones if possible.
  4. Use the browser's device emulation (developer tools) to try common sizes.
  5. Test portrait and landscape, and larger text size settings.
  6. Check touch targets: buttons and links should be at least about 44 by 44 CSS pixels.
  7. Check for horizontal scrolling, which usually indicates something wider than the screen.

Common mistakes

  • Editing on the wrong breakpoint and wondering why other sizes changed.
  • Setting fixed pixel widths on large elements.
  • Using images that are huge on mobile connections.
  • Hiding navigation or key content on mobile.
  • Testing only the exact device widths of one phone.

Check your understanding

Quick check ยท 4 questions

of 4 answered You scored / 4 ยท perfect!

  1. 1. What is a breakpoint?

    A breakpoint is a media query width where layout or style rules change.
  2. 2. In Webflow's desktop-first cascade, a style set on tablet also applies to which sizes?

    Styles cascade downward to smaller breakpoints until a smaller breakpoint overrides them.
  3. 3. What does clamp(16px, X, 24px) guarantee?

    clamp keeps the middle value between the minimum and maximum.
  4. 4. Which is a good practice for mobile?

    Content parity and comfortable touch targets serve users and SEO.

Summary

  • A breakpoint is a width where rules change; builders store them as media queries.
  • Webflow cascades downward from the desktop base (and upward for larger breakpoints); Wix Studio overrides a base per breakpoint; the classic Wix Editor uses a separate mobile view.
  • Fluid sizing (percentages, fr, wrapping, clamp()) reduces the number of breakpoint overrides.
  • Test at many widths, on real devices, and check tap targets and horizontal scroll.

Next: CMS Concepts: Collections, Items and Fields