Figma to Webflow

How to Hand Off Responsive Breakpoints from Figma So Mobile Doesn't Get Guessed

TS Talha Shahzad··9 min read
The short version
  • Design desktop plus mobile at minimum; add tablet for tricky sections only.
  • Note reflow intent where layout changes, not just how it looks but how it should behave.
  • Specify what stacks versus what hides on mobile.
  • Webflow cascades styles top-down, so design desktop-first to match the build flow.
  • Ambiguous mobile specs lead to revision rounds that cost more than designing them upfront.

Most Figma files I receive include one breakpoint: desktop. The designer builds every page at 1440px, delivers the file, and the developer is left to invent what mobile looks like. That is when things go wrong.

Inventing mobile is not a quick step. It is a series of design decisions disguised as development tasks. What stacks? What hides? What changes size? What reflows into a different arrangement? Every one of those decisions takes time, and when the developer guesses differently from what the founder or designer expected, the result is revision rounds that cost more than designing the breakpoints would have.

After 450+ Webflow builds, I can tell you this is one of the most expensive habits in the handoff. A desktop-only Figma file inflates the build timeline with developer questions, best-guess implementations, and correction cycles. Designing two to three breakpoints upfront is the single most effective way to keep a Webflow project on budget.

What Webflow needs from the Figma file

Webflow uses a cascading breakpoint system. You style the site at the desktop breakpoint, and those styles flow down to smaller screens. Then you override only what needs to change at tablet, mobile landscape, and mobile portrait.

This means the developer does not need a pixel-perfect design at every breakpoint. They need:

  1. Desktop layout (1440px). The primary design. This is where all base styles get set.
  2. Mobile layout (375px or 390px). The smallest view. This is where the most dramatic layout changes happen: columns stack, navigation collapses, font sizes shrink, sections simplify.
  3. Tablet layout (768px or 991px). Only needed for sections where the reflow between desktop and mobile is not obvious. If a section goes from three columns to one column, tablet might need to show two columns. If the reflow is straightforward (three columns simply stacking to one), the developer can handle that without a tablet frame.

That is the minimum. Desktop plus mobile for every page. Tablet for the tricky sections. You do not need to design every component at every size, just the sections where the layout behavior changes in a way that is not self-evident.

Design desktop-first to match the build flow

This is important because it matches how Webflow actually works. Webflow cascades top-down: desktop styles apply everywhere, and you add overrides at smaller breakpoints. If you design mobile-first in Figma and hand that to a Webflow developer, the developer has to mentally reverse the cascade to figure out what the desktop base styles should be.

Design the desktop layout as the primary file. Then create mobile frames that show how each section adapts. The developer reads the desktop file as "this is the base," reads the mobile file as "this is what changes," and builds accordingly.

If you are working in Figma with auto layout, the desktop frames should use auto layout direction and properties that map naturally to flexbox. Horizontal rows at desktop often become vertical stacks at mobile. That mapping is intuitive for developers, and seeing it explicitly in both the desktop and mobile frames removes ambiguity.

What to show in the mobile frames

The mobile frame is not a scaled-down desktop. It is a different layout with different priorities. Here is what needs to be explicit:

What stacks. Three columns at desktop usually stack to one column on mobile. But in what order? Top to bottom following left to right? Or does one column jump to the top because it is more important? If the order changes from the desktop reading order, note it.

What hides. Some elements should not appear on mobile at all. A large decorative illustration, a secondary sidebar, a wide data table that does not work at 375px. If something should hide on mobile, it needs to be absent from the mobile frame. Do not leave it in and hope the developer notices it does not fit.

What changes size. Hero images might crop differently on mobile. Heading text almost always needs to be smaller. Padding usually tightens. Show the actual sizes in the mobile frame, do not rely on the developer to calculate proportional reductions.

What changes behavior. Desktop navigation becomes a hamburger menu. A horizontal tab bar becomes an accordion. A hover tooltip becomes a tap-to-reveal. These behavioral changes need to be noted because they require different Webflow components, not just different styling.

What changes content. Sometimes the mobile version should show different text. A desktop headline that says "The Complete Platform for Revenue Operations" might need to be "Revenue Ops Made Simple" on mobile because the full text wraps awkwardly at 375px. If the content changes, show it in the mobile frame.

How to annotate reflow intent

Not everything can be communicated through layout frames alone. Some decisions need written context. Here is how I recommend annotating:

Use a notes layer. Create a layer in Figma (I call it "Dev Notes") with sticky-note-style annotations placed near the relevant sections. Each note describes the intended behavior:

  • "These three cards stack vertically on mobile, maintaining left-to-right reading order as top-to-bottom."
  • "This image is hidden on mobile. The text block expands to full width."
  • "Navigation collapses to hamburger on tablet (991px)."
  • "This section changes from horizontal scroll on desktop to vertical stack on mobile."

Color-code visibility. Some designers use a simple system: green overlay = visible on all breakpoints, yellow overlay = visible desktop only, red overlay = different layout on mobile. Whatever system you use, explain it in a legend so the developer does not have to guess what the colors mean.

Link desktop and mobile frames. Place the mobile frame next to or below its desktop counterpart on the same page. Do not put all desktop frames on one page and all mobile frames on another. The developer needs to see both views of the same section side by side.

Want a website that turns visitors into customers, not just compliments?

Book a 15-min intro

Sections that always need tablet frames

Most sections reflow from desktop to mobile predictably. But some layouts have an awkward middle state where neither the desktop nor mobile layout works at tablet width. These sections need an explicit tablet frame:

