Webflow vs custom code: when to move off Webflow, and when to stay

Should you move from Webflow to custom code?

Usually not, and the reason is who runs the website. Webflow is a visual website builder: marketers design, build and publish pages without a developer. A custom-coded site moves that work into a code repository. Developers make the changes there, or marketers do it with coding agents and a developer checking the result. That trade pays off for some sites and costs others a lot of speed. These signals show which side you're on.

Two or more signals in the "Move" rows deserve a closer look. A single one usually has a middle path, covered further down.

Why are teams moving off Webflow in 2026?

Most Webflow sites aren't going anywhere, but the movement that exists runs mostly one way. In its July 2026 crawl, TechnologyChecker counted 988 domains that had dropped Webflow for Next.js in about five weeks, and 95 that went the other way. That's a small share of the 249,194 domains it found on Webflow, but it's roughly ten to one. Software, IT services and technology or internet companies made up 32.8% of the movers. Four reasons stand out.

• AI tools made code cheaper to change. In Stack Overflow's 2025 survey, 84% of respondents used or planned to use AI tools in development, and 51% of professional developers used them every day. The AI startup Vellum moved its site off Webflow in about a week with coding agents. A showcase page that used to take its team a week now takes half a day.
• The website became part of the product. Integration directories, template galleries, docs and calculators all run on product data. Engineers would rather build them in the codebase they already maintain.
• Webflow changed its plans. New Site plans applied to new purchases from May 13, 2026, and to most existing sites at renewal from June 29. Basic costs more, CMS and Business merged into one Premium plan, and former Business sites pay less but get 50 GB of bandwidth instead of 100 GB. Sites in Freelancer and Agency Workspaces, and sites on legacy discounts from 2022 or earlier, switch from November 16, 2026.
• Ownership. Code in your own repository runs on any host you choose. A Webflow site leaves as a static export plus CSV files, as the export section below shows.

None of this makes Webflow the wrong choice for most marketing sites. It keeps adding ways to work with code and AI: its MCP server lets tools such as Claude Code, ChatGPT and Cursor create pages and work with CMS content inside a Webflow project.

What does custom code give you that Webflow doesn't?

By custom code we mean a site built in a framework such as Next.js or Astro, with content in a headless CMS such as Sanity, Storyblok or Payload, deployed from your own Git repository. Here's what that setup gives you that Webflow can't, or can only in part.

• Pages from any data. Templates can read your product database, docs, changelog or pricing rules directly, for example to generate one page per integration. Nothing has to be copied into a CMS first.
• No platform ceilings. Webflow's Premium plan holds 20,000 CMS items, and every CMS item page sits under its Collection's path, such as /blog/post-name. In code, URL patterns and page counts are design decisions.
• Your engineering workflow. Pull requests, code review, a preview build for every change, automated tests and rollbacks to any earlier version.
• Performance control. You decide which scripts, CSS files and fonts each page loads. Astro sends zero JavaScript by default and adds it only to the components that need it.
• Room for product features. Logins, gated content, search across your docs, personalization and anything else that needs server code.
• Portability. The code and the content are yours. You can change host or agency without starting over, and swap the CMS without redesigning the site.

Each of these is also something your team now builds, hosts and keeps up to date.

What do you give up when you leave Webflow?

Mostly the work Webflow does in the background. Vellum's write-up lists the work that became its team's job: robots.txt, the sitemap, 301 redirects, metadata and Open Graph tags, canonical URLs, structured data, image optimization, analytics events, forms and a staging setup. Even with that checklist, it had a few canonical issues on launch day and caught broken social images on a few pages during the migration. The table shows what Webflow runs today and what replaces it.

Security is the one teams underestimate. On your own Next.js site, patching is your job. In March 2025, Next.js fixed a middleware flaw that let attackers skip authorization checks, rated 9.1 out of 10. In December 2025, a flaw in React Server Components, rated 10.0, allowed remote code execution. Affected App Router sites had to upgrade and redeploy, and Next.js recommended rotating every application secret afterwards. Someone has to watch for advisories like these and act within days.

Editing is the other trade. Headless CMSs have narrowed the gap. Sanity's Presentation tool shows a live preview of your site inside the CMS, with click-to-edit. Storyblok's Visual Editor jumps from a content block to its place on the page, and Payload's Live Preview updates the page as you type. What none of them gives marketers is the Designer's design freedom: the power to create a new layout on their own. Editors assemble pages from sections a developer built first.

Can you just export your Webflow code?

You can export it, but the export won't run your site. Webflow's code export gives you the HTML pages, a CSS folder with three stylesheets, the JavaScript files and an images folder. Only paid Workspace plans can export; Site plans can't. You don't need to keep a Webflow plan, or credit Webflow, to host the files somewhere else.

CMS content comes out separately. Each Collection exports as a CSV file from the Designer, with image and file fields as URLs, so download those files before you delete the Webflow project. For many Collections, the Webflow Data API reads the items in code, at 60 to 120 requests a minute depending on the plan. If you want a React app out of Webflow, DevLink Export pulls Webflow components into a React codebase, though components bound to CMS content don't export fully and page-level interactions stay behind. All of it is raw material for a rebuild. None of it is a migration on its own.

Is there a middle path between Webflow and custom code?

Yes, three of them.

