Webflow review

Webflow combines visual website building, content management and site-growth tools in one platform. Teams can design pages on a visual canvas, control layouts and typography, and publish content through a CMS. The platform also supports shared workspaces for design, development and marketing teams, plus controls over what content goes live and when.

Its growth features cover SEO and answer-engine optimization (AEO), including exploring how AI crawls a site and tracking visibility in AI answers. Webflow also offers tools for A/B testing, personalization and testing multiple variables with AI. Page branching lets teams work on static or CMS pages, resolve conflicts and track activity before merging changes.

There is a free Starter plan, while the pricing page lists Basic at $15 per site per month and Premium at $25 per site per month when billed yearly. Monthly rates are not published.

Webflow’s main appeal is keeping design, publishing and team workflows in one place. Marketers can edit on the visual canvas, while designers control layouts and typography; teams can share a workspace instead of splitting those tasks across separate tools. CMS publishing controls let teams decide what goes live and when, and page branching supports changes to static and CMS pages before they are merged.

The plan limits give a rough sense of which sites fit:

• Starter is for experimenting: 2 static pages, 50 CMS items and 20 CMS Collections.
• Basic supports simple sites without a CMS, with 300 static pages, a custom domain and unlimited form submissions.
• Premium is aimed at content-rich sites: up to 20,000 CMS items, 40 CMS Collections and site search.

Webflow also offers SEO/AEO and conversion features, including AI-answer visibility tracking, A/B testing and personalization. These make the platform relevant to marketing teams that want more than a page builder. Optional Optimize, Analyze and Localize add-ons are available, though their prices are not published.

The plan boundaries matter. Starter has just 2 static pages, 1 GB of monthly bandwidth and 50 form submissions. Basic includes 10 GB of monthly bandwidth but is positioned for sites without a CMS. Premium raises the CMS allowance to 20,000 items and bandwidth to 2.5 TB, but costs $25 per site per month when billed yearly. Monthly prices are not published. Team is listed at $2,500 per site per month and requires an annual contract; Enterprise pricing is custom.

Cloud overages are also priced separately: the pricing material lists $2 per 1 million requests and additional charges for compute, storage and operations. Optional add-on prices are not published.

One Reddit thread describes a site using 400 GB of bandwidth and 2,000 CMS items whose owner expected a bill to rise from $476 to more than $2,000, plus seats and workspace costs. That is one user’s account, not a universal quote, but it makes a plan-by-plan cost check essential. Reddit commenters also warn that moving 2,000 structured CMS items can be the harder part of switching; test the import before committing to an alternative.

The pricing page lists Basic at $15 per site per month and Premium at $25 per site per month, both billed yearly. Starter is free, but limited to 2 static pages, 50 CMS items and 1 GB of monthly bandwidth. Basic raises the page limit to 300 and includes a custom domain, but has no CMS items listed. Premium is the tier for CMS sites: it includes 20,000 CMS items, 40 Collections and up to 2.5 TB of monthly bandwidth.

The jump to Team is steep: it is listed at $2,500 per month per site, with an annual contract required. It adds Localize, AEO agents, publishing workflows and priority support. Enterprise pricing is custom. Monthly rates for Basic and Premium are not published, so compare annual commitments rather than assuming you can pay month to month.

Optimize, Analyze and Localize are optional add-ons with unpublished prices. Premium Cloud overages are separately priced, including $2 per 1 million requests. Check expected usage and add-on costs before budgeting.

Plan the move around your content and publishing setup, not just the page designs. Webflow’s listed plans distinguish static pages from CMS items and Collections, so inventory both before choosing a tier. Check forms, custom domains, search and any publishing workflows you rely on; the published materials do not explain how those assets transfer from another platform or export from Webflow.

That leaves two key migration questions unanswered: what data you can export, and how much work it takes to rebuild your site elsewhere. We would confirm both with Webflow before committing, especially if your site depends on CMS content or custom design work. The published materials include no Reddit posts or comments, so we can’t responsibly say what users report as reasons for leaving. Treat portability as an open item, not a guaranteed feature: ask for export details and test a small content sample before moving a large site.