Yes, you can use an external hosting service instead of Webflow's hosting, but this requires exporting your site code and it comes with limitations—mainly, losing Webflow CMS and form handling features.
1. Requirements to Export
- You must be on a paid Webflow Workspace plan (such as the “Starter” or “Freelancer” plan) to use the Export Code feature.
- You will not need to pay for Webflow’s Site plan if you're not using Webflow Hosting.
2. Limitations of Exporting
- CMS features will not work—only static pages can be exported.
- Webflow Forms won’t submit—you'll need a third-party form handler like Formspree or Netlify Forms.
- No direct support for ecommerce, membership features, or advanced interactions tied to CMS data.
- Changes must be re-exported manually every time you update your site.
3. How to Export Your Site
- Finish building your site in Webflow.
- Click “Export Code” in the Webflow Designer (top right corner).
- Webflow will package your website as a ZIP file with HTML, CSS, JS, and assets.
4. Choose an External Host
- Popular hosting options include:
- Netlify (free tier available)
- Vercel
- GitHub Pages
- Firebase Hosting
- Traditional web hosts like Bluehost, HostGator, or SiteGround
5. Upload Files to Your Host
- Unzip the exported Webflow files.
- Use your host’s file manager, Git deployment, or drag-and-drop upload feature to publish the files.
- Ensure that paths for stylesheets, JavaScript, and assets are preserved.
- Webflow’s built-in forms require their hosting, so to make forms work:
- Replace form action with services like: Formspree, FormSubmit, or Netlify Functions.
- Follow the third-party service’s guide to get form endpoints and update the form's HTML.
7. Point Your Domain
- Update your domain’s DNS settings based on your new host’s IP addresses or CNAME requirements.
- You do not need to connect the domain in Webflow unless you host with Webflow.
Summary
Yes, you can host your Webflow site elsewhere by exporting static code, avoiding Webflow's monthly Site plan fee. However, you'll lose CMS, form processing, and need to handle manual uploads for updates. For a static 6-page portfolio, this approach is cost-effective and completely viable.