• Webflow Cloud. It deploys full-stack Next.js and Astro apps on Webflow's hosting, which runs on Cloudflare Workers. An app can sit next to your Webflow site or run without one on its own domain, and it gets SQLite, key-value and object storage. Good for a calculator, a customer tool or a gated area, while the marketing pages stay in the Designer.
• Code components. Developers build React components in their own codebase and share them to Webflow, where designers place and configure them like any other component. React only, and changes to the component itself go through code.
• Webflow as a headless CMS. Your team keeps editing content in Webflow, and a coded front end renders it through the Webflow Data API. Webflow says cached requests to its content delivery API have effectively no rate limits, while uncached ones count against your plan's limit.

A middle path works while code is a small part of the site. Once most new work happens in code, two systems cost more than one, and a full move is cleaner.

Next.js, Astro or something else: which stack do teams move to?

Next.js is the usual pick. TechnologyChecker found 570,205 active domains on it, more than twice its Webflow count, and coding agents know it well, which matters if you plan to change the site with them. Vellum chose it partly for that reason: in its words, "the AI tools know it cold." Astro is the other common choice for marketing sites. The CMS matters as much as the framework, because it decides how your marketers work.

Our own site runs on Astro, with Sanity as the CMS. We chose Astro because almost everything on our site is content, and Astro sends JavaScript only to the parts of a page that need it. We picked Sanity because it stores content as structured data rather than page layouts, so one piece of content can feed several pages. Running both ourselves also lets us test the setup we recommend, from server-rendered HTML to structured data, before we suggest it to a client.

What does moving off Webflow cost?

There's no standard price for a headless CMS migration. The cost follows how many pages have to be designed and built, which isn't the same as how many CMS items you have, and how complex they are. Complexity comes down to these six things.

• Templates. A website with 300 blog posts and eight templates is cheaper to move than a 60-page site with 30 one-off layouts. Each template becomes a set of coded components and a CMS schema.
• The editor experience. Basic editing is quick to set up. Live preview, reusable page sections and field validation take longer, and they decide whether marketers keep publishing after launch.
• Content. Clean CSV exports move by script. Rich text with embeds, references between Collections and images that need a new home take manual work.
• Integrations. Forms to the CRM, analytics, consent, search and any product data feeds.
• Languages. Each locale adds routing, hreflang tags, translated content and its own QA pass.
• Design. Rebuilding the current design costs less than a redesign, but it isn't free. Vellum found coding agents get the structure right and miss the spacing and small interactions, and it advises budgeting more time for that than you think.

Then add the running costs: hosting, CMS seats, form and search services, monitoring, and developer time for updates and security patches. Set that against your Webflow plans and add-ons. Vellum says it saves about 30,000 dollars a year on its Webflow bill. A site on a single Basic plan won't save anything close to that, and may pay more after the move.

How do you move off Webflow without losing rankings?

Once you're ready to move, treat it as a site move and follow Google's guidance. Keep every URL you can: if none change, Google's hosting-change guidance applies and there's no redirect map to build. Expect some movement either way. Google says a small to medium site can take a few weeks for most pages to move.

• 1. Benchmark. Export Search Console and analytics data for every URL: clicks, impressions, top queries and conversions.
• 2. Export everything. Crawl the site for a complete list of URLs, titles, meta descriptions, canonicals, Open Graph images, alt text and custom code snippets. Export Webflow's 301 redirects and every Collection as CSV.
• 3. Map URLs. Keep each URL where you can. Where one has to change, map it to its new address.
• 4. Rebuild the SEO basics. Metadata fields, canonicals, sitemaps, robots.txt, structured data and hreflang, set in templates so every new page gets them. Render content on the server, so search engines and AI answers can use it: Webflow's own AEO guidance notes that AI crawlers other than Google's Gemini don't yet run JavaScript.
• 5. Move the files. Download images and documents and host them with the new site or in the new CMS.
• 6. Test on staging. Crawl the staging site and compare it with the old crawl. Check redirects, responsive layouts, forms and tracking, and keep staging out of the index.
• 7. Launch. Lower your DNS TTL to a few hours at least a week ahead, as Google suggests. Switch DNS, remove any noindex tags or robots blocks, submit the new sitemap and check key pages with URL Inspection in Search Console.
• 8. Monitor. Check crawl errors, indexing and rankings daily for the first weeks. If your URLs stayed the same, Googlebot often crawls less for a while after launch, which Google calls normal; if they changed, expect it to crawl more. Keep redirects for as long as possible, generally at least a year.

The same checks apply in the other direction. Our Webflow migration page covers moves onto Webflow, including from WordPress.

When is staying on Webflow the better call?

More often than the migration stories suggest. Stick with Webflow if one of these fits.

• Nobody will own the code. A coded site without an engineer or an agency on call ages fast. Dependencies fall behind and security fixes wait.
• Your marketers design pages as well as fill them. If they create new layouts every month, a headless CMS will slow them down.
• The website is marketing pages and a blog. That's what Webflow is built for, and you're far from its limits.
• The goal is a smaller bill. Run the numbers in the cost section first. Moving to save a few dollars a month rarely survives the first invoice for developer time.
• You need to launch soon. A rebuild adds weeks or months of work before it saves any.

If you need more control, security reviews or governance inside Webflow, our Webflow Enterprise guide covers what to check.

How was this guide written and checked?

This guide draws on BenorMedia's Webflow projects and on building our own site in Astro and Sanity. We checked every outside fact against its source on October 12, 2026: Webflow's help center and developer docs, Google Search Central, the Next.js, Astro, Sanity, Storyblok and Payload docs, and the public migration data and write-ups listed below. We recheck it every 30 days. One disclosure: BenorMedia earns money on both sides of this decision. We're a Webflow Professional Partner, and we also build custom-coded sites on a headless CMS.