Webflow websites can be exported and hosted elsewhere, but with limitations. While Webflow allows exporting clean front-end code (HTML, CSS, JS, assets), some features dependent on Webflow’s CMS and hosting won’t function outside their ecosystem.
1. Exporting Webflow Code
- Go to Designer, then click the Export Code (</>) icon in the toolbar.
- Webflow generates HTML, CSS, JavaScript, and image files.
- This code can be uploaded to other platforms like cPanel or Plesk as a static site.
2. Hosting on cPanel or Plesk
- Use an FTP client to upload exported files to the appropriate directory on your cPanel/Plesk server (usually
/public_html). - Your exported site will function as a static website.
- Ensure correct file structure and paths when uploading.
3. Limitations of Exporting
- Webflow CMS content won't be included. The exported site does not retain dynamic elements like CMS Collections, filtering, or collection lists.
- No Webflow forms support. You'll need to connect forms to a third-party service (e.g., Formspree, Zapier, or a custom PHP backend).
- No Webflow-hosted Interactions or Ecommerce. Any interactions built in Webflow will function only if purely JavaScript-driven (not CMS-dependent). Ecommerce functionality cannot be exported at all.
4. Alternative Solutions
- Use Webflow’s native hosting if you rely on CMS, forms, Ecommerce, or editor features.
- Use APIs to pull CMS content into a custom-hosted frontend (e.g., via Webflow’s CMS API), but this requires developer setup.
- Rebuild CMS features in your own backend or using tools like WordPress, headless CMS options, or custom databases.
Summary
You can export Webflow sites as static code and host them on cPanel/Plesk, but CMS, Ecommerce, and backend-integrated features won’t work. For dynamic functionality, either stay on Webflow hosting or recreate those features externally.