Webflow vs a Static Site on Cloudflare: What We Learned Moving amariq.com

Key takeaways

• The saving is real but small. Webflow's own pricing page lists a Basic site at $15 a month and a Premium (CMS) site at $25 a month, both billed yearly, which is $180 to $300 a year per site. Our hosting on Cloudflare's free plan costs nothing, so the running cost is the domain. If you have one site, you are saving $15 to $25 a month, not rebuilding your budget.
• The real trade is who can edit. On Webflow, anyone you invite can change a headline in the Designer or the Editor. On our static site, one person edits, through code and a few scripts. If more than one non-technical person needs to publish, stay on Webflow.
• The hard parts of a move are not the hosting. They are redirects, email records, forms, Search Console and the pre-launch checks. We turned each one into a repeatable check, so the next move is quicker.
• We still build client sites on Webflow. This post is about one site with one editor. It is not advice to move a client who edits weekly, runs a large CMS or sells online.
• A static site is not a zero-JavaScript site. Ours still loads a GSAP animation bundle, because we wanted rich motion, and Webflow's own interactions are built on GSAP too.

Why we moved

Amariq's site is edited by one person, Rahat. It has no logins, no shop and no members area. It has pages, a blog, a few forms and some motion. That is close to the simplest kind of website there is, and it was sitting on a plan designed for teams.

Three things pushed the decision. The monthly fee on a site where one person edits. A wish to keep every page as plain files in a folder, so the whole site could be read, searched and rolled back with git. And a plan to use an AI coding assistant to do the repetitive parts: shared headers, meta tags, the blog and the checks.

None of that is a criticism of Webflow. We built the site on it first, Rahat is a certified Webflow developer, and we still deliver client work on it. The point is that the right platform depends on who edits and how often, and for this one site the answer had changed. The same question for your site is in the decision section below, and our Webflow development service is still the right answer for many sites.

What the move actually involved

The result is a folder of 44 HTML pages, where the folder structure is the URL structure. A handful of small Python scripts keep the shared header and footer in step across every page, turn blog posts written in Markdown into finished pages, generate the page titles, descriptions, schema and sitemap, and refuse to deploy if a link is broken. The folder is published to Cloudflare Pages with one command.

In practice the move had five jobs.

1. Keep every URL. Every page that was public on Webflow kept its address. The few that changed got a permanent 301 redirect. Today the redirect file has 14 live rules, and most are for pages we have since merged, retired or set aside. Blog traffic is the asset, and a dropped URL is a lost ranking.
2. Move the DNS without touching email. The domain stayed registered with Namecheap, and the DNS moved to Cloudflare. Email is a separate service, and its records had to be copied over exactly and left unproxied.
3. Replace Webflow Forms. Our forms now post to a small Google Apps Script web app that writes a row in a Google Sheet and sends an email. We tested it from the live domain before launch.
4. Replace Webflow Interactions. Motion now comes from GSAP, loaded as a single file. Webflow's own interactions are built on the same library, so the result looks similar, but we maintain the code ourselves.
5. Carry over search and analytics. The Search Console property and the Google Analytics property stayed the same, so the history did not reset.

The cost, with numbers

These are the figures a buyer can check. Webflow's prices are from its pricing page on 7 October 2026, and Cloudflare's limits are from its Pages documentation.

Two honest footnotes. First, we did the build with an AI coding assistant, which is a subscription we already pay for. If you are comparing costs, count your own tools and your own time, not only hosting. Second, if you need many sites, the saving grows with each one, since each Webflow site is its own plan. For a single site, it is a few hundred dollars a year at most.

A cost you will not see in a table is the cost of being your own support. When a build fails on Webflow, you open a support chat. When a script fails on a static site, you read the error. They are usually short and readable, but they are yours.

What we gained

• The whole site is plain files. Search the entire site for a phrase in a second. Change a shared footer in one place. Read exactly what is live, with nothing hidden inside a designer.
• A history of every change. Every edit is a commit in git, in plain English. When a change makes a page worse, undoing it is one command.
• Checks before every deploy. Scripts verify that links work, images exist, each page has one H1, titles and descriptions are the right length, and no preview tag has been left in. They are code, so we can add a new check whenever a new mistake teaches us one.
• No platform limits for our use. We do not think about static page counts, CMS item limits or bandwidth steps. The free plan's limits are far above a 44-page marketing site.
• Freedom to build the odd thing. Layouts that would take a custom code embed in Webflow are just HTML and CSS here.

What a static site gives up

• The visual canvas. You cannot click on a page and drag. You describe a change, it is written, and you refresh. For a designer, that is a real loss, and it is the main reason we would not recommend this to a team that works visually.
• Other people's ability to edit. There is no editor login. A colleague who wants to fix a typo needs a Markdown file, git, or you.
• Built-in forms with a dashboard. The Google Sheet works well, but spam handling, notifications and file uploads are now our problem.
• A CMS with fields and roles. Our blog is Markdown files and a script. It is fine for one author and impossible to hand to a marketing team.
• Webflow's built-in backups and staging domain. We have git and a draft link instead, which keep a stronger history and are slower to learn.
• Ecommerce. Webflow sells products. A static site would need a separate service such as a payment link or a hosted checkout.

The traps in a move, and the checks we built

This is the section that matters if you plan the same move. Each trap below became a check in our process.