Multi-column grids. A four-column grid at desktop might go to two columns at tablet and one at mobile. Without the tablet frame, the developer has to decide whether to show two columns or jump straight to one.

Side-by-side text and image sections. At desktop, image left and text right. At mobile, they stack. But at tablet, does the image stay side-by-side at a smaller size, or does it stack early? The answer depends on the image and text proportions, and the designer should decide.

Pricing tables. Three or four pricing cards side by side work at desktop and stacked at mobile. At tablet, two cards per row with the third below often looks best, but that is a layout the developer will not invent without seeing it.

Navigation with many items. If the desktop nav has eight links, the mobile nav has a hamburger, but what about tablet? Do the links stay visible in a condensed bar? Do some hide? Does it collapse to hamburger earlier? This is a common source of revision.

Complex hero sections. A hero with a headline, subtext, two CTAs, a product screenshot, and trust badges might need significant rearrangement at tablet. The desktop version has space. The mobile version stacks everything. The tablet version might need a different image position or a reduced trust badges row.

Common handoff mistakes I see

Desktop only. I already covered this, but it bears repeating. Handing off a desktop-only file is the single most expensive handoff mistake. It is not laziness, it is often deadline pressure, but the cost shifts from the design phase to the build phase. The work still has to happen. It just happens slower and with less design control.

Designing at the wrong widths. A desktop design at 1920px leaves the developer guessing what happens at 1440px and 1280px, which are far more common viewport sizes. A mobile design at 414px misses the behavior at 375px, which is still the most common mobile width. Use 1440px for desktop and 375px or 390px for mobile. These match real devices and align with Webflow's breakpoint system.

Assuming the developer will figure it out. "It is obvious that these stack on mobile." Is it? Is the order obvious? Is the spacing obvious? Is the text size obvious? What feels obvious to the designer who spent 20 hours in the file is not obvious to the developer seeing it for the first time. Be explicit.

Not accounting for content length. The mobile frame shows a heading that fits perfectly in two lines. But the real heading on another page is 30% longer. What happens then? Does it go to three lines? Does the font size decrease? Does the container grow? Show the mobile layout with the longest realistic content, not the shortest.

Forgetting CMS-driven pages. The homepage gets desktop and mobile frames. The blog post template gets desktop only. But blog posts are often the highest-traffic pages on the site. If the blog template does not have a mobile frame, the developer builds mobile typography, image handling, and content width by feel. That is a lot of design decisions to delegate.

The efficient breakpoint workflow

Here is the workflow I recommend for designers who want to deliver complete responsive specs without designing four versions of every page:

  1. Design every page at desktop (1440px) with full detail. This is the primary design.

  2. Design every page at mobile (375px or 390px) with full detail. This does not mean redesigning from scratch. It means placing the same components in a mobile-width frame and adjusting layout, sizing, and visibility.

  3. Identify tricky sections. After finishing desktop and mobile, scan for sections where the tablet behavior is ambiguous. Create tablet frames only for those sections.

  4. Add annotations for behavior. For any section where the visual layout does not fully communicate the intended behavior (animations, visibility changes, interaction differences), add a text note.

  5. Organize the file for developer reading. Group frames by page, with desktop and mobile side by side. Put annotations near the relevant sections. Make the layers panel readable by naming everything.

  6. Walk through the file with the developer. Fifteen minutes on a call reviewing the responsive intent page by page prevents hours of misunderstanding later. Point out the tricky sections, explain the reflow logic, and answer questions before the build starts.

The cost of getting this right versus wrong

A Figma file with clear responsive specs adds some time to the design phase, since you are documenting reflow intent that you would otherwise leave implicit.

A Figma file without responsive specs adds significant time to the build phase, plus extra revision rounds, because the developer has to guess the responsive behavior and then redo whatever does not match your intent.

The trade is lopsided in your favor. The extra time spent documenting responsive intent in Figma is consistently smaller than the build time and revision rounds it saves in Webflow. The site also ships better, because the responsive behavior was designed intentionally rather than guessed by a developer under deadline pressure.

Design the breakpoints. Annotate the intent. Hand off a file that builds clean. Your developer, your budget, and your launch timeline will all be better for it.

Prefer to hire through Upwork?
Top Rated Plus, 100% Job Success, 450+ projects shipped. See the reviews and start a contract.
Hire me on Upwork

FAQ

Do I need to design every page at every breakpoint?

No. Design every page at desktop and mobile. Add tablet frames only for sections where the reflow is not obvious, like complex grids, multi-column layouts, or sections where you want different content on tablet versus mobile.

What breakpoints does Webflow use?

Webflow's default breakpoints are 1920px and above (large desktop), 1440px (desktop base), 991px (tablet), 767px (mobile landscape), and 478px (mobile portrait). You can add custom breakpoints, but these five cover most designs.

Should I design at Webflow's exact breakpoint widths?

It helps. Designing at 1440px for desktop and 375px or 390px for mobile matches the most common real-world viewports and aligns with Webflow's breakpoints. It saves the developer from translating between arbitrary frame sizes and Webflow's system.

How do I communicate that an element should hide on mobile?

Add a note or annotation directly on the Figma frame that says 'hidden on mobile' or 'visible desktop only.' Better yet, create a mobile frame that shows the section without that element, so the developer sees exactly what the mobile version looks like.

All posts
the next step is small

Want a site that does this for you?

15 minutes, no deck, no pressure. Worst case, you leave with a free plan.

keep reading

More notes