Move a Webflow Site to Cloudflare: Free Hosting Guide

Yes, you can move a Webflow site to free hosting on Cloudflare, and the new site has to be running before you cancel. Webflow's code export gives you the files, and it needs a paid Workspace plan, which is separate from your Site plan. It leaves behind your CMS content (the blog posts, team and project entries you manage in Webflow's content editor), user accounts and ecommerce, and on the exported site your forms and site search stop working. Below: what you pay now, what the export gives you, what you lose, and the route to a site with no monthly hosting fee.

What a Webflow Site plan costs

Webflow's pricing page says "All prices in USD, per site, plus applicable taxes added at checkout." The page shows no Canadian-dollar price, so the figures below are US dollars and your card statement may differ. These are the figures as of November 2026.

The monthly figures come from Webflow's May 2026 pricing announcement, which says the new Site plan pricing started May 13, 2026 for new purchases and June 29, 2026 for most existing sites (for an existing site the new price applies at its next renewal on or after that date). Sites in a Freelancer or Agency Workspace, or on 2022-or-earlier discounts, move on November 16, 2026. At yearly billing that is $180 a year for Basic and $300 a year for Premium, every year, for a site that may not change much.

Webflow says its purchases are nonrefundable, so check your renewal date before you start. The Workspace plan that code export needs is a separate charge from your Site plan. Webflow's pricing page lists Core, the cheapest Workspace plan with code export, at US$19 a month billed yearly as of November 2026.

Will I lose the site? What the export gives you

What you keep depends on whether your site uses the CMS. A site without one exports as pages you can host. On a site built on the CMS, Webflow says the collection pages export as empty templates, and the words live in a separate CSV file. Webflow's code export help page says you can export your site's HTML, CSS, JavaScript and assets and host it "anywhere you like" with no attribution required. HTML is the page text and structure, CSS is the styling, and JavaScript is the small programs that make parts of a page move.

Two conditions apply. Code export is available on paid Workspace plans, and Webflow says Site plans do not include it. A Workspace plan is separate from the plan on each site. At the moment, you cannot choose what gets exported.

Webflow says you do not need a Webflow plan for the exported files to work on your own server. Webflow also warns that manual edits to exported files may break some Webflow components.

What you lose on the way out

Webflow's help page lists what the code export leaves out.

Your form submissions so far can be exported separately, according to Webflow.

What the CMS CSV gives you

Webflow can export each CMS collection as a CSV, which is a spreadsheet file, and it describes that as useful for moving content to another platform. Read its CMS help page before you rely on it.

• Rich text fields come out as HTML, so a blog post is text with tags in it.
• Images and files come out as links to Webflow-hosted files, not as image files. Webflow says those links break if you delete the original site, and tells you to keep the original site as a backup or download your images and files manually.
• Reference fields export as plain text, and the file only holds the language you are viewing.

The CSV holds your content, and a blog layout still has to be rebuilt around it. For the detail of everything the export includes, see what you get when you export a Webflow site.

The route to free hosting

Cloudflare's limits page lists up to 20,000 files per site and 25 MiB per file on the free plan, and its Functions pricing page says requests to static assets are free and unlimited. A static site is one made of finished files rather than a database, which is what an exported Webflow site is.

The steps run in this order:

