Skip to main content
RapidDev - Software Development Agency
webflow-tutorials

Webflow Responsive Design: Breakpoints and Mobile Layouts

Webflow uses a cascade-down breakpoint system starting at Desktop (base). Styles set on Desktop inherit to Tablet and Mobile unless overridden. Switch breakpoints using the bar above the canvas and apply styles only where needed. Use the 'None' display value to hide elements at specific breakpoints, and viewport units (vw, vh) for fluid sizing that responds to screen dimensions.

What you'll learn

  • Understand Webflow's cascade-down breakpoint system and how Desktop styles inherit to mobile
  • Override styles at specific breakpoints without affecting Desktop or larger sizes
  • Hide and show elements per breakpoint using Display: None vs a visibility toggle
  • Add optional large-screen breakpoints (1440px, 1920px) that cascade upward from Desktop
  • Use viewport units (vw, vh, svh) for fluid sizing and full-screen layouts
Book a free consultation
4.9Clutch rating
600+Happy partners
17+Countries served
190+Team members
Intermediate10 min read25-35 minAll Webflow plans (custom code requires Basic plan or above)March 2026RapidDev Engineering Team
TL;DR

Webflow uses a cascade-down breakpoint system starting at Desktop (base). Styles set on Desktop inherit to Tablet and Mobile unless overridden. Switch breakpoints using the bar above the canvas and apply styles only where needed. Use the 'None' display value to hide elements at specific breakpoints, and viewport units (vw, vh) for fluid sizing that responds to screen dimensions.

Webflow Responsive Design: Breakpoints, Cascading Styles, and Mobile Layouts

Webflow's breakpoint system is built around one rule: Desktop is the base, and styles cascade DOWN to smaller screens. Every style you set on Desktop is inherited by Tablet, Mobile Landscape, and Mobile Portrait — unless you override it at a smaller breakpoint. This tutorial explains the cascade direction, how to add large-screen breakpoints (1440px, 1920px) that cascade UP from Desktop, how to hide elements per breakpoint, how to use viewport units for fluid layouts, and how to avoid the most common responsive mistakes that leave sites broken on mobile.

Prerequisites

  • A Webflow project with at least one designed Desktop layout
  • Familiarity with the Style Panel (S) and basic class/selector concepts
  • Understanding that Webflow's Navigator (Z) shows the element hierarchy

Step-by-step guide

1

Understand the breakpoint bar and cascade direction

The breakpoint bar sits above the canvas in the Webflow Designer. From left to right: 1920px (optional), 1440px (optional), 1280px (optional), Desktop (the base — ≥992px), Tablet (≤991px), Mobile Landscape (≤767px), Mobile Portrait (≤478px). Desktop is the anchor. Styles on Desktop cascade DOWN (to smaller) automatically. Optional large breakpoints (1440px, 1920px) cascade UP from Desktop using min-width media queries. Click each breakpoint pill to switch the canvas view. When you make a style change, an orange dot indicator appears on that breakpoint to show it has local overrides. A blue indicator means the style inherited from another breakpoint. You only need to add styles where the inherited Desktop style needs to change.

Expected result: You understand which breakpoint is currently active (canvas label shows the breakpoint name) and how styles flow from Desktop down to Mobile Portrait.

2

Make Desktop layout responsive for Tablet

Click the Tablet breakpoint pill in the breakpoint bar. Your canvas now shows a ~991px wide viewport. Elements that worked at Desktop may look cramped or overflow. Identify layout issues: multi-column Flexbox rows that need to stack vertically, text that's too large, or padding that's excessive. For each issue, select the element, make your adjustment in the Style Panel, and the change will apply ONLY to Tablet and below (cascading down). For a three-column Flex container that should become two columns at Tablet: select the parent Flex container, Style Panel > Layout > Flex > change Wrap to 'Wrap', and each child element to Width: 50%. The orange dot on the Wrap and Width properties confirms the Tablet-specific override.

Expected result: Your layout at Tablet breakpoint looks clean without horizontal overflow. Multi-column layouts that needed to stack are now wrapping correctly.

3

Hide and show elements per breakpoint

To hide an element at a specific breakpoint, select it and switch to that breakpoint. In Style Panel > Layout > Display, select 'None'. The element disappears at that breakpoint and all smaller ones. To show a mobile-only element (like a simplified mobile menu or a stacked version of a desktop comparison table), create the element and set Display: None on Desktop. Switch to Mobile Portrait and set Display: Flex (or Block). Important: Display: None actually removes the element from the rendering (unlike visibility: hidden which only hides it visually). This is the correct approach for responsive hiding. In the Designer canvas, hidden elements show with a strikethrough in the Navigator.

Expected result: Desktop-only elements (like a horizontal desktop nav) are hidden on Mobile. Mobile-only elements (like a hamburger menu icon) are hidden on Desktop. Each breakpoint shows the appropriate version.

