Export a Webflow CMS Site to Static HTML
Turn published Webflow collection pages into a portable static site for stable portfolios, archives and content sites.
Paste your Webflow CMS URL and choose pages.
//blog/*/projects/*/categories/*
Paste the public Webflow CMS link
Copy the address of your published site, not its editor. The page must open without a login.
Choose the pages to export
The scan follows links up to three levels deep. Select the pages you need from the results, within your plan’s limit.
Download your Webflow CMS site as HTML files.
yoursite.webflow.io/blogPage content and design
Your published Webflow pages and styles, including collection pages found during the scan. The ZIP is not an editable Webflow project. Review page titles and search settings before publishing.
Images and fonts
Choose downloaded assets to include available images and fonts. Free exports keep them linked to the original site. Videos and embeds may still need an internet connection.
Menus and animations
Supported menus, sliders, tabs and animations are included. Test each interaction after export.
Test your exported site then publish it.
webflow-cms-static-export.zipTest the exported site
Unzip the download and open the files through a local web server or temporary hosting. Check layouts, links, forms and animations on desktop and mobile.
Publish on your chosen host
Upload the tested files to Vercel, Netlify, Cloudflare Pages or GitHub Pages. Check the live site before changing your domain. Hosting costs and provider terms apply.
Before you move your domain. Collection pages are fixed copies, without the Webflow CMS editor or database. Publish and export again after updates. Set up forms, search, accounts and ecommerce separately.
Webflow Native vs Export Code Tool
Webflow provides native code export on eligible paid Workspace plans. NoCodeExport instead starts from a public URL and can capture rendered CMS pages as static snapshots.
| What you need | Webflow native workflow | Recommended path NoCodeExport |
|---|---|---|
Access to deployable code | Available on eligible paid Workspace plans. | Creates a rendered static package from a published URL. |
CMS content | CMS databases and dynamic content are excluded from native code export. | Reachable published CMS pages can be captured as static snapshots. |
Migration planning | Still requires QA and replacement planning for hosted features excluded from the export. | Produces one static review build; forms, search, accounts, and ecommerce still need replacements. |
Best fit | Teams using Webflow’s native code export from a paid Workspace. | Teams that need a rendered snapshot from a public URL, including reachable CMS pages. |
Webflow code-export documentation, checked 7 September 2026: help.webflow.com
Webflow guides to pair with the tool page
These articles cover exporter options, code handoff details, and the practical steps teams use when moving a Webflow site off-platform.
Try the tool
Validate this on a live site
When you're ready to test this path on a real project, open the dedicated tool page and run it against your live URL.
Webflow Export
Export Webflow projects to code
Use the main exporter page to analyze a real site, review the export setup, and continue with the right workflow.
Open Webflow ExportCommon Questions
Review what the workflow covers, what needs separate implementation, and what to verify before making a change.