Capture an authorized Webflow site into portable static files -- editable, versioned, and ready to host anywhere you choose.
What Webflow's own code export leaves behind
Webflow's help centre is explicit about this: code export is a paid Workspace feature, and several kinds of content never travel with it. This is the gap a capture of the published site closes — it reads what visitors see, which is the rendered result of all of it.| In the site | In a Webflow code export | In a capture of the published site |
|---|
| Static pages, CSS, JS, assets | Yes | Yes |
|---|
| CMS collection content | No | Yes, as rendered |
|---|
| Ecommerce and User Accounts | No | Public pages only, as rendered |
|---|
| Localized pages and content | Primary locale only | Yes, as published per locale |
|---|
| Plan required | Paid Workspace plan | None on Webflow's side |
|---|
Source: Webflow — How do I export my Webflow site code?
Read this before you pick a route
- You want the source of truth back
- Use Webflow's export — It is the designer's own markup, and it is the cleaner code
- You want the site as visitors see it
- Capture the published pages — CMS output included, because it is rendered
- You want to keep editing without Webflow
- Either — then edit the files — A capture opens in the visual editor; an export you edit by hand
- The site is not yours
- Neither — Authorization is confirmed before protected output
Source: Webflow — How do I export my Webflow site code?