Add to Chrome — first conversion freeWhy this conversion is different
Webflow's code export is available on paid plans but strips CMS content and leaves you reassembling files by hand. Agencies typically hit this when a client wants to leave Webflow's per-site pricing but keep the design.
Webflow interactions run in the browser through its own engine. What matters for a theme is the resting, rendered state — the position, opacity and transform the elements settle at — and that is exactly what a rendered capture stores.
CMS collection pages are templates with sample content. Capture one collection item page to become your WordPress single-post template, then move the collection items into WordPress as posts.
How it works, step by step
1. Open the published Webflow site
Use the live domain or the .webflow.io staging URL. The published site renders exactly as visitors see it, unlike the Designer canvas.
2. Run through the page, then capture
Scroll to the bottom so scroll-based interactions complete and lazy images load, then click Generate theme.
3. Install and rebuild the CMS side
Upload the .zip in WordPress, activate it, then re-create Webflow collections as WordPress posts or custom post types using the captured collection template.
What gets converted — and what doesn't
Converted
- Page layout, grids and Webflow's generated class styling
- Every breakpoint Webflow generated, including the tablet and mobile variants
- Fonts loaded by the published site and all image assets
- The rendered end-state of Webflow interactions and animations
- Symbols such as navbars and footers, captured on each page
Not converted
- Webflow CMS collections as data — they move to WordPress as posts
- Webflow forms, which need a WordPress form plugin
- Ecommerce carts and checkout
- Interactions as live behaviour rather than rendered state
A real example
Before
A Webflow marketing site with a sticky nav, scroll-triggered fades, a CMS blog and a contact form.
After
A WordPress theme with the same layout and typography, a blog template ready for WordPress posts, and the contact section rewired to a form plugin.
Home, about, blog listing and a single blog post are captured; posts are then imported into WordPress and the form is reconnected.
Benefits
- No Webflow paid plan needed for a code export
- Design fidelity, including the parts the exporter mangles
- Removes Webflow's recurring per-site hosting cost
- Clients keep an editing interface they already know
Limits to know before you start
- CMS content and forms are separate work after installation
- Complex multi-step interactions ship as their captured state
- Ecommerce is out of scope
Frequently asked questions
Can I move a Webflow site to WordPress without the code export?
Yes. Themify captures the published site as it renders, so the export feature is not required at all.
What happens to Webflow CMS content?
It becomes WordPress content. Capture one collection page as the template, then create or import the items as WordPress posts.
Do Webflow interactions still animate?
CSS-based animation and transition styling carries over; interactions driven by Webflow's JS engine ship in their rendered state and can be re-added with WordPress-side scripts.
Will the mobile layout match?
Yes — Webflow's breakpoint styles are part of the stylesheet, which is captured along with the page.