Native, not embedded
Sections, divs, headings, images, and classes — editable in Designer like anything you built there.
Flowtools rebuilds a page of HTML, CSS, and JavaScript as editable Webflow content — sections, styles, and classes you can keep building on inside Designer.
Built for one page at a time · Public beta
Webflow's clipboard needs its own native format. Without a translation step, every generated section gets rebuilt by hand — class by class — undoing most of what AI saved you.
Sections, divs, headings, images, and classes — editable in Designer like anything you built there.
Runs in the browser. No plugin, no extension, no Designer setup — result lands on your clipboard.
GSAP, ScrollTrigger, and custom scripts come across as embeds and run on publish — nothing dropped.
Flowtools is built around a single page — a landing page, a hero, a pricing block, one exported Webflow page. Cleaner input, cleaner output.
Standalone HTML from Claude, ChatGPT, Cursor, Gemini, v0, or Lovable — lands as real Webflow structure, not an embed.
Bring one exported page back in. Head styles and scripts route to the right editors — reuse across pages may need class cleanup.
Move a hand-written page or single component into Designer without recreating its classes and layout by hand.
Paste or upload your files, preview across breakpoints if you want, then convert. The result is copied to your clipboard as native Webflow content.
Drop HTML, CSS, and JS into the editors — or upload files. A full Webflow export works too.
Check the layout at Desktop, Tablet, and Mobile before you convert.
Flowtools rebuilds the structure as native Webflow elements and copies the result to your clipboard.
⌘ V into any section. Styles, classes, and layout come across editable — keep building in Webflow.
You generate the code. Webflow ships the site. Flowtools is the translation layer that hands the code to Webflow as editable elements — nothing more, nothing less.
FlowtoolsThe output isn't wrapped in an Embed block. It's the same clipboard payload Designer produces itself — parsed, styled, and ready to edit.
Classes map to Webflow classes. Hover, focus, transitions, and keyframes come across as native styles.
Collection-style layouts land as wrapper + item divs — swap in a real Collection List and connect fields.
Render the page at Desktop, Tablet, and Mobile inside Flowtools — spot layout issues before pasting into Designer.
There's a built-in prompt tuned for the converter — get cleaner HTML from ChatGPT, Claude, Cursor, Gemini, v0, or Lovable, then land it as native Webflow elements in one paste.
Prompt for a page. Get HTML and CSS back.
Convert HTML and CSS into Webflow-ready structure.
Continue building with real structure and classes.
The converter is in public beta. Direction after that is shaped by what beta users actually need — send feedback and it lands on the roadmap.
Free while we sharpen the converter. Bug reports and feature requests move the roadmap directly.
Advanced controls for serious Webflow builds. Shape is still forming — early access opens the door.
More utilities for the AI-era Webflow workflow. What ships next depends on what beta shows us.
How much of your page stays editable in Webflow depends on the code you paste in. The built-in prompt steers AI toward output the converter can turn into real elements.
Section, header, article, nav, footer — the tags Webflow understands as native elements.
Named classes over tag or ID selectors — so the Style panel picks them up cleanly after paste.
Wrap output in a single root element. Full sections convert more reliably than isolated fragments.
Flowtools is tuned for a single HTML document with its CSS and JavaScript in place. Feed it that, and most of the page comes across as native Webflow content.
Vanilla HTML, CSS, and JavaScript in one page — the format we test against. Everything the docs recommend applies here.
GSAP and ScrollTrigger come across as embeds. They don't run inside Designer, but execute on preview and on your published site.
Collection-shaped divs come through ready to swap for a real Collection List — layout intact, easy to wire up.
“In the AI era, building faster is the need. Flowtools moves Webflow builders in that direction.”Flowtools · product direction
No. Flowtools gives you a faster starting point. You continue building and refining the site in Webflow.
A single HTML page with its CSS and JavaScript — a landing page, a hero, one exported Webflow page. Flowtools is built around one page at a time; whole-site exports aren't in scope yet.
Scripts, including GSAP and ScrollTrigger, are preserved as Webflow embeds. They don't run inside Designer, but execute normally on Preview (with Render custom code) and on your published site.
Yes — that's the primary workflow. Use the built-in prompt with Claude, ChatGPT, Cursor, Gemini, v0, or Lovable to get output tuned for reliable conversion.
Flowtools is under active development. Most pages convert cleanly; some edge cases still won't. If something looks off, send it through the Report a bug form and it goes straight into the fix queue.
Free during public beta. A Pro tier will come later — early-access sign-ups help shape what goes into it.
Conversion runs where you paste and the result is copied straight to your clipboard for Designer. Your code is never uploaded, stored, or seen.
Free during public beta. No plugin, no Designer setup. Or sign up for early access to Pro.
More Flowtools tools are on the way.