Skip to content

Figma to Webflow: what a good design handover includes

What a Figma file needs before someone builds it in Webflow: styles, components, responsive states, real content and ready assets, plus the traps that slow builds down.

Development
October 20, 2026 · 6 min read

A Figma file can look finished and still be hard to build. A design shows how a page looks at one width with one set of content. A Webflow build has to decide how that page behaves at every width, with content that changes, when someone hovers over a button, and when a form fails. Every decision the design leaves out falls to whoever builds it, and their guess may not match what the designer meant.

Whether you are handing your own design to a developer, or checking a file a designer sent you before you pay for a build, the handover is where those gaps show up. Below is what a good handover includes, followed by the traps that tend to slow a build down or produce a site that only looks right on the designer's screen.

Styles: colours, type and spacing as named values

Webflow works best when a site is built from a small set of reusable values: colour variables, text styles and a consistent spacing scale. The Figma file should already contain these.

  • Colours saved as Figma styles or variables with clear names, such as "Text / primary" or "Background / muted", instead of twenty slightly different greys picked by eye.
  • Text styles for every level in use: headings, body text, small print, button labels and captions. Each one with font, weight, size and line height, plus the mobile sizes if they change.
  • A spacing scale, for example 4, 8, 16, 24, 32, 48, 64 and 96 pixels, used for every gap and padding.

When a design uses a gap of 22 pixels in one place and 26 in another for no visible reason, the builder can either copy the odd values, which makes the site harder to maintain, or round them, which means the build no longer matches the file. Settle the system in Figma, and Webflow's variables and classes can mirror it one to one.

Components that map to how Webflow is built

Anything that repeats should be a Figma component, with variants for its states. Buttons are the obvious case: primary, secondary and text buttons, each with default, hover, focus and disabled variants. The header, footer, cards, form fields and pricing blocks belong in the same library, and can become Webflow components in the build.

Use auto layout. It behaves much like flexbox, which Webflow uses for most layouts, so it tells the builder how elements stack, wrap and space themselves. Elements placed by hand at fixed coordinates tell them very little.

Name layers and components sensibly. "Frame 482" and "Group 17 copy" give no hint of what something is or whether it repeats. Avoid detaching components, too: a detached button nudged by two pixels becomes a second button style, and the builder has to ask whether that was intentional.

Responsive states, designed rather than implied

Webflow's standard breakpoints are desktop, tablet (991 pixels wide and below) and two phone sizes (767 and 478 pixels and below), with optional larger ones for wide screens. A handover should show at least desktop and mobile for every section, plus tablet wherever the layout changes in a way that is not obvious.

These are the parts that most often go unanswered:

  • The header menu on small screens: what the menu button looks like, and what the open menu looks like.
  • Grids: does a row of three cards become one column, two columns or a horizontal scroll?
  • Large headings: what size are they on a phone, and where do the lines break?
  • Images with text on top: how does the image crop, and which part of it must stay visible?
  • Tables and comparison blocks, which rarely fit a phone screen as they are.
  • Very wide screens: does the content stop at a maximum width, and what fills the sides?

If the mobile design is left "to be figured out in the build", it will be, by the builder rather than by you, and you may spend a revision round getting back to what you pictured.

Interactive states and motion

A static frame shows one moment. A good handover also shows the moments in between:

  • Hover and focus states for links, buttons and cards. Focus states matter for anyone using a keyboard.
  • Open and closed states for menus, accordions, tabs and pop-ups.
  • Form states: empty, filled, error messages, sending, and the success message.
  • Any animation, described in plain words: what moves, when it starts and roughly how long it takes. "Cards fade up slightly as they scroll into view, about 0.4 seconds each, one after another" is enough to build from. A short Figma prototype helps where words fall short.

Keep motion modest unless it is central to the idea. Webflow Interactions can do a lot, but every animation is something to build, test on real phones and maintain.

Content and CMS structure

If the site has a blog, a portfolio, a team page or anything else made of repeating items, it will probably use the Webflow CMS. The design should mark which sections are driven by the CMS and list the fields each item needs, for example title, slug, cover image, summary, date, category and body text.

Design those items with realistic content, including the awkward cases: the longest title you expect, an item with no image, a category name in a language with long words. A card that only works with a four-word title will break on the first real post.

The same applies to fixed pages: final copy, or something close to it, should be in the file. Otherwise the layout gets adjusted to the real words during the build, which is design work done in the wrong place.

Assets and fonts, ready to export

The builder should not have to dig for files or recreate them. A good handover includes:

  • Icons as SVG, with strokes outlined where needed and drawn on a consistent frame size.
  • Photos and illustrations at twice their display size, so they stay sharp on high-density screens, or the original files for the builder to export.
  • Clear file names, not "image 23 final final".
  • A favicon and a social sharing image, which is the picture that appears when someone shares a link to the page.
  • Fonts that are licensed for use on websites. Google Fonts can be used freely. A font bought for desktop use is often not licensed for the web, so check the terms before the build starts.

The usual traps

Most slow handovers come from the same short list of problems:

  • Only a desktop design, at a single width, usually 1440 pixels.
  • Several versions of the same page in the file, with no indication of which one is final.
  • Text converted to outlines or flattened into images, which cannot be selected, translated or edited in Webflow.
  • Effects that look simple in Figma but need custom code on the web, such as text that follows a curved path or complex blend modes over video. They are possible, but they should be flagged so they can be planned and priced.
  • No design for the form success message, the 404 page or the legal pages.
  • Hidden layers and leftover experiments inside frames that are meant to be final.

Before handing over, mark one Figma page as ready for build and move everything else out of it. Then go through the sections above one at a time. If each question can be answered from the file alone, without a message explaining it, the handover is in good shape.

If you would rather have someone else build it, Hyper Framez sells Webflow landing page builds at a fixed price, and this list is a good thing to run through before you send the file.

Hyper Framez
Design and development studio
Contact Us

Have Any Project Idea?

Pick a deliverable, pay once and send your brief. Not sure which one fits? Write to us and we will tell you honestly.