How Much Does a Webflow Website Cost in 2026? Platform Fees vs Project Costs
For a company website with a blog or any other CMS content, Webflow's own fee is the Premium Site plan: $25 a month billed yearly, or $39 billed monthly (Webflow list prices in USD, checked on webflow.com/pricing on 15 Oct 2026; prices change). Everything else in the budget is project work: research, copy, design, templates, CMS set-up, integrations, migration, testing and launch. Its cost depends on scope, so ActiveSet does not publish project prices here: two sites with the same page count can need very different amounts of work.
Last updated 15 October 2026. Webflow prices in this guide were checked on Webflow's pricing page the same day.
There is no useful single price for every B2B website. A small site built from approved content is a different engagement from a multilingual migration with hundreds of existing URLs. The most reliable estimate starts with a shared scope and a clear definition of what counts as finished.
What does Webflow itself cost?
Webflow's pricing page lists these platform fees. They are list prices in USD, checked on 15 Oct 2026; tax is added at checkout and prices change, so re-check before you commit a budget.
| Line on the Webflow bill | What it covers | Webflow list price |
|---|---|---|
| Basic Site plan | One site on a custom domain, for sites that don't need a CMS; 300 static pages | $15 a month billed yearly, $25 billed monthly |
| Premium Site plan | One site with the CMS: 20,000 CMS items, 40 Collections, 300 static pages, 50 GB bandwidth | $25 a month billed yearly, $39 billed monthly |
| Full seat | A person who designs full sites or manages admin settings | $39 a month per seat, billed yearly |
| Limited seat | A person who edits content or builds pages with components | $15 a month per seat, billed yearly |
| Reviewer seat | Reviewers and commenters | Free |
| Workspace plan | Starter is free and includes the owner's Full seat; Core and Growth add staging and collaboration tools | Starter free; Core $19 and Growth $49 a month, billed yearly |
| Team (Platform plan) | A site and Workspace with 5 Full and 5 Limited seats, Webflow Localize with 2 locales, 100 Collections, page branching and single-page publishing | $2,500 a month, annual contract required |
| Enterprise | Custom limits, single sign-on, invoice billing | Not published; quoted by Webflow |
Two rules shape the total. Site plans are per site: Webflow's Choose a Site plan article says each site you host on a custom domain needs its own Site plan, billed separately from the Workspace plan. Seats are per Workspace, and every Workspace includes one Full seat for its owner (Choose a Workspace plan). For example, a Premium site whose Workspace owner does the design work, plus three content editors on Limited seats, comes to $25 + 3 × $15 = $70 a month on yearly billing, before add-ons. Each extra person who needs a Full seat adds $39 a month.
These are platform prices, not design or development fees. An agency quote may or may not include them, so ask.
Webflow distinguishes the plan for an individual hosted site from a Workspace plan used for team capabilities and collaboration. A paid Workspace is not automatically a substitute for the site's hosting plan. Check who owns the site, which people need access and which roles they need before deciding what to buy. Webflow's plan overview explains the distinction.
What changes the project quote?
Count both unique templates and content records. Twenty pages built from one approved case-study template can require less design work than five completely different interactive pages. Content preparation and quality checks still take time, even when layouts repeat.
| Scope area | What to define before asking for a quote | Common source of extra work |
|---|---|---|
| Strategy and copy | Audiences, messaging, page goals and who writes each page | Rewriting content after layouts are approved |
| Design | Unique page types, reusable sections and responsive behavior | Treating every page as a new design |
| CMS | Collections, fields, relationships and editor tasks | Discovering missing content types during development |
| Migration | Existing URLs, content records, redirects and retained assets | Missing source exports or late URL changes |
| Integrations | Forms, CRM, attribution, search and other connected tools | Unclear data ownership or unavailable test accounts |
| Localization | Languages, translated content and review responsibilities | Assuming translation also covers local design and QA |
| Motion and media | Specific interactions, assets and fallback behavior | Unspecified effects or oversized media |
| Launch and handoff | Test cases, approvers, training and support | No agreed acceptance or ownership process |
For an existing design, our Figma-to-Webflow service is a more relevant starting point than a full redesign brief. If the content and structure also need to change, scope the website redesign work explicitly.
How does each driver move the quote?
The table above says what to define. This one says what each driver changes, so you can see why two quotes for "a 20-page site" can be far apart.
| Driver | What to count | What it changes |
|---|---|---|
| Unique page templates | Distinct layouts, not pages: home, product, pricing, blog post, case study, landing page | Design and build effort. Twenty pages on one template cost less to build than five unique pages. |
| CMS Collections and items | Repeating content types and how many items each holds, now and in a year | Content modelling, import and QA effort; plan headroom (Premium: 20,000 items and 40 Collections) |
| Integrations | CRM and forms, scheduling, marketing automation, analytics and consent, search, gated content | Build and testing effort, and risk: each one needs a real test account and someone who owns the data |
| Languages | Locales at launch and within 12 months | Translation review, layout checks per language and a recurring Localize fee per locale (localization cost guide) |
| Content to migrate | Pages, posts and URLs that move from the current site | Import, clean-up and a redirect map. Webflow's migration overview says there is no automated way to convert a site from another platform, so moving is a rebuild. |
| Design and copy status | Approved Figma, wireframes, brand guidelines only or nothing yet; copy ready, needing edits or needing writing | Whether discovery, design and writing are in the quote at all, and how many review rounds the timeline needs |
| Accessibility and QA level | Browsers and devices, accessibility checks, form and redirect tests, who signs off | Testing effort before launch, and how much rework is found late |
How big is your project?
Before you brief anyone, write your own answers to the drivers above. Count templates rather than pages, list the content types that repeat, and name every tool the site must connect to. Note the design and copy status honestly: "we have a brand" and "we have approved Figma files" lead to very different quotes.
The worksheet below follows the same fields. Tick each line as you fill it in, then print the page or save it as a PDF and send the same version to every agency on your shortlist. Nothing you enter leaves your browser. For the rest of the brief (goals, stakeholders, timing and acceptance criteria), use our Webflow website brief template.
Build a first-year budget
Use this worksheet to compare proposals. Put each item in one category so that an annual subscription is not counted again inside a monthly operating estimate.
| Budget line | Amount to collect | Billing basis |
|---|---|---|
| Discovery, copy and design | Approved project quote | One time or milestone based |
| Development and CMS setup | Approved implementation quote | One time or milestone based |
| Migration and launch | Included scope or separate quote | One time |
| Webflow site and team access | Selected plan and required seats | Monthly or annual |
| Domain and external services | Registrar, CRM, forms, search and other necessary services | Monthly or annual |
| Ongoing support | Defined support agreement | As agreed |
| Internal team time | Estimated hours for writing, approvals, training and testing | Internal cost |
| Contingency | Amount chosen for unresolved scope | Planning reserve |
First-year budget = one-time work + annual recurring charges + 12 × monthly recurring charges + internal costs + contingency.
Keep a list of assumptions next to that total. An estimate that assumes clean content, one language and no CRM work cannot be fairly compared with a proposal that includes rewriting, localization and lead-routing implementation.
How to compare two agency proposals
Ask both agencies to price the same brief and identify exclusions. Then compare five things:
- Deliverables: which pages, templates, content records and integrations are included?
- Responsibilities: who provides copy, assets, access and approvals?
- Acceptance: how will responsive behavior, accessibility, forms, redirects and editor workflows be checked?
- Changes: what happens when the scope changes, and who approves additional work?
- Ownership: who controls the domain, website, connected accounts and documentation at handoff?
A lower quote can be appropriate when you already have approved designs and clean content. It can also move necessary work onto your team. Ask where that work appears in the budget rather than treating every price difference as a quality difference.
Then go line by line. Mark each item "in", "out" or "unclear" for both proposals; anything unclear is a question for the next call, not an assumption.
Where can you reduce cost responsibly?
Prioritize the pages needed for the next business milestone. Reuse agreed layouts, prepare assets early and nominate one person to consolidate feedback. A phased release can make the scope easier to manage, provided the migration and linking plan handles the pages that remain on the old system.
Keep functional launch checks in the scope. A lead form that looks right but routes nowhere, or a migrated page without its intended redirect, can create work after launch. For an existing site, review our migration service alongside the build proposal.
What should happen after launch?
Agree who handles routine content requests, technical defects, analytics checks and changes to connected tools. Define response expectations in the contract rather than assuming that every support arrangement provides the same coverage. Our Webflow maintenance service provides a starting point for that conversation.
To get a useful project estimate, bring an existing-site URL, a page and template inventory, design status, content ownership, required integrations, languages, launch constraints and the tasks your marketing team needs to perform after handoff. Talk to ActiveSet about that scope, then evaluate the written proposal against the same checklist.
What keeps running on the Webflow bill?
The build is a one-off. These lines recur, and they belong in the first-year budget above:
- The Site plan, renewed monthly or yearly for each site.
- Seats, as editors join or leave. Full and Limited seats are charged per person per month; reviewers are free.
- Add-ons, if you need them: Localize per locale, extra bandwidth on Premium (from $20 a month for +50 GB, billed annually), Analyze and Optimize. Webflow's Manage add-ons article notes that add-ons follow the billing cycle of the Site plan.
- Upkeep: content updates, connected-tool changes, accessibility and SEO checks. Our Webflow maintenance checklist separates what Webflow handles from what your team owns.
If your site sits in an agency's or freelancer's Workspace, Webflow's 2026 Site plan changes reach it on 16 November 2026, later than other sites. Our guide to Webflow's November 2026 plan changes explains what changes.
How does ActiveSet scope a Webflow project?
ActiveSet is a Webflow Premium Partner based in Bengaluru, India. We size every project from the drivers in this guide and put the scope in a written proposal; we don't publish project prices because the same page count can hide very different work.
Our usual order is a discovery questionnaire and call, stylescapes, Figma design, the Webflow build, a review on staging in Markup.io, then launch, with the work tracked in ClickUp and a shared Slack channel. We build on Finsweet's Client-First with the style guide set up first and reusable components. Sites are built in, or transferred to, the client's own Webflow Workspace, with an editor guide or short recorded walkthroughs at handover. If your project is a redesign, see our Webflow website redesign service.
Disclosure: ActiveSet is a Webflow Premium Partner and earns a commission from Webflow on Webflow plans. The prices in this post are Webflow's own list prices.
Sources
- Webflow, Plans & pricing, checked 15 Oct 2026
- Webflow Help Center, Updated pricing and simplified plans for May 2026, updated 31 Aug 2026, checked 15 Oct 2026
- Webflow Help Center, Choose a Site plan, updated 2 Aug 2026, checked 15 Oct 2026
- Webflow Help Center, Choose a Workspace plan, updated 13 May 2026, checked 15 Oct 2026
- Webflow Help Center, Webflow Workspace and Site plans overview, checked 15 Oct 2026
- Webflow Help Center, Manage add-ons, updated 23 Sep 2026, checked 15 Oct 2026
- Webflow Help Center, Migrate your site to Webflow overview, updated 16 Jul 2026, checked 15 Oct 2026
Frequently Asked Questions
Webflow's fees are the platform: a Site plan per site, seats for the people who edit, and optional add-ons such as Localize or extra bandwidth. They are list prices on Webflow's pricing page. The project cost is the work of planning, designing, building, migrating and testing the site, priced by whoever does it. Budget the two separately, because the platform fee recurs and the project is mostly one-off.
Usually because they price different scope. One quote may count templates where the other counts pages, include copywriting or leave it out, or treat migration and redirects as extra. Integrations, languages and the design starting point also move effort a lot. Ask both agencies to price the same written brief and list exclusions, then compare line by line before comparing totals.
For one CMS site on yearly billing, Webflow's list price is $25 a month for Premium, plus $39 for each extra Full seat and $15 for each Limited seat; the Workspace owner's Full seat is included (checked 15 Oct 2026). Add Localize, bandwidth or analytics add-ons if you use them, your domain, connected tools such as a CRM, and any support agreement. Prices change, so check webflow.com/pricing.
The project work itself, your domain registration, third-party tools such as a CRM, scheduling, consent or membership software, translation review, stock images and fonts, and any support or maintenance agreement. Internal time for writing, approvals and testing is also a real cost. List these lines next to the Webflow fees so the first-year total is complete.
Not always. Many agencies quote the build only and expect the client to pay Webflow directly, often with the site in the client's own Workspace. Others add plan fees for a period. Ask each agency which Webflow plan, seats and add-ons they assume, who pays Webflow, and whose Workspace the site will live in at launch, so the totals are comparable.
