Should you leave Webflow? When I'd stay, and when I'd move to code

Fri, 13 Nov 2026 00:00:00 GMT

For most marketing sites, yes, I'd leave. The exception is a team whose marketers are confident changing layouts themselves in the Designer. If that's you, Webflow is the right tool, so stay.

I've used Webflow since 2017 and paid for it since 2018. I still do: I'm on the Agency workspace plan today. My first portfolio was built on it, and I've built on it for clients ever since. I'm not writing this as someone who never liked it. I think Webflow's Designer is the best visual builder there is. I've still moved my own site off it. Here's why, and when I'd tell you not to.

// fig. 1 Answer in order and stop at the first yes.

Weighing it up for your own site? Start a project and I'll give you a straight answer.

// 01

Why I moved my own site

The CMS was the first thing. Once I started building past what a marketing site needs, the CMS limits kept getting in the way, and I found open-source and paid tools that did far more. That's when I went off Webflow for my own work.

Then the cost. My site plan cost around $20 to $25 a month, and the price went up over the years. My site now runs on Astro behind Cloudflare. I pay about $10 a year, and that's the domain. There's no hosting bill.

And the editing. I don't open an editor to add a page any more. I describe the change to an AI agent, it makes it on a staging copy, and I check it there before it goes live. Backups and security are handled in the same setup.

// 02

When staying is the right call

Some marketing teams are very comfortable in the Webflow Designer. They don't just edit text. They adjust the build: sections, layouts, new pages. If that's how your team works, Webflow is a great tool for you, so go for it.

One client's marketing team is in the Designer every day. When they need a landing page for a Google Ads campaign, they make a new page, copy over components they like from other pages, and mix and match them. They don't need a developer for any of it, and Webflow handles it well.

Move a team like that to Next.js and they'll expect to keep doing it. On a code build that means touching the source, and that's where things break. If your marketers want to own the build, a code site is the wrong fit.

Webflow is leaning further into this with Source by Webflow, a platform for marketing teams and AI agents to work on the site together. It's in a limited research preview (read 8 November 2026), and I haven't used it.

The other case is when the problem is fixable where you are. Hunterbrook is a news site Scaler Marketing moved from WordPress to Webflow, and I led the build. Two weeks after launch it had used just over 1 TB of bandwidth in 16 days, on a plan that includes 50 GB a month. About 99% of the requests were automated, so I put Cloudflare in front, and bandwidth dropped by about 99.5%. The site is still on Webflow, on the plan it launched with. A big bill on its own isn't a reason to move. Find out what's causing it first. That's speed and bandwidth work, not a migration.

// 03

The real signs you've outgrown it

Over the years, the clients I've seen leave Webflow have left for the same few reasons.

CMS limits. This is the most common one. The site has outgrown what Webflow's CMS will hold or do.
Bandwidth costs. Webflow charges a lot for bandwidth once you go past your plan. Check whether it's bots first, as above.
No branching. Several people need to work on the site at once and publish only what's ready.
Paying for basics. Localisation and analytics are paid add-ons on Webflow. Localize starts at $9 a month and Analyze at $9 a month (Webflow's pricing page, billed yearly, read 8 November 2026). Cloudflare, for one, includes web analytics for free.

Logins aren't on that list. I've never had a client leave Webflow because it can't do user accounts. A marketing site doesn't need them, and people who need an app know Webflow isn't an app platform.

// 04

What's going on with Webflow

Webflow switched off User Accounts, its built-in logins and gated content, on 29 January 2026. Sites still using it lost their members' logins, and their user data wasn't moved to the CMS (Webflow help, read 6 November 2026). If you relied on it, you've already had to choose something else.

// 05

What you lose when you leave

The Designer. Nothing else I've used comes close to it. If you're building an HTML page, it gives you a lot of control and it all makes sense. That's the one thing I miss, and the only one.

For most teams, the bigger worry is editing. Marketing teams like being able to change a page without a developer, and for a long time that was the weak spot of leaving. Open-source editors like Payload and Sanity have closed most of that gap. When Scaler Marketing moved client sites to code, I built a Webflow-style visual editor on Payload so their clients could keep editing with ease. Several people can edit at once.

What it won't do is let clients move div blocks around. That's on purpose. Even on Webflow, clients break layouts without meaning to, all the time. On a Next.js or Astro site, I don't want anyone touching the code that holds the layout together unless a developer is involved. That's why teams whose marketers change layouts in the Designer should stay.

// 06

Where people go instead

Next.js. Scaler Marketing has moved three client sites from Webflow to Next.js so far. The clients didn't ask for it. Most clients don't mind what their site runs on. It was an in-house call, made for cost and speed of building. When a client sends a list of changes (a page, a section, a new feature), it can take hours in Webflow. On a fully coded site, with agentic coding, it's usually minutes. Those are rough numbers from our own work, not a benchmark.
Astro. This site. A good fit for a content-led marketing site you want fast and low-cost to host.
Other platforms. A few more sites I've worked on have moved off Webflow to other platforms.
WordPress. Some clients who left over cost went to WordPress. The platform is free, but the plugins aren't, and that's where the cost comes back.

// 07

Will leaving hurt your rankings?

It doesn't have to. Every old URL needs a 301 redirect to its new home, and the sitemap and Search Console need updating on the day you switch. When Hunterbrook moved from WordPress to Webflow, about 120 articles came across with 301s from their old URLs. It's the same job whichever direction you're moving.

// 08

What it costs

My own numbers: a Webflow site plan at around $20 to $25 a month, against about $10 a year for a domain now. Webflow's Premium site plan is $25 a month billed yearly today (pricing page, read 8 November 2026). A full breakdown of what I've paid for Webflow, Wized and Xano over the years is coming in a later post.

// 09

Where I'm not sure yet

A large marketing team, with lots of people making changes at once, is the case I'm most nervous about. On Webflow, letting several people make separate changes and publish only some of them needs branching, and most of the clients I work with aren't on a plan that includes it. On the code side, I haven't stress-tested a Payload editor with a team that size. If a team like that asked me to move them, I'd plan to build the editor features they need as part of the move, and I'd be honest that it's the part I'd watch most closely.

Part of my work on website migration.

If you're weighing this up and want a second opinion from someone who's built on both, I'm happy to look at your setup. Start a project and tell me what's pushing you to move.

Aonnoy Sengupta: notes from building