Book a call

Compare

Webflow vs HubSpot in 2026

Webflow if designers need control and the content has a shape of its own. HubSpot if the site should sit inside the CRM you already run and change by contact.

Trusted by teams from pre-seed to the S&P 100

  • Morse Micro
  • Lumos
  • Superpower
  • Managed
  • Keeyu
  • Crimson Education
  • Trusst AI
  • Kaizn
  • Everlab
  • Startmate

So, which one?

Each is the better pick for a different team. Here’s which.

  • Designers edit it:Some
  • Marketers edit it:Strong
  • Developers own it:Limited
  • Publish a lot:Strong
  • App-like features:Limited
  • Live in weeks:Some

Webflow is usually better if

  • Designers need to change layouts without a developer
  • Case studies, people or products need fields of their own
  • You might stop using HubSpot as your CRM one day
  • Designers edit it:Limited
  • Marketers edit it:Strong
  • Developers own it:Some
  • Publish a lot:Some
  • App-like features:Limited
  • Live in weeks:Some

HubSpot is usually better if

  • Forms and pages should write to the CRM with no connector
  • Pages should change by CRM record, source or device
  • You test page versions inside HubSpot already

Which way each one leans

The middle means it’s even.

WebflowHubSpot
  1. Marketing sites where design and linked content lead

    Best forEven

    B2B teams whose marketing already runs in HubSpot

  2. Embedded HubSpot forms, or tools such as Zapier and Make

    Link to the CRMLeans HubSpot

    Built in: forms write to contacts, smart content reads them

  3. Designers change layouts visually in Webflow

    Design changesLeans Webflow

    Developers write themes in HubL or React, editors arrange modules

  4. Collections with fields you define, linked by references

    Content structureLeans Webflow

    Pages and blogs, plus HubDB tables on a higher tier

  5. Sitemap and canonical URL to switch on, a schema field

    Search settingsEven

    Sitemap and canonicals by default, schema coded in templates

  6. Marketers in a content role, each on a Workspace seat

    Who edits itEven

    Marketers on Core Seats, with view-only seats free

  7. Site code on a paid Workspace plan, collections as CSV

    Leaving laterLeans Webflow

    HTML export with HubL templates, and forms to replace

Reviewed

Webflow and HubSpot in detail

What the site gains inside HubSpot, then tiers, design, content, search, cost, moving and who each one is wrong for.

What the site gains inside HubSpot

This page is for a team that already runs HubSpot as its CRM and is deciding where the website should live. HubSpot sells its website product as Content Hub. It used to be called CMS Hub, and a few of HubSpot’s own pages still use the old name. A site doesn’t need Marketing Hub. From here on we call it HubSpot.

A site built in HubSpot sits in the same account as your contacts. Forms on its pages write straight to the CRM, and each paid tier of Content Hub comes with the CRM at the same tier. From the Professional tier, a section of a page can change for each visitor by their contact record, where they came from, their device or a query string. HubSpot calls that smart content. The same tier adds A/B testing and adaptive testing of up to five versions of a page.

A Webflow site reaches the CRM from outside. HubSpot forms can be embedded on it, and Webflow’s APIs, or tools such as Zapier and Make, can carry other data across. We didn’t find anything in HubSpot’s documentation saying smart content works on pages hosted somewhere else, so don’t plan on it.

There is a middle route. A domain or subdomain can host content in only one place, and HubSpot’s advice for using two platforms is a subdomain for each. That lets the main site stay on Webflow while campaign landing pages live on a HubSpot subdomain.

So the decision rests on how much of your marketing depends on pages that change by contact, or on tests run inside HubSpot. If a lot of it does, the site belongs in HubSpot. If the site mainly has to look right, hold structured content and pass leads to the CRM, an embedded form does that from Webflow.

The tools we connect sites to

What each Content Hub tier opens up

HubSpot gates most website features by tier, so the tier decides what kind of site you can run. This is the structure as HubSpot’s product catalogue and knowledge base describe it.

  • The free tools: 30 website pages, 30 landing pages and one blog of up to 100 posts, all carrying HubSpot branding. Hosting, a custom domain and the design manager for templates are included. The redirects tool is not.
  • Starter: HubSpot branding removed and the redirects tool added. The cap stays at 30 website pages, which HubSpot lists as limited functionality. One Core Seat is included.
  • Professional: up to 10,000 website pages and 100 blogs, smart content, A/B and adaptive testing, HubDB tables for pages built from data, content staging for a redesign, member-only pages for two access groups, single sign-on and three Core Seats.
  • Enterprise: serverless functions, up to 10 root domains, 100 access groups, content limited by team, and five Core Seats.

