Note: We’re transitioning to Workspaces, and are in the process of updating our content. Visit the Workspaces blog post to read more about these updates and changes, or visit our updated lesson on code export. You can also learn how to check if your account is on Workspaces.
Minifying your HTML can help improve page load times by removing white space, comments, and other code elements browser's don't need to load the page. To export minified HTML:
The downloaded ZIP file contains all your site's pages, styles, scripts, and images:
Due to a known limitation with Safari's URL support, you'll need to add the ".zip" filename extension to extract the exported folder's contents.
To avoid conflicts with other code frameworks, Webflow adds "w-" to the front of any component-specific classes.
At the moment, you cannot choose what gets exported. Every exportable part of your project will be included in each and every export.
You can edit the code after it's exported. However, manual changes to exported files may break some Webflow components.
If you want to remove the .html extensions from your exported pages, you can do so with a .htaccess file [↗].
After exporting, you don't need to provide attribution to Webflow or maintain a Webflow plan for your exported site to work on your own server.
CMS and Ecommerce content (databases) aren't exported. Collection lists will show the empty state. Collection pages will also not show any content that's bound to Collection fields as well.
No. Any password protected pages in your site won't be "protected" after code export. Your site must be hosted with Webflow in order for password protection to work as expected. Read more about project and page passwords.
Site search and forms (including file upload and reCAPTCHA) do not work on exported sites. If you intend to export your site, you'll need to either send form data away from Webflow or embed 3rd party widgets. Ecommerce elements won't function either.