Webflow to React: Why and How I Switched
After 9 years on Webflow, I've moved all my sites off the platform and stopped recommending it. My hosting costs dropped to $0 and my productivity is up. Most importantly, my clients have at least a site they can fully manage on their own.
I created my Webflow account in May 2017. For 9 years it was the core of my freelance work, including mission critical launches with large enterprise clients.
As of this year, I've stopped recommending it and moved all of my own sites off the platform.
My main reason to stop using it: it's become the slowest tool I open up on a weekly basis.
Instead, I'm using React for all my projects. For hosting I'm using Netlify and for managing my sites I'm using Cursor.
The 4 sites below were once Webflow projects and are now all React:
Will I ever go back to building sites on Webflow? It comes down to productivity. There are things I already miss about it but for me at least and my client it's a step in the right direction.
My 3 reasons to switch from Webflow to React
1. Webflow's productivity penalty
My sites are all on React now, and I manage them with Cursor.
A site change that previously took me 10 minutes on Webflow now gets done in a single prompt. And if that weren't enough, on Webflow my changes were manual, meaning one change at a time. On Cursor, I can have 10 agents working on 10 complex tasks simultaneously.
The productivity delta is immense.
Webflow does have an MCP, but it's slow and its tool coverage is limited. It often times out, and I need to keep the MCP Bridge app open for most changes. The experience, at least today, is awful.
2. The free alternative is better
As of May 2026, a CMS site on Webflow costs $276/year, and a Basic site costs $168/year. For my 4 sites, that added up to $780/year.
My new fixed costs after the conversion: $0/year.
For hosting, I'm using Netlify, which has a generous free plan, but you could also use Vercel or Cloudflare.
This blog you're currently reading was previously on Webflow CMS, and it now runs on Sanity.io. Sanity's free plan has more than I need, and since it's fully agentic, I can manage my entire CMS from Cursor directly.
3. No learning curve for my clients
As a Webflow freelancer, once I was done with a project my clients could easily make text and CMS changes to the site, but they always needed me for anything more complex. For me, that meant monthly retainers. For my clients, it meant a fixed cost on top of what they were already paying Webflow.
Today, my clients can continue to edit the page themselves using their agent of choice. My recommendation is Cursor, but they can prompt the changes on Claude, Codex, or whatever else they prefer.
While I used to be the "Webflow guy" doing all the changes for my client, now their entire team can prompt changes to the site directly.
The creativity that unlocks is something else.
My new stack for marketing sites
Webflow's elegance lies in having everything on one platform. The tradeoff of leaving is that a handful of tools have to work together to replace it.
My new stack:
- Cursor: Managing my site and making changes.
- Netlify: Hosting and CDN.
- TanStack Start: React framework powered by TanStack Router and Vite.
- GitHub: Version control and triggering new site changes.
- Sanity: Headless CMS that replaces Webflow's CMS.
The only tool I pay for is Cursor, and it's a variable cost.
The reason I went with TanStack Start instead of Next.js is the ability to easily switch to another hosting provider at any time. Next.js is amazing, but switching it out of Vercel isn't trivial.
I'm enjoying Netlify, but I can easily move my React site to Cloudflare or Vercel whenever I want.
Webflow-to-React: a free skill
To make the conversion, I created a free React skill. Using it is very simple:
- Export your site from Webflow. Go to Webflow and export your site. You'll get a
.zipfile. - Install the skill on Cursor, Claude, etc. Run
npx skills@latest add dmenchaca/webflow-to-react -y. To install it for all projects on this machine, add-g. Reload your editor or agent after install. - Upload the exported
.zipto your agent and prompt:Convert this Webflow export to TanStack Start (React, SSR) with pixel parity. Use the webflow-to-react skill and follow SKILL.md from step one.
Closing thoughts
Webflow gave me a career, and I'll always be grateful for that. For 9 years it was the right tool, and for many people and projects it still is. This post isn't a takedown, it's a snapshot of where I've landed in May 2026.
What changed isn't really Webflow, it's the rest of the toolbox around it. AI agents have made it possible for a non-technical designer to ship and maintain production sites at a speed that no visual builder can match right now. The lock-in disappeared, the costs collapsed, and my clients gained autonomy instead of depending on me for every change.
If you're a freelancer or a small team still on Webflow and curious about what life looks like on the other side, give the webflow-to-react skill a try. Export one site, run the prompt, and see how close to pixel parity you land. Worst case, you go back to Webflow with a clearer view of what you actually value about it. Best case, you join me on the other side.
Either way, the creativity you'll unlock is worth the experiment.