Skip to main content
FXFramExporter
Export a site
Migration path

Framer to Webflow

A visual builder with a class-based CSS model, its own CMS, and hosting that competes directly with Framer's.

VerdictRebuild required
Read this before you quote the work
Webflow has no HTML import. You cannot upload an export and get an editable Webflow project — the platform builds its own DOM from its own style engine. The export is useful as a specification: exact spacing, colour values, font stacks, and breakpoint behaviour to rebuild against.

The order that works

  1. 1Export the Framer site and open the CSS to pull the real design tokens — colours, type scale, spacing steps.
  2. 2Recreate those tokens in Webflow as global classes and variables before building any page.
  3. 3Rebuild the layout section by section, checking each breakpoint against the exported HTML in a second tab.
  4. 4Move repeating content into a Webflow CMS collection rather than duplicating static sections.
  5. 5Recreate interactions in Webflow's Interactions panel — these do not transfer in any form.

What you keep

  • Design decisions, as measurable values rather than guesses
  • Copy, ready to paste
  • Image assets at the sizes actually used

What you rebuild

  • Everything structural — the rebuild is manual
  • All interactions and animations
The mistake to avoid
Treating this as a migration rather than a rebuild, and quoting a client accordingly. The export saves the design and content phase, not the build phase.

Questions

›Can I import a Framer site directly into Webflow?

Webflow has no HTML import. You cannot upload an export and get an editable Webflow project — the platform builds its own DOM from its own style engine. The export is useful as a specification: exact spacing, colour values, font stacks, and breakpoint behaviour to rebuild against.

›What transfers from Framer to Webflow?

Design decisions, as measurable values rather than guesses. Copy, ready to paste. Image assets at the sizes actually used.

›What has to be rebuilt?

Everything structural — the rebuild is manual. All interactions and animations.

›What is the most common mistake on this migration?

Treating this as a migration rather than a rebuild, and quoting a client accordingly. The export saves the design and content phase, not the build phase.