Once you’ve clicked Convert and you’re looking at the preview popup, you have a Copy to Webflow button in the top right. Figma is a sibling tool: Convert to Figma (/tools/html-to-figma) takes HTML and CSS only and has its own Copy to Figma button. Each puts a native version of your section onto your clipboard, Webflow elements or Figma layers. From there it’s just paste.
You can now edit the section the same way you’d edit anything you built by hand: change text, swap colors, adjust spacing, restyle classes, add interactions. Everything that converted natively is fully editable in the Designer.
Anything that came through as embedded custom code (JavaScript, CSS animations, certain advanced styling) will appear as an Embed element inside the section. It runs on the published page but won’t render in the Designer view. See How the Converter works for the full picture on why that happens and how to preview properly.
From there, treat it like any other Figma design. You can rename layers, restructure frames, swap colors via local styles, replace images, and build around it as part of a larger file.
Convert to Figma is processed by a partner service, code.to.design, so your HTML and CSS are sent to it to build the layers.
Convert to Figma takes no JavaScript, and animations and interactions don’t exist in Figma’s design model. What you get is the clean static visual of the section, which is usually what you want when you’re using the Figma path.
This is the single most important habit to build when using the Converter, especially for Webflow.
The Webflow Designer is sensitive to certain structural patterns, and while the Converter handles most of them gracefully, it cannot guarantee compatibility with every possible piece of AI-generated code. In rare cases, pasting a converted section into a complex existing project can cause the Designer to crash or behave unexpectedly.
The fix is simple and takes about ten seconds: paste into a fresh, empty Webflow project first.
This isn’t paranoia — it’s the standard practice we recommend to everyone. The cost is a few seconds. The benefit is never having a converted section corrupt the project you’ve spent weeks building. Treat it like saving before a risky operation.
For Figma, the same principle applies but the stakes are much lower — Figma handles unexpected paste content well, and there’s no equivalent crash risk. You can paste directly into your real Figma file if you want, though pasting into a scratch file first is still a reasonable habit.
Every conversion you run is saved to your Recent Conversions on the Converter page (your latest 60 conversions are listed). If you want to bring an older section into a new project, you can open any past conversion and re-copy it to Webflow.
This is especially useful when you’ve already done the work of generating, converting, and verifying a section, and you want to use it again somewhere else without re-running the whole flow.
If the section pastes into Webflow and something looks wrong, the most common causes are:
If a conversion produces unexpected results consistently, it’s worth re-generating with a cleaner prompt (or a clearer code structure) and converting again. Feeding the Converter cleaner code is always the fastest path to a cleaner result.