4

Add large-screen breakpoints for widescreen displays

Enable large breakpoints from the breakpoint bar. Click the '+' icon on the left side of the breakpoint bar (or hover over the area to the left of Desktop) and add 1440px. You can also add 1280px and 1920px. These breakpoints use min-width media queries and cascade UP from Desktop. Styles on the 1440px breakpoint apply only on screens ≥1440px. Use these to: prevent containers from stretching too wide (add max-width constraints), increase font sizes for very large displays, or adjust grid column counts for ultrawide screens. A common pattern: set section containers to Max Width: 1280px and Margin: 0 auto on Desktop, then at 1440px increase max-width to 1440px. Important: once you enable a large breakpoint, it cannot be deleted.

Expected result: Your site layout scales gracefully on widescreen monitors without content stretching across the full viewport width.

5

Use viewport units for fluid sizing

Viewport units make elements respond to the browser window size rather than parent containers. In the Style Panel, any size input field (width, height, font-size, padding, margin) accepts viewport units. Type your value followed by 'vw' (viewport width), 'vh' (viewport height), or 'svh' (small viewport height — accounts for mobile browser chrome). Common patterns: Set a section Height to 100vh for full-screen sections. Set a hero heading font-size to 6vw so it scales with the screen width. Set a container Max Width to 90vw so it has consistent side margins. For mobile-safe full-screen heights, use 100svh (small viewport height) instead of 100vh — 100vh on iOS Safari includes the browser toolbar height and causes overflow.

Expected result: Full-screen sections fill exactly the visible viewport on all devices. Heading font sizes scale proportionally with screen width.

6

Override typography settings at Mobile breakpoints

Typography set at Desktop often needs adjustment at mobile sizes. Switch to Mobile Portrait breakpoint (≤478px). Select your main heading (H1). In Style Panel > Typography, change Font Size to 28px (from Desktop's 48px). The orange dot confirms this is a Mobile Portrait-specific override. Set line-height to 1.2 if the heading wraps to multiple lines on small screens (tighter line-height works better for 2-line headings). For body text, reduce from 16px to 15px if space is tight. For button padding, reduce horizontal padding from 24px to 16px. These overrides cascade from Mobile Portrait to nothing smaller (it's the smallest breakpoint) — so they're safe changes.

Expected result: Headings, body text, and buttons are appropriately sized for Mobile Portrait without looking cramped or uncomfortably large.

7

Test and debug the full responsive layout

Switch through each breakpoint from largest to smallest and check for: (1) Horizontal overflow — elements wider than the viewport causing horizontal scroll. Fix: select the overflowing element, check Width in Style Panel, switch to % or remove a fixed px width. (2) Text overflow — text breaking out of its container. Fix: check parent element width and add overflow: hidden or word-break: break-word via Custom Properties. (3) Spacing inconsistency — gutters that are too large on mobile. Fix: override padding/margin at the Tablet or Mobile Portrait breakpoint. (4) Stacked elements with incorrect order — Flex column direction reverses the visual order. Use the Flex Order property (Custom Properties > 'order') to reorder elements visually at a breakpoint without changing HTML structure.

Expected result: No horizontal overflow exists at any breakpoint. All content is readable and usable on Mobile Portrait. Layout transitions gracefully between breakpoints.

Complete working example

Visual Steps Summary
1RESPONSIVE BREAKPOINTS VISUAL STEPS SUMMARY
2
3BREAKPOINT BAR (left to right):
4 1920px (optional, add via '+') cascades UP (min-width)
5 1440px (optional, add via '+') cascades UP (min-width)
6 1280px (optional, add via '+') cascades UP (min-width)
7 Desktop (BASE 992px) all styles start here
8 Tablet (991px) DOWN from Desktop
9 Mobile Landscape (767px) DOWN from Tablet
10 Mobile Portrait (478px) smallest breakpoint
11
12CASCADE RULE: Set styles on Desktop. Only override where the Desktop style breaks.
13
14HIDING ELEMENTS PER BREAKPOINT:
15 At target breakpoint > Style Panel > Layout > Display > None
16 (NOT opacity: 0 that leaves layout gaps)
17
18FLUID SIZING:
19 Full-screen sections: Height > 100svh (not 100vh on mobile)
20 Responsive font: Font Size > 6vw
21 Side margins: Max Width > 90vw
22
23COMMON MOBILE FIXES:
24 H1: Desktop 48px Tablet 36px Mobile Portrait 28px
25 Section padding: Desktop 80px Tablet 60px Mobile 40px
26 Flex containers: Wrap = Wrap at Tablet, column-direction on Mobile

Common mistakes

Why it's a problem: Style changes at Mobile are affecting Desktop layouts

