Webflow Hosting vs. Code Export: A Decision Guide for Marketing Sites

Your marketing site is built in Webflow, and now someone — finance, security, or an engineer who already runs a static hosting stack — asks why you're paying Webflow to host it. The answer depends on one question: does the site use anything that runs on Webflow's servers? If yes, exporting the code won't save you money; it will silently break features. This guide lays out the decision, the trade-offs, and a cheap way to validate which side your site falls on before committing.

The constraint that decides everything

Webflow's code export produces static HTML, CSS, and JavaScript. Anything that requires Webflow's backend does not come along. That includes CMS collection pages, native form submissions, e-commerce, site search, and the client-facing Editor. If your site is a handful of static pages with a link to an external booking tool, export is viable. If marketing publishes blog posts through collections or your lead-gen forms post to Webflow, export turns your site into a snapshot that needs manual re-export and redeploy for every content change — and broken forms on day one.

Comparing the supported options

One constraint sits outside the table: code export requires a paid Workspace plan. Free accounts and site-plan-only accounts cannot export at all. Plan terms have changed over Webflow's history, so verify export availability in your current plan before budgeting a migration around it.

Trade-offs that don't show up in feature lists

You lose the reason you chose Webflow. Most teams pick Webflow so non-developers can ship pages. An exported site inverts that: every typo fix becomes a developer task involving an export, a deploy, and a cache invalidation. If publishing velocity matters, self-hosting the export is the worst of both worlds.

Forms are replaceable but not free. Services like Basin or Formspree can receive submissions on an exported site by pointing the form's action attribute at their endpoint. That works, but adds a vendor dependency, per-submission pricing, and a spam-filtering decision you didn't have before.

Asset references can leak. Webflow-generated markup and heavy custom code embeds sometimes reference assets hosted on Webflow's CDN. After export and migration, those references can break — or worse, keep working until the Webflow project is deleted, then break. An asset audit is not optional.

The hybrid often wins. A common pattern: keep the marketing site on Webflow hosting and point a subdomain such as app.example.com at your own infrastructure. Marketing keeps the CMS and Editor; engineering keeps full control of the product. This avoids the export trade-off entirely and is worth pricing before assuming migration is necessary.

Validating the decision with a test export

Before committing either way, spend an hour proving which features your site actually depends on. You need a Workspace plan with export enabled, a static host (a Netlify free tier or an S3 bucket works), and a non-production Webflow project.

1. In a test Webflow project, create one CMS collection with a template page and one page containing a native form.
2. From the Designer's project settings, use the code export option to download the ZIP. This requires the appropriate paid Workspace plan; check project settings first if the option is missing.
3. Deploy the extracted files to your static host. On Netlify, drag the folder into the deploy UI; no build command is needed.
4. Open the deployed URL and check three things: does the collection template page exist in the export, does the form submit anywhere, and do all images and scripts load?
5. Open your browser's network inspector and reload each page. Filter for requests to webflow.com or Webflow's asset CDN — any hits are dependencies that will break when the Webflow project is removed.

Expected result: the form submission fails or goes nowhere, and collection-driven pages are either absent or frozen as static HTML. That failure is the point — it tells you exactly what you'd need to replace. If your real site has no forms and no collections, and the network audit comes back clean, self-hosting is a legitimate cost decision. If anything fails, the hosting fee is buying you those features, and the honest comparison is Webflow hosting versus rebuilding them elsewhere.

Limitations to keep in mind

Export behavior and plan requirements have changed over time; confirm current terms on Webflow's pricing page before making a budget case. This guide covers marketing sites — e-commerce and membership features have their own, stricter dependencies on Webflow's backend. And if you do migrate, keep the Webflow project active (even on a free staging state) until the exported site's asset audit has been clean in production for a few weeks.