The wrong reason to pick either: “it is what we know.” A marketing site outlives most of the team that built it, so the maintenance owner should decide.

Who Maintains the Site After Launch?

This is the deciding question, and it is organizational, not technical.

If a marketer publishes landing pages without engineering tickets, Webflow pays for itself in a month. Every page change in Next.js becomes a pull request, a review, and a deploy — in a busy marketing org that is a two-day lead time on a headline fix.

If an engineer already owns the site and it also hosts the app, Next.js in the same repo is less total surface area. Two systems to maintain is worse than one, always.

How Do the Costs Actually Compare?

Webflow’s list price looks higher than Vercel hosting. Add engineering time and it flips fast. At a loaded $80/hour, the initial Next.js build alone equals three to five years of Webflow site plan fees.

What Dynamic Features Break the Webflow Case?

These, roughly in order of frequency:

• User-specific content — logged-in pricing, account dashboards.
• Complex search across thousands of items; Webflow’s site search is basic.
• Multi-step forms with server-side validation and persistence.
• A/B testing with proper statistical control — Webflow’s optimization product is limited compared to a dedicated testing tool.

Each is solvable in Webflow with embeds and third-party scripts, but at that point you are maintaining a hybrid that nobody fully owns.

How Does the Editor Experience Differ in Practice?

Webflow’s editor lets a marketer change copy, images, and CMS items without touching layout. That is bounded and safe.

Next.js with a headless CMS gives similar editing, but only after someone builds preview, routing, and image handling. The gap is not capability — it is the initial 40-120 hours plus ongoing friction when an editor asks for a layout change.

What About SEO and Performance?

Both output fast sites if you do not over-build. Webflow ships clean semantic HTML by default; a badly configured Next.js site with client-side rendering and unoptimized images can easily score worse.

The real difference is image handling. Next.js gives you automatic format negotiation and responsive sizing you control precisely. Webflow’s built-in image optimization is decent but you get less control over the exact markup. Unless you are chasing a specific Core Web Vitals number, this rarely decides anything.

How Do I Handle the Migration Either Way?

Migrating to Webflow: rebuild pages in the designer, re-add CMS items via CSV import, then redirect old URLs. Expect two to three weeks for a 30-page site and set up 301s for every URL — nobody does this thoroughly the first time.

Migrating off Webflow: export HTML/CSS, then re-implement the CMS in another system, because export drops dynamic content entirely. Budget more time for the exit than the entry.

When Should You Pick Neither?

If the site is five pages of copy and one contact form, use a static generator or even a hosted page builder. Neither Webflow’s editor depth nor Next.js’s flexibility pays off at that size.

Quick Summary

• The deciding factor is who maintains the site, not which tool is technically better.
• Webflow is $23-39/month; Next.js costs 40-120 engineering hours up front.
• Personalization, complex search and multi-step forms are where Webflow needs help.
• Webflow exports drop CMS content, so migration out costs more than migration in.
• For five-page sites, neither option is justified.

It is not a drag-and-drop page builder in the Wix sense. The learning curve is real, and it exists because Webflow gives you CSS control rather than template choices.

What Is Webflow and Who Is It For?

Webflow is a visual web development tool. You place elements on a canvas, and every change writes real CSS properties — flexbox, grid, spacing, typography. Nothing is abstracted into a proprietary format at runtime.

That makes it a good fit for designers who know CSS concepts and want production-grade output without a developer. It is a bad fit for someone who wants to pick a theme and type text.

How Do I Build the Layout Without Fighting It?

Use the box model deliberately. Every element is a box, and every container controls its children.

1. Add a Section for each page band. Sections give full-width backgrounds.
2. Inside, add a Container to constrain content width — 940px or 1200px are common.
3. Use Grid for card layouts and Flex for rows. Mixing both in one band creates the alignment bugs people complain about.
4. Style the class, not the element. Renaming a class updates every instance; styling an element creates one-off overrides you will hunt down later.

Set breakpoints in this order: desktop, tablet, mobile landscape, mobile portrait. Webflow inherits down, so desktop changes bleed into tablet unless you override.

How Do I Add a CMS Collection?

Open the CMS panel, create a collection (say, Blog Posts), and add fields: Name, Slug, Rich Text body, Image, and a Reference to an Author collection.

Then on a page, add a Collection List, bind it to the collection, and style the first item — the rest inherit. Add a Collection Page so each item gets its own URL.

Collection limits matter: the CMS site plan caps items at 2,000 per collection, and 10,000 total across the site. That is fine for a blog and a hard stop for a product catalog.

How Do I Publish and Connect a Domain?

Click Publish and pick a webflow.io subdomain — that is free and works immediately for testing.

For a custom domain, you need a paid site plan. Add the domain under Project Settings → Publishing, then create the A and CNAME records Webflow shows you. SSL provisions automatically, usually within an hour.

What Does Webflow Cost in 2026?

The Site plan (Basic) is $23 per month billed annually and includes 150 pages, 2,000 CMS items, and 10 GB bandwidth. The CMS plan at $39 per month raises items to 2,000 per collection and adds 3 content editors. Workspace seats are billed separately, which surprises people — a two-person team pays for the site plan plus seats.

Staging is unlimited and free on paid plans, so build on staging and push to production when it is ready.

What Is the Export Gotcha?

The Basic site plan includes code export; the CMS plan does too, but exported sites lose their CMS — collections stay in Webflow’s servers and you get static HTML of whatever was published. If you plan to export and host elsewhere, CMS content has to be migrated by hand, and dynamic features like forms stop working.

That constraint is deliberate. Treat Webflow as a hosting commitment, not a temporary design tool.

Who Should Skip Webflow

Anyone who needs heavy custom application logic, server-side rendering, or a team of engineers maintaining the codebase. Also skip it if you want a blog running this week with no design ambition — the setup time is measured in days, not hours.

Quick Summary

• Webflow writes real CSS; it is a visual dev tool, not a template builder.
• Build with Sections and Containers, use Grid or Flex per band, and style classes.
• Basic site plan is $23/month annually: 150 pages, 2,000 CMS items.
• CMS data does not survive code export — treat Webflow as your host.
• Publishing to a custom domain requires a paid site plan.