Webflow to Next.js Migration Service,
Enter your Webflow site's address. We read its sitemap, group the pages into the templates a rebuild has to design, size each one, and estimate the price and timeline. Our own team does the work.
Updated Oct 28, 2026Switches tracked by TechnologyChecker.io since May 28, 2026Delivered by our own teamDTReviewed by David Thomson, CTO
Estimate your migration
Enter your Webflow site. We count its pages and templates from your sitemap and price the rebuild in about a minute.
Built by people, sped up by AI. Our engineers rebuild and check every page; AI coding agents take the repetitive work. It is not an automatic converter.
- 24/7 supportReach the team any time during the project and for 30 days after launch.
- SEO-safe, keep your trafficSame URLs, a 301 for every one that changes, metadata moved page by page. If search traffic drops after launch, we fix the cause free.
- Tested in detailEvery page checked against the old site on desktop and mobile: links, forms, redirects, tracking and speed.
- Pay 50% now, 50% at the endHalf to start, the other half when the finished site is live and you've signed it off.
Webflow
262,281 live domains
541
domains won back from Next.js in 90 days
Next.js
731,970 live domains
3,050
domains gained from Webflow in 90 days
Live domains and switches come from TechnologyChecker.io's own crawl of 29.9M live business domains, read Oct 28, 2026. Counts are domains, not accounts.
Stay on Webflow if…
- Marketing owns the site and needs to publish the same day without a developer.
- It's a small marketing site the visual builder handles without workarounds.
- Nobody on your team will look after a React codebase once it launches.
Move to Next.js if…
- Engineering owns the site, or is about to.
- You need custom logic, app features or integrations a visual builder can't reach.
- Performance work or plan costs have started to hold the site back.
- You want the code in your own repository, on hosting you choose.
- You want to change the site by asking an AI agent, and review every change before it goes live.
How we built this page
Every number names its source and the date it was read.
Webflow to Next.js: key findings
TechnologyChecker.io crawl, read Oct 28, 2026- The flow runs 7.5 to 1 toward Next.js. Since May 28, 2026, TechnologyChecker.io's crawl has seen 5,002 domains drop Webflow for Next.js and 666 go the other way; in the last 30 days the gap narrowed to 2.2 to 1 (646 vs 289).
- Next.js is the top destination for sites leaving Webflow. It takes 2.3× as many Webflow leavers as Astro, the next most common destination.
- 31.8% of the companies that moved are technology firms, against 14.9% of all Webflow companies (software, IT services and internet; 3,877 movers matched to a company).
- 61.9% of movers have 1–10 employees, close to Webflow's own base (60.7%). This is not only an enterprise move.
- Next.js runs on 2.8× as many live domains as Webflow (731,970 vs 262,281), and companies with 501+ employees make up 3.5% of its users against 1.5% for Webflow.
- 10,150 domains run both today, most of them partway through a move or with the marketing site on one and the app on the other.
Webflow is excellent for launching a marketing site without engineers. Teams leave once the site outgrows that stage.
Change anything by asking an AI agent
On Next.js the whole site is code in your repository, so a coding agent such as Claude Code, Codex or Cursor can change any part of it from a plain-English request: copy, layouts, components, redirects, structured data, integrations. It runs the build to check its own work and opens a pull request with a preview link, and nothing goes live until someone approves it. Webflow has an MCP server too, but there the agent works through the tools Webflow exposes, and isolated page branches need an Enterprise plan.
Performance and Core Web Vitals
Next.js renders on the server, generates static pages and optimises images out of the box, so the team tunes LCP, INP and CLS directly instead of working around a builder's runtime.
G2: 82 Webflow reviews mention “missing capabilities and slow performance on larger projects”.
SEO control at scale
Webflow handles a standard marketing site well. The limits show at the edges: rendering strategy, programmatic pages at scale, custom redirect logic and structured data beyond the built-in fields.
G2: 94 Webflow reviews mention “limited features: cms depth and ecommerce”.
Cost at scale
Webflow bills a predictable subscription that grows with seats, locales and CMS plans. Next.js swaps it for build time plus hosting, which often starts free for small sites. Whether that saves money depends on the team.
G2: 68 Webflow reviews mention “expensive relative to hand-coding”.
Developer ownership and control
On Webflow you work inside its hosting, interactions engine and export format. On Next.js the codebase is yours: you pick the CMS, the components, the host and the test setup, and wire the site into the rest of your stack.
Our crawl: technology firms are 31.8% of the companies that moved, against 14.9% of all Webflow companies.
They solve different problems. Webflow lets designers ship marketing sites without code; Next.js lets developers build anything, with full control and full responsibility. Most migrations happen when ownership of the site moves from the first group to the second.
| Dimension | Webflow | Next.js |
|---|---|---|
| What it is | Visual builder (low-code) | React framework (code) |
| Hosting | Managed by Webflow | Vercel, Netlify or your own infrastructure |
| CMS | Built-in visual CMS | Headless CMS of your choice (Sanity, Contentful, Payload) |
| Animations | Webflow Interactions | Code libraries (GSAP, Motion) |
| Workflow | Visual canvas, designer-led | Git, code review, CI/CD |
| AI agents | Webflow's MCP server, limited to the tools Webflow exposes | Any coding agent edits the code, runs the build and opens a pull request |
| Cost model | Monthly subscription (seats, plan tier, hosting) | Build time upfront, then hosting (often low or free) |
| Who edits content | Anyone, visually | Editors in the headless CMS |
| Best for | Marketing sites, landing pages, fast publishing | Web apps, custom logic, performance at scale |
Does moving to Next.js solve what Webflow users complain about?
G2, read Oct 28, 2026We read G2's published numbers for both listings on Oct 28, 2026: Webflow 4.4/5 from 996 reviews, Next.js 4.7/5 from 17. Of Webflow's 5 most-mentioned complaints, moving to Next.js solves 2, softens 2 and leaves 1 where it was.
Webflow's top complaints on G2, after the move
The curve moves rather than disappears. Developers take over the code, and Next.js reviewers raise a learning curve too. Editors stop learning the Designer and work in a CMS form.
We set up a headless CMS with preview so editors never touch code, and hand over a documented repository.
No built-in CMS or store limits. Content lives in the CMS you choose, and commerce comes from a dedicated platform wired into the site.
Collections move by script, and the price follows your page count in three published packages. Ecommerce is scoped separately.
Server rendering, static generation and image optimisation are built in, and Next.js reviewers single out fast page loading. Speed becomes your code's job, not the platform's.
We check Core Web Vitals on every template before launch.
Moving is the hard part on any platform. Next.js reviewers report a difficult setup outside Vercel and time-consuming deployment work.
That transition is the service: we run the rebuild, the content import, the redirects and the hosting setup.
Next.js is free and open source, and hosting often starts free for small sites. The subscription is replaced by build and maintenance time.
The calculator prices the build up front, so you can weigh it against your Webflow plan.
Topic labels and mention counts are G2's, from 996 Webflow reviews; the verdicts and what we do about each are ours.
What you give up from Webflow
- Ease of use 246 praise itEditors work in a headless CMS; pick one with a visual editor if they need a canvas.
- Fast publishing and CMS 158 praise itContent changes publish from the CMS without a deploy.
- Design flexibility 158 praise itLayout changes now go through code; a component library keeps common changes small.
- Visual controls 149 praise itPreview in the CMS shows the real page before it goes live.
New problems you take on with Next.js
- Difficult setup outside Vercel 2 mentionsWe set up hosting on Vercel or your own infrastructure and document the deploy.
- Learning curve 2 mentionsThe handover covers how the repository, CMS and deploys fit together.
- Time-consuming deployment and vulnerability management 2 mentionsDependency updates become your team's routine; we leave the update path written down.
- Confusing errors in production builds 1 mentionLogging and error reporting are wired in before launch.
From 17 Next.js reviews: a small sample, so read these as signals, not rates.
How G2 reviewers score each
Webflow8.6 (795)Next.js9.0 (15)Webflow8.1 (839)Next.js8.8 (15)Webflow8.4 (549)Next.js8.9 (15)Webflow8.5 (702)Next.js8.1 (13)Stated preference and revealed preference point the same way. G2 reviewers score Next.js higher on 3 of 4 shared criteria, on too few answers to call; our crawl shows the move itself, 7.5 domains leaving Webflow for Next.js for every one going back. For scale, Webflow's own G2 reviewers report 2 months to implement Webflow itself (137 responses).
Who is switching from Webflow to Next.js?
TechnologyChecker.io crawl, read Oct 28, 20263,050domains moved from Webflow to Next.js in the 90 days to Oct 28, 2026 · 541 went the other way
Counted by TechnologyChecker.io's crawl. Switched = dropped Webflow on every host we track since May 28, 2026 and currently runs Next.js. A drop is a tag disappearing from our crawl, not a confirmed cancellation. 10,150 domains run both today. Counts are domains, not accounts.
“3,050 domains moved from Webflow to Next.js in the 90 days to Oct 28, 2026; 541 went the other way (TechnologyChecker.io's crawl of 29.9M live business domains, https://technologychecker.io/migration/webflow-to-nextjs)”
Switches by month
Domains by the month Webflow (or Next.js) disappeared from our crawl. The first and last months are partial: tracking began May 28, 2026 and the data runs to Oct 28, 2026.
Recent switchers
| Company | Industry | Employees | Country | Seen |
|---|---|---|---|---|
| B2BinPay group | Financial Services | 51-200 | Estonia | Oct 28, 2026 |
| Alpha10x | Investment Management | 11-50 | France | Oct 27, 2026 |
| Agentur Triebfeder | Movies, Videos, and Sound | 11-50 | Germany | Oct 27, 2026 |
| Conta Simples | Financial Services | 201-500 | Brazil | Oct 27, 2026 |
| AdPrompt LLC. | Technology, Information and Internet | 11-50 | United States | Oct 27, 2026 |
| Acceleration | Business Consulting and Services | 501-1000 | Italy | Oct 27, 2026 |
| bureau 1440 | Telecommunications | 1001-5000 | Russia | Oct 26, 2026 |
| The 150th Aero Flying Club, Inc. | Airlines and Aviation | 51-200 | United States | Oct 26, 2026 |
What kind of company leaves Webflow for Next.js?
TechnologyChecker.io crawl, read Oct 28, 2026We matched 3,877 of the 5,002 domains that moved to a company record. Technology firms lead at 31.8%, 2.1× their share of Webflow's base, followed by financial services, advertising services, and marketing services. By size, the movers look like Webflow's own customers.
By industry
By company size
By country
Where do sites leaving Webflow go?
TechnologyChecker.io crawl, read Oct 28, 2026Next.js is the most common destination for domains that drop Webflow: 5,002 since May 28, 2026, against 2,207 for Astro, the next most common.
Next.js5,002
Astro2,207
WordPress2,000
Framer528
Squarespace307
Wix225Webflow vs Next.js: who runs each
TechnologyChecker.io crawl, read Oct 28, 2026By company size
Webflow60.7%Next.js60.5%Webflow27%Next.js23.9%Webflow8.7%Next.js8.9%Webflow2.1%Next.js3.2%Webflow1.5%Next.js3.5%By industry
Webflow6.6%Next.js9.4%Webflow4.5%Next.js2.7%Webflow4.4%Next.js7.6%Webflow3.9%Next.js2.6%Webflow3.9%Next.js6.9%Webflow3.7%Next.js3.4%Top countries for WebflowTop countries for Next.jsFast pages, tested before launch
Pages ship as static HTML with optimised images and fonts, and every template is tested against Google's Core Web Vitals on mobile before launch. Speed comes from how the site is built, not from the framework, so we measure it instead of assuming it.
HTTP Archive, September 2026: 71.3% of Webflow sites pass Core Web Vitals on mobile, against 35.7% of Next.js sites. Moving alone doesn't make a site faster; building it right does.
Build and change it by chatting with AI
Describe a change to a coding agent such as Claude Code, Codex or Cursor: a new landing page, a pricing update, a redirect. It edits the code, runs the build and opens a pull request with a preview link, and nothing goes live until you approve it. The repository ships with an AGENTS.md so the agent follows your design system.
Price follows the size of the site, counted in pages from your sitemap, CMS items included. Each package covers the rebuild, the content import, redirects, testing and launch. Interactions, localization, ecommerce and memberships are scoped on the call, because that is where estimates go wrong.
| Package | Price | Timeline |
|---|---|---|
| Small siteUp to 100 pages · A marketing site with a small blog | $1,500–$2,500 | 1 week |
| Medium siteUp to 1,000 pages · Several CMS collections, a few hundred items | $2,500–$4,000 | 2–3 weeks |
| Large site1,001+ pages · A large blog or resource library | $4,000–$6,000 | 4–5 weeks |
Does it pay back? It rarely does on hosting alone. It pays when developer control, performance and workflow speed are worth more than Webflow's convenience. For reference, Webflow's G2 reviewers report 7 months to see a return on Webflow itself (128 responses).
The right method depends on whether you have React developers and whether marketing still needs to publish without them.
Webflow DevLink
Your team's time · 1–4 weeks
Webflow's official React export. It keeps your Webflow components inside a Next.js app, but design still happens in Webflow and interactive components need client boundaries.
Best for: In-house React developers who want to keep Webflow visuals
Manual export and rebuild
Developer time · 3–8 weeks
Export the HTML, CSS and JS and rebuild each piece as React components. More work, and a clean codebase with no dependency on Webflow's export format.
Best for: A long-term re-architecture
Hire a migration team
About $5,000–$50,000+ · 4–12 weeks
One team runs the whole job: rebuild, CMS wiring, interactions, redirects and launch. You trade budget for speed and skip the learning curve.
Best for: Teams without React capacity, or a site that can't absorb SEO risk
Costs and timelines are typical market ranges for planning, not figures from our data. Our own price for your site comes from the calculator above.
Every page rebuilt in Next.js
Each Webflow page design and CMS template rebuilt as React components on the Next.js App Router, matching your current design.
CMS content moved by script
Collections exported through the Webflow API and imported into Markdown in your repo or the headless CMS you choose, with rich text, images and references carried over.
URLs and rankings protected
Same URLs wherever possible, a 301 redirect for every one that changes, and titles, meta descriptions, canonical tags and structured data carried over page by page.
Forms and embeds rewired
Forms, analytics and third-party embeds reconnected. Anything the calculator can't price, such as Webflow Ecommerce or Memberships, is scoped on the call.
Set up for AI agents
The repository ships with an AGENTS.md instructions file and documented components, so Claude Code, Codex or Cursor can add pages and make changes that match your design from a plain-English request.
Launch and handover
Deployed to Vercel or your own host, checked against the old site before DNS moves, and handed over with the repository.
- Webflow interactions and animationsWebflow Interactions run on Webflow's own runtime, so a code export doesn't bring them along.
We inventory every interaction before the build (the calculator flags them) and rebuild them with GSAP or Motion.
- CSS conflicts and hydration errorsExported Webflow styles clash with new component styles, and browser-only code rendered on the server causes hydration mismatches.
We migrate styles deliberately instead of importing Webflow's global stylesheet, and keep browser-only logic in client components.
- Preserving SEO through the moveNew URLs without 301 redirects make Google treat old pages as gone; rankings built over years reset.
Same URLs where possible, a 301 for every change, titles, meta and structured data carried over, and every old URL checked before DNS moves.
- Complex builds: many collections, localization, custom codeMulti-reference collections, Localization locales, Memberships, Ecommerce and custom embeds are where estimates go wrong.
The calculator counts each collection and flags locales, ecommerce, memberships and interactions; the fixed quote lists every one.
You don't have to move everything at once. Many domains run both: Next.js for the product and app, Webflow for the marketing pages the content team owns. The app can live under the same domain, on a path or a subdomain, with Next.js rewrites or a proxy in front.
Our crawl sees 10,150 domains running Webflow and Next.js at the same time (Oct 28, 2026). Some are partway through a move; many are a deliberate split.
If a full move is too much now, we set up the split as a smaller project and move the marketing pages later.
Ask any partner these questions before you sign, us included. A fixed price before anyone has looked at your interactions and CMS is a guess you pay for later.
| Ask | Our answer |
|---|---|
| Will you write down the migration plan before you quote? | Yes. The fixed quote lists every template, collection, interaction and integration we found. |
| How will you preserve SEO through the move? | Same URLs where Next.js allows, a 301 for every change, metadata and structured data carried over, and every old URL checked before launch. |
| Which animation library will rebuild our Webflow interactions? | GSAP for timeline sequences, Motion for component animation, mapped interaction by interaction before the build. |
| Will marketing be able to edit content without you? | Yes, in the headless CMS you choose, with preview before publishing. |
| Who owns and hosts the code when you're done? | You do: your repository and your hosting account. |
- 01EstimateThe calculator counts your pages and templates from your sitemap and prices them. It takes about a minute.
- 02Scoping call and fixed quoteWe check the estimate against your site, list anything it couldn't see, and send a fixed quote within one business day.
- 03BuildOur engineers build the templates first, using AI agents for the repetitive parts, then run the content import, redirects and forms. You review each page on a preview URL as it lands.
- 04LaunchWe compare the old and new sites URL by URL (status codes, titles, redirects), then switch DNS with you.
Expert review: is moving from Webflow to Next.js worth it?
Reviewed Oct 28, 2026Move when engineers will own the site. What you gain is control: the code lives in your repository, every change is reviewed before it ships, and a coding agent can make the edit for you. If marketing publishes every day without a developer and nobody will look after React code, stay on Webflow: the move will cost more than it returns.
The risk is in search, not in the code. Google re-crawls a migrated site URL by URL, so every changed path needs a 301 and every page needs its title, description and canonical carried across. Speed is not automatic either: in HTTP Archive's data fewer Next.js sites pass Core Web Vitals than Webflow sites, so each template has to be tested before launch.
Before you migrate: David's 4 checks
- List every URL before anything elseTake the URLs from your sitemap and from the Pages report in Google Search Console. The sitemap misses pages that still get traffic; Search Console shows them. That list becomes the redirect map.
- Freeze the CMS on a set datePick a content freeze date and export each Collection as CSV after it. Anything edited in Webflow after the export won't reach the new site.
- Measure your current speed firstRun PageSpeed Insights on your three heaviest templates and keep the scores. Launch the new site only when the same templates match or beat them.
- Keep Webflow live until the new site is verifiedSwitch DNS, then watch Search Console for 404s and dropped pages for two weeks before cancelling the Webflow plan. While the old site exists, rolling back is one DNS change.
Where this data comes from
Analysed Oct 28, 2026Our detection data
Switching counts, destinations and both platforms' user bases come from TechnologyChecker.io's own monthly crawl of 29.9M live business domains. A switch is an observed change: a domain dropped Webflow on every host we track and now runs Next.js. Company attributes come from company records matched by domain (3,877 movers matched).
Full detection methodology →The calculator
It reads only what your site publishes: robots.txt, the sitemap and up to eight sampled pages. Nothing is stored unless you ask for a quote. Pages missing from your sitemap, gated content and app-like features aren't counted; the scoping call covers them.
G2's published numbers
Ratings, respondent counts and pros-and-cons topic counts for both listings, read on Oct 28, 2026. Numbers only: no review text is reproduced, and every count links back to G2. The verdicts on each complaint are ours.
G2's comparison →TechnologyChecker sells this migration. The switching numbers come from the same crawl that powers our technology profiles and are not adjusted for this page.
How much does a Webflow to Next.js migration cost in 2026?
From $1,500 to $6,000 with us, by site size: $1,500–2,500 up to 100 pages, $2,500–4,000 up to 1,000 pages and $4,000–6,000 above that. The calculator above reads your sitemap and places your site in a package; interactions, ecommerce and memberships are scoped on a short call before the fixed quote. You pay 50% to start and 50% when the site is live.
How long does a Webflow to Next.js migration take?
About a week for a small site (up to 100 pages), 2–3 weeks for a medium one (up to 1,000) and 4–5 weeks for a large one. Pages are counted from your sitemap, CMS items included. The calculator above sizes your site, and the fixed quote confirms the date.
Should I hire a team or migrate Webflow to Next.js myself?
Do it yourself if a React developer is on staff and the site is small: DevLink or a manual rebuild costs only their time. Hire a team when nobody will look after React code, the site has hundreds of CMS items, or search traffic is too valuable to risk on a first attempt. Developer capacity decides it, not company size.
Is there a free tool that converts Webflow to Next.js?
No tool turns a Webflow site into a finished Next.js site. Webflow's DevLink exports the components you designed as React code, and its code export gives you static HTML, CSS and JS, but neither moves your CMS content, redirects or interactions into a working app. The calculator on this page is free: it counts your pages and templates and shows a package price and timeline.
Will I lose my Google rankings when I move off Webflow?
Rankings hold when URLs, content, titles and internal links survive the move. We keep URLs wherever Next.js allows, 301 every URL that changes, carry over metadata and structured data, and check every old URL against the new site before launch. If search traffic drops after launch, we find and fix the cause at no extra cost.
Can I serve a Next.js app under my Webflow domain?
Yes. Keep Webflow on the marketing pages and route a path such as /app, or a subdomain, to the Next.js app with rewrites or a proxy. Many sites run this split on purpose; see the hybrid path above.
When should I use Webflow instead of Next.js?
When marketing owns the site, needs same-day publishing without engineers, and the site is a small marketing site the builder handles without workarounds. Rebuilding that in Next.js is usually the wrong call.
Should I move to Framer instead of Next.js?
Choose Framer if designers should keep a visual canvas and nobody will maintain code: it is a hosted builder, like Webflow. Choose Next.js if engineering owns the site, you need an app or custom logic on the same domain, or you want AI coding agents to make changes. In TechnologyChecker.io's crawl, Next.js is the most common destination for sites leaving Webflow, well ahead of Framer.
Is migrating from Webflow to React too risky?
The risk sits in three places: lost redirects, dropped interactions and a CMS editors can't use. Each has a known fix: a URL-by-URL redirect map, an interaction inventory before the build, and a headless CMS set up before launch.
Can I manage a Next.js site by chatting with AI?
Yes. Because the site is code in your repository, a coding agent such as Claude Code, Codex or Cursor can make any change you describe, from a new landing page to a redirect rule or a CMS field. It builds the site to check its work and opens a pull request with a preview link; you approve it before it goes live, and any change can be rolled back. We hand the repository over set up for this, with an AGENTS.md instructions file and documented components so the agent follows your design system. Webflow also has an MCP server, but an agent there is limited to the tools Webflow exposes.
Can you migrate a complex Webflow build with multiple collections, localization and custom code?
Yes. The calculator counts every collection and flags localized pages, ecommerce, memberships and interactions. Those are scoped on the call and listed in the fixed quote.
Webflow or Next.js for a B2B marketing site?
If marketing publishes daily and nobody maintains code, stay on Webflow. If the site shares a design system with your product, or needs programmatic pages and custom integrations, Next.js fits better.
What happens to my Webflow CMS content?
Collections are exported through the Webflow API and imported by script, so item count adds little to the cost. You choose where the content lives afterwards: Markdown files in the repository or a headless CMS.
How does the calculator count pages and templates?
It reads your robots.txt and sitemap, treats each top-level page as its own design, and treats any folder holding three or more pages (such as /blog/...) as one CMS collection. It loads a sample of pages to judge how heavy each design is. Pages missing from your sitemap aren't counted.
Who does the migration?
TechnologyChecker's own engineers, not an automatic converter. People plan the build, write and review the code and check every page; AI coding agents take the repetitive work, which is why it's faster and cheaper than a traditional rebuild. We run the detection crawl behind the switching numbers on this page, and we deliver migrations ourselves rather than passing them to a partner.
Where do the switching numbers come from?
From TechnologyChecker.io's own detection crawl of 29.9M live business domains, run every month. A switch counts when a domain that ran Webflow stops showing it while it runs Next.js. Counts are domains, not companies, and each figure carries the date it was measured.
How can I export code from Webflow?
Open the site in Webflow and choose Code export from the main menu (Shift + E) to download a zip of the HTML, CSS, JavaScript and images. Code export needs a paid Workspace plan; a Site plan alone doesn't include it. The zip leaves out your CMS content, so each Collection has to be exported as CSV, and forms and site search stop working once the site is hosted elsewhere. That is why a rebuild moves content by script and rewires every form.
Is Next.js basically React?
Next.js is a framework built on React. You write React components; Next.js adds what a website needs that plain React leaves out: routing, server-rendered and static pages for SEO, image optimization and redirects. Moving from Webflow to Next.js means moving to React with those parts already in place.
Is Next.js still good in 2026?
For sites that engineers own, yes. TechnologyChecker.io's crawl finds Next.js on 731,970 live domains in October 2026, and it is the most common destination for sites leaving Webflow: 5,002 domains since May 28, 2026. It is not faster by default: in HTTP Archive's September 2026 data, 35.7% of Next.js sites pass Core Web Vitals on mobile against 71.3% of Webflow sites, so a migration has to be built and tested for speed.
Is Webflow still used?
Yes. TechnologyChecker.io's crawl finds Webflow on 262,281 live domains in October 2026, and sites still move to it: 666 domains went from Next.js to Webflow since May 28, 2026, against 5,002 the other way. For a marketing team that publishes without developers, Webflow remains a sound choice.
Is there anything better than NextJS?
For a content site with little interactivity, Astro is the main alternative: it ships far less JavaScript by default. Among sites that left Webflow since May 28, 2026, TechnologyChecker.io's crawl finds 2,207 now on Astro against 5,002 on Next.js. Choose Next.js when the site shares a domain or code with a React app, or needs logged-in features.
How do I stop paying for Webflow?
Downgrade or cancel the Site plan in Site settings under Plans, then downgrade the Workspace plan to Starter if you no longer need it. Do it after the new site is live: export your CMS Collections and form submissions first, point the domain at the new host and check the redirects, so you can still roll back if something was missed.
Includes questions people also ask on Google about this move, quoted as Google shows them; the answers are ours.