1. In Webflow, point each form at a form service: choose Custom Action in the form's settings and paste the service's address. Webflow's forms page puts this before the export.
2. Export the code from Webflow, and export your CMS collections and form submissions as files.
3. Rebuild what the export drops, such as the CMS pages.
4. Put the files in a GitHub repository (a folder of your site's files kept on GitHub) and connect it to a Cloudflare project. Cloudflare builds and deploys every time you push a change (send updated files to GitHub). Pages gives every branch other than your live one (a side copy of your files) its own preview address, and Workers does once you switch preview builds on. Check every page on a preview address.
5. Point your domain at the new site. The domain section below explains what that means and what to check for email.
6. Only then cancel the Webflow Site plan.

Cloudflare has two products for this, Pages and Workers. Its Pages overview says to start new projects with Workers. Both list the same 20,000-file and 25 MiB limits on the free plan, and both connect to GitHub. Nameservers are the setting, kept at your registrar (the company where you bought the name), that says who answers for your domain. For a bare domain such as example.com, Cloudflare's Pages custom domains page says the nameservers have to point to Cloudflare, so plan on changing them whichever product you pick.

The form service and the rebuild are the hard parts for a non-developer. For the sibling moves, see how to move a Squarespace site to Cloudflare and how to move a WordPress site to free hosting. The general case is in a website with no monthly fees.

Editing in Webflow, and after the move

In Webflow you edit in the Designer, and publishing is a separate step. Webflow's publishing help page says you can publish to a free webflow.io address first and to your custom domain from the same publish menu. It warns you to choose the destination carefully. Webflow also keeps automatic backups, unlimited on paid Site plans, that you can preview and restore.

After the move, the live site is whatever files are in the connected GitHub repository, and it updates when you push a change to your production branch. Webflow warns that manual edits to exported files may break some Webflow components.

What happens to your domain

Your domain stays yours. The catch is timing: Webflow says cancelling a paid Site plan removes your custom domains, so you point the domain at the new site first and cancel after. Your domain registration (the registrar, where you bought the name) does not have to move. What changes is where the domain points. That is kept in its DNS records, the entries that send your web address to a site and your email to a mailbox. For a bare domain such as example.com, Cloudflare says the domain has to be added to Cloudflare with its nameservers pointed there, and you change them at your registrar. Cloudflare says a subdomain such as www does not need that and can use a CNAME record (one DNS entry) at your old DNS provider.

Email deserves a check before anything switches. Cloudflare says its scan of your existing records is not guaranteed to find all of them, so you need to review them yourself. Open the DNS settings where the domain is managed today, find the email records (the ones that send your mail to Gmail, Microsoft 365 or another mailbox provider), and check that each one shows up in what Cloudflare copied.

Google rankings and old addresses

Every old address needs to land on its new page, and that is a redirect. Nobody can promise where you will rank after a move. What you can do is keep the old addresses working and check them against a list.

Doing it yourself or having it done

SiteFree is the business that wrote this guide, and it sells this move. It is a Canadian (Montreal) migration service with prices in CAD. SiteFree handles Webflow in beta, and Wix, Squarespace and WordPress as well. Because it is in beta, ask us about your site before you pay.

We rebuild your site to match your design closely, on free hosting in your own Cloudflare account, with the files in your own GitHub account. Both are yours. The site is served from Cloudflare's global network, not from a Canadian host. You pay once, with no monthly fee:

• Small: up to 5 pages plus one blog or other section, $99 CAD for the first 20 sites, then $360.
• Large: up to 100 pages, any number of sections, $199 CAD for the first 20 sites, then $720.
• Bigger: a shop, a member area or over 100 pages gets a fixed quote.

Your private preview is ready within two business days of payment. You get up to two rounds of fixes, and a full refund any time before you approve; your Webflow site stays live until then. Every old address is redirected to its new page. A feature your old platform ran itself is $49 CAD each. If you want to see the page count and price first, you can check your site with no email.

What editing looks like on a SiteFree site

On a SiteFree site, every change goes through a copy.

This is how a professional developer sets up a site: changes are tried on a copy first and every version is kept. You get that without running any of it yourself.

It costs something. The assistant is a plan you subscribe to separately, such as Claude Pro at US$20 a month, or the AI plan you already have. You can stop the plan between edits. You need a free GitHub account, because that is where your site's files live. After you say yes, the live site updates a few minutes later. Any web developer can also edit the files, or you can email the changes to SiteFree.

For an owner who updates the site once or twice a year, that is a good fit. For an owner who lives in the Designer every week, it is a real change of habit.

SiteFree keeps contact forms sending to the owner's inbox and checks email settings before switching the domain.