Framer vs Webflow: design-to-web

Framer says HIPAA in writing, and the word is no

Framer’s own documentation states that the product is “not currently designed to comply with HIPAA,” an explicit written refusal rather than a silent gap, and its certifications — SOC 2 Type 1 and 2, ISO 27001 — are reserved to Enterprise customers, whose Trust Center page is itself blocked from indexing. Webflow takes the same position through its Terms instead of a direct statement: no HIPAA compliance, health data forbidden by contract, no BAA at any tier. Scope compared, criterion by criterion. Checked 7 September 2026.

Book a call

Free Intro Call

Last Update:

2026

Framer

VS

Webflow

Framer vs Webflow: scope compared, criterion by criterion — checked September 7, 2026
Framer	Webflow
What the tool answers
What it measures or produces
Framer produces and hosts published websites — business sites, marketing sites, portfolios, directories and content sites — designed on a visual canvas and pushed live in one click.	Webflow produces websites structured across pages, branches, and locales, with CMS collections, assets, and generated HTML, CSS, and JavaScript that it then hosts.
The job it equips
The web designer — explicitly the Figma user inside a design or marketing team — who designs and ships without a handoff stage to engineering.	The Designer role, defined in Webflow's Workspace roles as the one who designs with all features, alongside the Marketer and Content editor roles.
What it cannot tell you
Code components can no longer reach CMS collections: Framer calls those properties a private implementation detail subject to change, closing off programmatic CMS reads from within rendering code.	Code export returns no CMS content, no ecommerce, and no user accounts: an exported site shows empty states on Collection lists.
Building and running the site
Editing model
A Figma-like open canvas: designs are imported then refined into responsive pages. The Content Editor role, billed 10 US dollars monthly, edits CMS, localization and on-page text.	Free visual canvas, no imposed theme: every action directly produces the published HTML/CSS. Templates are optional. A separate edit mode opens content to non-developers.
Dynamic content
Thirteen field types and up to thirty custom fields per collection. Free tier: 2 collections and 1,000 items. Basic tier: 10 collections and 2,500 items.	Site plan (USD/month): Starter free 50 items/20 collections; Basic has no CMS; Premium 20,000 items/40 collections; Team 100 collections. Sixteen field types, including reference and multi-reference.
Performance
AWS with a global edge network, anycast routing, pre-rendering at publish time. Framer publishes LCP of 1.1 seconds, INP of 95 milliseconds and CLS of 0.01.	Hosting and SSL included in every site plan, global CDN, 99.99% uptime claimed. Webflow publishes no quantified commitment on its own Core Web Vitals.
SEO settings
Sitemap.xml and robots.txt ship automatically. Titles, descriptions, canonicals and a full Open Graph set are editable; redirects live in site settings; structured data via JSON-LD.	Sitemap auto-regenerated on every publish, editable robots.txt, 301 redirects one by one or by CSV, self-referencing global canonical, native schema in the Pages panel, bound to CMS fields.
Multilingual
Native localization in subdirectories — /fr, /es-MX, /nl — never subdomains. Sold as an add-on at 20 US dollars per locale per month, up to 20 locales.	Webflow Localize is a paid add-on on top of the site plan: USD 9/month up to 3 locales, USD 29/month up to 10. Subdirectory URLs. Incompatible with ecommerce.
Access to the code
React 18 components authored in the built-in editor, plus custom code injection per page or site-wide. Site export is contradictory in the publisher's own docs — see criterion 4.	Export requires a paid Workspace plan, not a site plan. It delivers HTML/CSS/JS/images but excludes CMS, ecommerce, forms, search, localized content and password protection.
Traffic included
Bandwidth measured in gigabytes: 50 GB on Free, 100 GB on Basic, then 40 US dollars per 100 GB block up to 2 TB. Overage escalates over two months.	Site plan (USD/month, billed yearly): Starter 1 GB and 1,000 monthly visits; Basic 10 GB; Premium 50 GB, extendable up to 2.5 TB via paid add-ons.
What comes out of it
Export formats
SENSITIVE POINT — UNRESOLVED PUBLISHER CONTRADICTION. One help page denies any HTML export for self-hosting; another states published files can be downloaded at any time. Both pages are quoted below.	Site export as an archive of HTML, CSS, JavaScript, and assets, limited to paid Workspace plans; CSV export of a CMS Collection's content from the Designer.
Shareable reports
Built-in analytics tracks unique visitors, pageviews, bounce rate, sources and UTM tags; the unbilled Viewer role grants read-only access to every project in the workspace.	Webflow Analyze shows traffic dashboards covering ninety days; no report sharing or export function is described on the pages tested.
API access
The Server API updates and publishes a project from a server-side script. It is in beta and free; the announced future billing would be per-use with a monthly free allowance.	The REST Data API is included, capped at sixty requests per minute on Starter and Basic, one hundred twenty on CMS, eCommerce, and Business, plus one successful publish per minute.
What it connects to
Native integrations
Fourteen integrations are documented, with no publisher-stated total. The three that matter for a marketing site: Google Tag Manager, Google Analytics 4 and HubSpot forms.	No total app count is announced on the Apps page, which is organized into twenty-four categories; the three that matter: Google site tools, HubSpot, and Zapier.
Google tools it connects to
Google Tag Manager and Google Analytics 4 each have a dedicated integration article; the Analytics ID is entered in site settings rather than through custom code.	The Google site tools for Webflow App connects Google Analytics 4, Tag Manager, and Search Console to the site after Google account authentication and property selection.
Bringing your existing data across
Four documented paths from WordPress: CSV import after an XML/WXR export, a Chrome extension for visuals, manual rebuild, or programmatic sync through the Server API.	Content import via a CSV file of at most four megabytes; CSV exports from other content management systems such as WordPress are described as typically compatible with Webflow.
Getting started, and the fine print
Support
In-app product support with a 72-hour first response, 24 hours on the in-app channel. Enterprise adds Slack, Microsoft Teams and direct access to engineering.	Requests go through the support portal and chat with an AI Assistant then a Live Agent; no phone or video support except Enterprise customers. Hours and languages unpublished.
Where the data is hosted
United States. All Framer services are hosted in Amazon Web Services facilities located in the United States, spread across several physically separate availability zones.	Customer and end-user data is stored in the United States; the publishing infrastructure combines AWS with Cloudflare's global CDN.
What happens if you leave
Framer publishes a portability page tied to the EU Data Act: CMS content exports to CSV or JSON through plugins. The fate of the site files is contradictory — see criterion 4.	Canceling the Site plan removes custom domains and unpublishes the site from both its custom domains and the staging subdomain at the end of the current billing period.
Data residency and regulated cloud
Framer hosts on AWS in the United States, with no specific region named; its certifications (SOC 2 Type 1/2, ISO 27001) are reserved to Enterprise customers. Framer excludes HIPAA; its Trust Center is blocked by robots.txt.	Customer sites run on AWS plus Cloudflare, no region. Webflow isn't HIPAA-compliant and its Terms forbid health data; no BAA at any tier. FedRAMP, StateRAMP, GovCloud absent. Own certifications: SOC 2 Type II, ISO 27001, PCI DSS.
What it costs
The entry price and what it includes
Two separate charges. Basic site plan: 10 US dollars per month per site. Workspace seat: 20 US dollars per month per editor, always billed monthly.	The Basic SITE PLAN is fifteen US dollars per month billed yearly: custom domain, three hundred static pages, ten gigabytes of bandwidth, unlimited form submissions.
What pushes the bill up
Four overrunnable counters bill as add-ons: pages, CMS collections, CMS items and bandwidth. On top come 20 US dollars per locale per month, and every editor seat.	Workspace seats, billed on top of the Site plan: thirty-nine US dollars per full seat per month, fifteen dollars per limited seat, both billed yearly.
Sales tax and nexus
Framer adds US sales tax based on “your location” at checkout (via Stripe or Paddle.com), naming no state, no nexus and no tax-policy page; the contracting entity is Framer B.V. (Netherlands).	Webflow itself charges US sales tax based on billing address, at the local rate, across 25 states and D.C. (Alabama, Texas...). Templates are tax-exempt. Exemption needs a certificate; 501(c)(3) status alone isn't enough.
Procurement and invoicing
Net-30 named (“due 30 days from Framer's invoice”), in USD with 1.5%/month late interest; a PO is accepted but stripped of its own clauses. Only Enterprise opens non-card billing (bank transfer included), no published amount.	Non-card billing opens only at Enterprise (invoice or card, annual); below that, card only, invoices in USD. No ACH, wire transfer, or net-30 is named. A W-9 is provided on request; Enterprise terms: an unpublished Order Form.

Key takeaways

Framer writes its own HIPAA refusal down

Framer’s documentation does not stay silent on health data: it states plainly that the product is “not currently designed to comply with HIPAA.” That written refusal sits next to a narrower set of certifications than Webflow’s — SOC 2 Type 1 and Type 2, ISO 27001 — available only to Enterprise customers, whose dedicated Trust Center page is blocked from search engines by its own robots.txt file.

Webflow reaches the same refusal through its contract instead

Webflow never states outright that it fails HIPAA; its Terms simply forbid storing health data on the platform, and no tier offers a Business Associate Agreement. The certifications it does hold — SOC 2 Type II, ISO 27001, PCI DSS — belong to Webflow itself, not to a hosting partner, but none of them substitutes for the BAA that HIPAA requires.

Hosting sits in the United States on both sides, unnamed further

Framer hosts on Amazon Web Services facilities located in the United States, spread across several separate availability zones, with no specific region named. Webflow’s customer sites run on the same combination — Amazon Web Services plus Cloudflare’s content delivery network — again with no region stated. Neither one names FedRAMP, StateRAMP or a GovCloud option.

The invoice terms run in opposite directions

Framer names net-30 payment terms in writing, due thirty days from its own invoice, in US dollars, with one and a half percent monthly interest once late; a purchase order is accepted, though its own clauses are stripped out. Webflow, below Enterprise, publishes no purchase order, ACH, wire transfer or net-30 term at all, and accepts only a card; Enterprise terms for either vendor are unpublished, negotiated documents.

Sales tax lands on a different legal footing for each

Framer adds United States sales tax based on “your location” at checkout, collected through Stripe or Paddle.com, naming no state and no nexus, with the contracting entity itself registered abroad, as Framer B.V. in the Netherlands. Webflow collects its own sales tax directly, across twenty-five states and the District of Columbia, based on the billing address, with templates exempted and a certificate — not a 501(c)(3) letter alone — required for any exemption.

What the platforms still won’t export cleanly

Framer’s own help pages contradict each other on exporting a site: one denies any HTML export for self-hosting, another states published files can be downloaded at any time — a contradiction this comparison reports without resolving. Webflow’s export is unambiguous but narrower: an archive of HTML, CSS, JavaScript and assets, gated to a paid Workspace plan, that excludes CMS content, ecommerce, user accounts, forms, search and password protection.

Frequently asked questions

Can't find what you're looking for ? Contact us here

jordan@bulldozer-collective.com

Does Framer support HIPAA compliance for a regulated site?

No: Framer explicitly excludes HIPAA, and its Trust Center is blocked by robots.txt, with certifications such as SOC 2 Type 1/2 and ISO 27001 reserved to Enterprise customers. Webflow is not much better: it states it is not HIPAA-compliant either, its Terms forbid health data, and no BAA exists at any tier. For a buyer handling protected health information, neither tool is a fit.

In how many US states does Webflow charge sales tax, versus Framer’s disclosure?

Webflow charges US sales tax at the local rate across 25 states plus D.C., though templates themselves stay tax-exempt, and exemption requires a certificate since 501(c)(3) status alone is not enough. Framer, by contrast, adds US sales tax based on your location at checkout through Stripe or Paddle.com, but names no state, no nexus, and no tax-policy page at all. For a buyer needing a clear state list, Webflow publishes one and Framer does not.

Does Framer name net-30 payment terms in its invoicing policy?

Yes: Framer names net-30 explicitly, due 30 days from its invoice, in US dollars with 1.5 percent monthly late interest, and accepts a purchase order though it strips out the PO’s own clauses. Webflow names no such term: non-card billing opens only at Enterprise, invoice or card on an annual basis, with no ACH, wire transfer, or net-30 mentioned anywhere. For a buyer needing standard net-30 terms below an Enterprise deal, Framer states one and Webflow does not.