For most B2B marketing sites that puts the real choice at Professional. Thirty pages is tight once service pages, case studies and landing pages add up. Pages generated from HubDB don’t count toward the cap, but HubDB itself needs Professional.

Design and who can change it

Webflow is a visual builder. Someone on a full seat designs and builds the site in Webflow itself, and a limited seat can edit content or put pages together from components. People in the content editor role change copy, media and collection items, and the layout is protected from them. Whether each one can publish is a setting.

On HubSpot the design lives in a theme. Developers write its templates and modules in HubL, HubSpot’s template language, or write modules in React. Editors then build pages in a drag-and-drop editor from the modules the theme provides. Every account has at least one default theme, and more are sold in HubSpot’s Template Marketplace. A permission called Design tools decides who may change templates and modules.

In practice a new kind of page on HubSpot is a developer’s job, and on Webflow a designer can make it.

Undo works differently too. HubSpot keeps a version history for each page and post on every plan, and templates and coded files have their own revisions. A restored version comes back as a draft. A page that has been deleted can only be recovered by HubSpot Support. Webflow’s restore points cover the whole site in one go, collection item IDs included, and you can save one yourself before a big change.

Content beyond pages and posts

HubSpot’s core content is website pages, landing pages and blogs, and a Professional site can run up to 100 blogs. Anything more structured goes in HubDB, HubSpot’s database tables for dynamic pages. A table holds up to 10,000 rows, an account up to 1,000 tables and a million rows in all, and tables stay drafts until they are published. HubDB has an API, so another system can read the data or sync it. Whatever the tier, an account tops out at 10,000 website pages and 10,000 blog posts.

Webflow’s CMS is a set of collections you design. Case studies, people, events and resources each get the fields they need, and a collection can reference up to 10 others outside Enterprise. A list on a page shows up to 100 items, and how many items the site can store depends on its Site plan. Webflow’s APIs reach the collections too.

The gap shows when content links to other content. In Webflow, a case study can point at the services and people it involves through reference fields an editor fills in. In HubSpot the same thing is HubDB tables, plus templates someone has to write to display them.

For Morse Micro, a semiconductor company, we designed and restructured their website and built it in Webflow with reusable templates, CMS structures and components.

Morse Micro case studyWhat a headless CMS is

How each one charges

We leave prices out because they change. What follows is how each vendor bills.

HubSpot charges for Content Hub by tier. Each paid tier brings the CRM at the same level and a set number of Core Seats, the seats that can create and edit content, and you buy more as the team grows. View-only seats are free and unlimited, but they can’t edit. Hosting, the security certificate and the CDN are in every tier. A certificate of your own is a paid add-on. AI features draw on a monthly allowance of HubSpot Credits that doesn’t carry over.

For a team already paying HubSpot, the mix of tiers matters. HubSpot prices every Core Seat at the highest tier you hold in any hub. Before adding Content Hub, ask what it does to the price of the seats you already have.

Webflow bills each site on a Site plan, which brings hosting and sets the bandwidth, and moves the site up a plan if it runs over two months in a row. People are billed separately as Workspace seats. Since October 2026 that includes everyone who edits content. Localisation costs extra.

Webflow with HubSpot connected means two bills: Webflow for the site and HubSpot for the CRM you already have. HubSpot alone means one vendor, priced by tier and seat. Price both over the life of the site with your real number of editors.

What a B2B website costs

Moving between Webflow and HubSpot

Either direction is a rebuild. Webflow says there is no automated way into Webflow from any platform. HubSpot shut down its website migration service on 7 October 2026, though one of its product pages still advertises paid migration.

Into HubSpot, the website import brings over only each page’s title, URL and meta description, plus the navigation, 400 pages at a time. The pages are built again in the theme. Blog posts come in more easily, from a CSV file or with smart copy, which reads posts from any CMS, up to 400 per import. Webflow exports each collection as CSV.

Out of HubSpot, you get pages, posts and templates as HTML, blog data as CSV or a spreadsheet, and HubDB tables as CSV with images as links. Webflow’s CMS takes CSV files of up to 4 MB, and images imported that way get no responsive versions, so upload the key ones again.

HubSpot exports its redirects as CSV too. A HubSpot account can hold 10,000 fixed redirects, and Webflow recommends staying under 1,000 with wildcard rules, so a long list needs condensing first. A Webflow import replaces every redirect already there. Going into HubSpot, redirects upload 500 at a time, and one bad row stops the whole file.

We inventory valuable URLs, plan redirects and check canonicals, indexability, content and internal links. We also monitor after launch. These steps manage migration risk; they cannot guarantee that rankings will stay unchanged.

What a 301 redirect isWhat a website migration involves

