Bring your Webflow design
and published pages into code.
Capture your published Webflow markup and available styles, scripts and assets as a runnable project. Review forms, CMS content and interactions as you prepare to replace Webflow hosting.
Packing your site…
·
Your Webflow front end
Published page and collection output
HTML served to visitors, including content already rendered into a captured CMS page. This is page output, not a collection database.
Available styles and assets
Linked theme CSS, scripts, images and fonts, with nested CSS assets copied when reachable.
A runnable migration sample
HTML, Astro or Vite source, local page links, a route map and reports of forms, scripts and missing resources.
Replacements to build
CMS collections and relationships
Export collection records separately and map the fields into your new CMS. A published-page capture does not reconstruct collection schemas.
Forms, search and commerce
Plan replacement handlers and services. Captured markup does not provide a new submission endpoint, search index or checkout backend.
Interactions and dynamic modules
Copied scripts may still need Webflow services or additional chunks. Test navigation, menus, animations and browser-loaded content locally.
Your Webflow move,
one step at a time.
- Choose pages that show the real site.
Capture a landing page and a few representative published CMS pages so you can inspect both the design and visible content.
- Review the project beside your native export.
Run the source files and inspect styles, scripts and captured routes. Use the report to identify remaining platform dependencies.
- Move collections and hosted behavior.
Export collection CSVs separately, map them into your new CMS and replace form/search services before switching hosting.
Questions,
answered.
Can't find what you need? You'll get an answer from an engineer within a day.
Talk to usHow is this different from Webflow’s native code export?
Webflow offers a native HTML/CSS/JavaScript export on paid Workspace plans. This tool captures a small sample of published public pages into a runnable project and adds a route map and dependency report. Use the native export when it fits your migration.
Will published CMS content appear in the capture?
Content present in the server HTML of captured pages is retained as markup. This does not export the full collection database, field definitions or relationships.
What should I do with collection CSV exports?
Export collection records from Webflow separately. The CMS CSV-to-JSON tool can turn them into records for your rebuild; you still need to map fields, relationships and remote assets to your destination.
Will I get the original PHP code, CMS database or a React rewrite?
You get the public front-end HTML, downloaded assets and a runnable project structure. PHP source, database content, user accounts and CMS workflows cannot be recovered from a public URL. Astro and Vite outputs retain editable HTML; they are not generated component rewrites.
Can the exported project work without the original hosting?
Downloaded assets and copied pages can be served locally. CSS imports, fonts and background images are followed and localized when available. Missing assets remain remote, while forms, embedded services and runtime scripts may still depend on the old host. The report identifies detected dependencies so you can rebuild them.
How much can I export free?
Choose one, three or five linked public pages. Each project is capped at 100 asset attempts, 5 MB per asset, 2 MB per page and 25 MB total fetched data. Query-based pages are kept distinct. Pages and assets beyond the caps are listed in the report. No account or card required; request limits apply.