How to avoid: You may have changed styles while on the Desktop breakpoint when you intended to be on a smaller one, OR the change was made at a large breakpoint that cascades UP and affects Desktop. Check the current breakpoint indicator in the canvas before making changes. If you accidentally changed Desktop, select the element, switch to Desktop breakpoint, and use Cmd+Z to undo, then switch to the correct breakpoint and re-apply.

Why it's a problem: Hiding an element with Display: None on Desktop but it's still showing on Mobile

How to avoid: Check if the Mobile breakpoint has an override that re-enables the Display value. Select the element at the Mobile breakpoint, open Style Panel > Layout > Display — if you see an orange dot, a breakpoint-specific override is showing the element. Click the orange dot or the 'X' that appears next to the Display value to remove the override, allowing it to inherit 'None' from Desktop.

Why it's a problem: Full-screen section on mobile shows a scrollbar or leaves a gap below

How to avoid: You're using 100vh which on iOS Safari includes the browser toolbar area. Change the Height value from '100vh' to '100svh' (small viewport height) in the Style Panel > Size section at the Mobile Portrait breakpoint. svh calculates the available visible height after subtracting the browser chrome.

Why it's a problem: Content looks correct at 991px Tablet breakpoint but breaks at 850px

How to avoid: Webflow Designer shows fixed breakpoint widths but your site renders at all screen sizes. Preview your published site and resize the browser window manually to catch issues at non-breakpoint widths. The fix is usually making widths percentage-based (50%, 33%) rather than fixed pixels, or adding a max-width to prevent excessive stretching.

Best practices

  • Design desktop-first completely before working on mobile. Going back to change Desktop after setting mobile overrides creates a maintenance nightmare.
  • Use Display: None (not opacity: 0) to hide elements at specific breakpoints — Display: None removes the element from layout flow so it doesn't create empty space.
  • Prefer percentage widths and max-width constraints over fixed pixel widths for containers — this makes layouts naturally responsive without needing as many breakpoint overrides.
  • Use 100svh instead of 100vh for mobile full-screen sections to account for iOS Safari's dynamic browser toolbar.
  • Test between breakpoints by resizing the browser window in Preview mode, not just at the fixed breakpoint widths in the Designer — fluid layouts can have issues at intermediate viewport sizes.
  • Audit orange dot indicators (breakpoint-specific overrides) periodically to keep track of what you've customized at each level and prevent conflicts as you iterate.

Still stuck?

Copy one of these prompts to get a personalized, step-by-step explanation.

ChatGPT Prompt

I'm building a responsive website in Webflow and I'm confused about the breakpoint cascade system. When I change a style on Mobile, does it also change Desktop? How do I properly hide a navigation element on mobile that should still show on desktop? What is the correct way to set up full-screen sections on mobile without the iOS Safari viewport height bug? Walk me through Webflow's responsive design system step by step.

Webflow Prompt

Make this Webflow page fully responsive. The three-column flex layout should become two columns on Tablet and one column (stacked) on Mobile Portrait. Reduce H1 from 48px to 28px on Mobile. Hide the desktop horizontal navigation on Mobile Portrait. Ensure all full-screen sections use 100svh instead of 100vh.

Frequently asked questions

If I change a style on Tablet in Webflow, does it change Desktop too?

No. Styles only cascade DOWN (to smaller breakpoints), never up. If you make a change on Tablet, it affects Tablet, Mobile Landscape, and Mobile Portrait. Desktop and any large breakpoints above it are unaffected. This is why the rule is 'design Desktop first' — Desktop is the base that everything inherits from, and smaller breakpoints only override what Desktop defined.

What is the difference between hiding an element in Webflow's Navigator vs using Display: None at a breakpoint?

Hiding in the Navigator (eye icon) hides the element only in the Designer canvas — it still renders on the published site. This is a 'hide while editing' toggle, not a production visibility control. Display: None in the Style Panel (at a specific breakpoint) is a real CSS property that prevents the element from rendering on the live site at that breakpoint. Always use the Style Panel Display: None for production responsive hiding.

Can I target screen sizes between Webflow's fixed breakpoints, like 600px?

Not directly through Webflow's breakpoint bar, which uses fixed thresholds. For intermediate screen sizes, you need custom CSS media queries injected in Page Settings > Head Code (requires paid plan). For example: @media screen and (max-width: 640px) { .my-element { font-size: 14px; } }. Most responsive issues can be solved with percentage-based widths and fluid techniques that handle the transitions between breakpoints smoothly without needing intermediate breakpoints.

RapidDev

Talk to an Expert

Our team has built 600+ apps. Get personalized help with your project.

Book a free consultation

Need help with your project?

Our experts have built 600+ apps and can accelerate your development. Book a free consultation — no strings attached.

Book a free consultation

We put the rapid in RapidDev

Need a dedicated strategic tech and growth partner? Discover what RapidDev can do for your business! Book a call with our team to schedule a free, no-obligation consultation. We'll discuss your project and provide a custom quote at no cost.