Who should not choose HubSpot

HubSpot is the wrong home for some sites, even for a team on its CRM. We’d build elsewhere if:

  • Designers want to make new layouts themselves. On HubSpot those are templates a developer writes.
  • The site needs more than 30 pages and the budget won’t reach Professional. Starter has the same page cap as the free tools.
  • Content links in many directions. Structured content means HubDB, which needs Professional and templates to display it.
  • You might change CRM in a few years. With the site in HubSpot, leaving the CRM means moving the website as well.
  • The site needs server-side code below Enterprise. Serverless functions are Enterprise only, with a 15-second limit.
  • You want llms.txt or AI crawler settings built in. We found neither in HubSpot’s documentation.

WordPress vs HubSpot

Who should not choose Webflow

Webflow is the wrong choice for some HubSpot teams as well. We’d keep the site in HubSpot if:

  • Pages should change for each visitor based on their contact record.
  • Campaigns depend on A/B or adaptive tests run on HubSpot pages.
  • Nobody will own the link between the two. Embedded forms and connectors need someone to set them up and keep them working.
  • Your editors already have HubSpot Core Seats, and a Webflow seat for each would be a second bill.
  • Developers already look after a HubSpot theme and the marketing team knows the editor well.

Webflow vs WordPress

How to decide

Write down what your marketing needs the website to do this year and next. If much of it is pages that change by contact, tests run in HubSpot or member-only content, put the site in HubSpot and plan for Professional. If it is design, linked content and the freedom to change tools later, build in Webflow and connect HubSpot through its forms.

If the list points both ways, book a call and we’ll work through it with you.

Which platform fits which team

HubSpot’s details were checked against its knowledge base, developer docs, product catalogue and pricing page on 15 November 2026, and Webflow’s against its own documentation on 14 November 2026. Both vendors change their tiers and features, so check theirs before you commit.

Webflow or HubSpot?

Short answers, from the comparison above.

  1. It depends on how much the site needs the CRM. Webflow is usually the better pick when designers need to change layouts themselves, the content needs fields of its own, or you may leave HubSpot as a CRM one day. HubSpot is usually better when forms should write to the CRM with no connector and pages should change by contact record, source or device.

  2. Not automatically. A site built in HubSpot writes form entries straight to contact records, and on a higher tier its pages can change by CRM data. A Webflow site reaches the same CRM through embedded HubSpot forms or a tool such as Zapier. If personalised pages matter most, that favours HubSpot. If design and content structure matter more, Webflow with HubSpot connected is worth the setup.

  3. On Webflow, marketers change copy, images and collection items in a content role while the design stays locked, and designers change the layouts. Everyone who edits needs a Workspace seat. On HubSpot, marketers build pages in a drag-and-drop editor from modules in a theme that developers write, on Core Seats. View-only seats are free but can’t edit content.

  4. Webflow exports the site’s code on a paid Workspace plan and each collection as CSV. HubSpot exports pages, posts and templates as HTML on every plan, but the templates are written in HubL, HubSpot’s own template language. If you leave HubSpot altogether, HubSpot forms embedded on any site lose their paid features, so plan to replace them.

  5. Both can rank. HubSpot adds pages and posts to the sitemap itself, makes each new page canonical to itself, and lets you edit robots.txt on every plan. Structured data is hand-coded into a template or module. On Webflow you switch the sitemap on, enter a canonical URL, and on a paid plan fill in a schema markup field. HubSpot’s redirects tool needs a paid tier.

  6. By tier and by seat. Each Content Hub tier includes the CRM at the same level and a set number of Core Seats for people who edit, and you buy more as the team grows. HubSpot prices every Core Seat at the highest tier you hold in any hub. Webflow bills a Site plan for each site and Workspace seats on a separate bill.

  7. It is a rebuild. HubSpot ended its website migration service on 7 October 2026, and its website import brings in only each page’s title, URL, meta description and the navigation. Pages are built again in HubSpot. Blog posts can come in from a CSV file or through smart copy, up to 400 at a time, and Webflow exports each collection as CSV.

  8. Yes, in different ways. HubSpot keeps a version history for each page and post on every plan, and a restored version comes back as a draft. A deleted page has to be recovered by HubSpot Support. Webflow’s restore points take the whole site back at once, collection item IDs included. They are saved automatically as you work, and you can add your own.

Want a second opinion on your stack?

Tell us who will run the site and what it has to do. We’ll say which we’d pick, and why.

Most teams start with a call, then a sprint or an audit.

Book a call
  • Angus
  • James
  • Naiya
  • Lilian
  • Luca
  • Minh
  • Jorge
  • Toffee

The people you’d work with, from the first call to launch