• Check the page body for a leftover no-index tag, not only the headers. A preview version of a site often carries a robots meta tag to keep search engines out, and it can travel into the live pages. We caught ours the day we launched, removed it, and added a check that fails the deploy if the tag appears in any page body. Headers alone do not show it.
• Verify Search Console by DNS, not by an HTML tag. A tag lives inside the old site and stops working at the switch. We re-verified with a DNS record, which does not depend on any page, and kept the same property so the history stayed.
• Ask the registry where DNS lives. A local resolver can answer as if the DNS has already moved. We query the domain registry directly.
• List the mail records before you move DNS. Several mail records were created automatically by the email host and do not appear in a normal dashboard view. We read them off the old nameservers with a DNS tool, copied them across, and left every mail record as DNS only, never proxied.
• Give a changed image a new filename. Our images are served with a long cache lifetime for speed, so a replaced picture under the same filename would keep showing the old one.
• Hold back anything unfinished. Pages that are not ready go to a "later" folder with a redirect, so nothing half-built goes live.

If you want a general checklist for leaving any platform, our Webflow migration service page covers the same ground from the client side.

Who should move, and who should not

Use this as a quick test. Count how many of the left column describe you.

A client who hands the site to a marketing team belongs in the right-hand column. That is why we still build client sites on Webflow, WordPress, Shopify and Framer, and why we call our own move a good fit for one editor, not a policy. If you are choosing between platforms for a new site, see how each one fits in our post on how to build a high-converting website, which holds for any platform, and in our guide to why a website is not converting.

The honest case for staying on Webflow

A static site only wins if you edit rarely and value the files. In every other case, Webflow earns its fee. It gives you hosting with no deploy step, a visual designer, a built-in CMS with an editor interface for non-developers, staging, forms with a dashboard, and a vendor to ask. For a business that depends on its site every week, paying $25 a month to avoid owning the plumbing is a sensible choice, and for most of our clients it is the one we recommend.

If you are weighing WordPress or Framer instead, those are different trades again. WordPress suits sites that need a large plugin ecosystem, and our WordPress development service covers when. Framer suits fast marketing sites built by designers, and our Framer development service covers that. The right question is never "which platform is best". It is "who edits, how often, and what happens when it breaks".

Our checklist for the next move

• Check the page body for a leftover no-index tag before launch. It is one command.
• Write the redirect list before building anything. Make a list of every old URL first, then decide what each one becomes.
• Prove the form from the live domain before the DNS switch. A static host answers a raw form post with an error, so the endpoint has to be somewhere real.
• Keep the old platform for a few days as a rollback. Do not cancel on launch day.
• Write down what only one person knows. If you are the only editor, your notes are the support team.

Frequently asked questions

Is a static site faster than Webflow?

Not automatically. Webflow serves its sites through a CDN, and a static site on Cloudflare does too. What differs is what the page loads. A static site can load very little, but ours still includes an animation bundle, so we do not claim it is faster. Measure your own pages with Lighthouse before and after, rather than trusting either side.

How much does it cost to move from Webflow to a static site?

The hosting cost drops to zero on Cloudflare's free plan, against $15 or $25 a month on Webflow billed yearly. The move itself costs time: rebuilding the pages as HTML, setting up redirects, forms and DNS. For a client, a small marketing site is usually a project, not a small fix, so quote it as a build.

Will I lose my Google rankings if I leave Webflow?

Not if every URL keeps working. Keep the same addresses where you can, and use a permanent 301 redirect for any that must change. Keep the same canonical host that Google already indexes, resubmit your sitemap, and keep your Search Console property so the history stays.

Can I keep my email when I move the DNS to Cloudflare?

Yes, but copy every mail record exactly, including the ones your email host created automatically, and leave them as DNS only so they are not proxied. Compare the old and new records before you change the nameservers.

What replaces Webflow Forms on a static site?

Something that receives a form post and does something with it. We use a Google Apps Script web app that adds a row to a Google Sheet and sends an email. Other options are a form service or a Cloudflare Worker. Whichever you pick, test it from the live domain.

Can a non-technical team edit a static site?

Not without more tooling. A git-based CMS can put a login over the same Markdown files, but it is another system to set up and maintain. If the team edits often, Webflow's editor is simpler.

Do I need Astro or Next.js for this?

No. Our site is plain HTML, CSS and JavaScript with a few scripts to keep it tidy. A framework like Astro makes sense once someone other than you must edit content, or when pages number in the hundreds.

Is Cloudflare Pages free for a business site?

Cloudflare's documentation lists a free plan with 500 builds a month, up to 20,000 files per site and a 25 MiB limit per file, and we use it for a commercial site. Check the current limits page before you commit, since plans change.

Should I cancel Webflow straight away?

No. Keep the old site and plan for a few days after launch as a rollback, confirm that every page, form and redirect works on the live domain, and only then cancel.

Do you still recommend Webflow to clients?

Yes, when the client or their team edits regularly. We build on Webflow, WordPress, Shopify and Framer, and we pick the platform by who edits and what the site has to do. See our list of the 12 best Webflow agencies in 2026 for how to choose a studio if you need one.

Is this the same as moving off WordPress?

The steps are the same: URLs, redirects, DNS, email, forms and search. The content export differs, and WordPress sites often have plugins doing hidden work, such as forms, redirects or SEO tags, that you must replace one by one.

Can I move back to Webflow later?

Yes. Plain HTML pages can be rebuilt in Webflow, though not imported automatically, and the URLs can stay the same. That is one more reason to keep the redirect list and the URL inventory up to date.