Hosting Webflow-exported sites externally can boost agency margins by letting you charge for hosting while using more affordable infrastructure. Here's how to effectively manage external hosting, especially for non-CMS projects, along with platform and CMS recommendations.
1. Exporting Sites from Webflow
- Only static websites can be exported. Webflow’s CMS and e-commerce functionality do not work outside of its platform.
- Go to the Webflow Designer, click the Export Code icon (top-right), and download the ZIP file containing HTML, CSS, JS, and assets.
- The code is well-organized and production-ready for static hosting environments.
For externally hosting a static site, the following platforms are commonly used:
- Netlify – Free tier available, continuous deployment, custom domains, HTTPS, blazing fast CDN, simple drag-and-drop deploy or Git integration.
- Vercel – Optimized for frontend frameworks but works great for static HTML exports. Low-latency, strong CDN, Git-based workflow.
- Cloudflare Pages – Free tier, excellent performance, handles caching and security automatically.
- Amazon S3 + CloudFront – More complex setup, but offers full control and scalability. Use for enterprise-level performance or tailored environments.
You can charge clients for hosting while using these low-cost or free hosting services to increase your margins.
3. Disadvantages of Hosting Outside Webflow
- Loss of CMS/E-commerce functionality – Only static pages will work. Editing content requires a developer or page rebuild.
- Manual updates – Any content or tech changes need manual re-export and deployment.
- No Webflow form handling – You'll need to set up third-party services like Formspree, Basin, or Netlify Forms.
- No staging/previews – Webflow provides visual staging links. Outside platforms may require custom setups for previews/stages.
4. Additional Considerations
- Domain management – You’ll need to manage domain settings (DNS, SSL, etc.) yourself or on behalf of the client.
- Maintenance and support – Factor ongoing support into your pricing. Clients often expect changes, but there’s no Webflow Editor interface in this setup.
- Version control – Git-based workflows (with Netlify or Vercel) offer rollback and version control capabilities, which can be valuable.
- Legal & compliance – Ensure GDPR/CCPA compliance for forms or analytics if you're using external tools.
5. CMS Recommendations for Hosting with a CMS
If you require CMS functionality but want to host outside Webflow, consider these easier-to-learn CMS options:
- Statamic – Flat-file CMS. No database required. Developer-friendly but easy for designers with minimal backend skills.
- Plasmic – Visual builder with CMS capabilities and integrates with your dev stack. Easier transition for Webflow users.
- Sanity – Headless CMS. You can build the front end however you like (e.g., using Next.js), then fetch content. Steeper learning curve but scalable.
- Grav – Another flat-file CMS. Easier to learn than WordPress, better performance, and doesn't require a database.
Avoid WordPress unless you're already familiar with backend development, as it can be bloated and high-maintenance in comparison to Webflow.
Summary
To increase agency profits, export static Webflow sites and host them on modern static hosting platforms like Netlify or Vercel. You’ll lose CMS editing capabilities but gain control and higher margins. For CMS capabilities outside of Webflow, use Statamic or Plasmic for a smoother learning curve. Always balance cost savings with the ongoing support responsibilities you'll take on.