Cookie consent on WebflowNo banner included, so you bring your own
Reviewed · 5 sources
Webflow's cookie policy says it does not add any cookies to customer sites. A site with no analytics, no embeds and no custom code can therefore run without a banner.
Webflow also has no general consent banner. Its consent functions apply only to its own Analyze and Optimize products. For Google Analytics, ad pixels and anything else in custom code, you need a consent tool of your own.
Check your Webflow site
See every cookie it sets before consent, after Reject and after Accept.
What Webflow setsOn its own
Webflow's cookie policy states that it adds no cookies to customer sites. That policy dates from 2020, before Analyze and Optimize existed, and we could not confirm from official sources which cookies Webflow hosting sets today. Scan your published site to see what it really sets.
Built-in consent tools
A consent API for Analyze and Optimize only
Webflow's developer documentation is explicit: the consent functions (wf.getUserTrackingChoice(), wf.allowUserTracking(), wf.denyUserTracking()) apply only to Analyze and Optimize, and without those products you must set up your own banner or consent platform.
For Analyze and Optimize you choose a tracking default in the site's settings: always track, let visitors opt out, or don't track by default. In the EU the last one is the safe choice, combined with a banner that calls wf.allowUserTracking() after consent.
Where the cookies come fromThe ones that need consent
Webflow Analyze and Optimize
Webflow describes Analyze as using local storage instead of cookies. Storing or reading information on a visitor's device is covered by the ePrivacy Directive whatever the technology, so plan for consent here too.
Custom code and the Google integration
Google Analytics, Tag Manager and pixels added in site or page custom code load for every visitor unless a consent tool holds them back.
Embeds
YouTube and Vimeo videos, maps, forms and chat widgets placed with embed elements contact their providers on load.
Fonts and scripts from other hosts
Fonts or libraries loaded from a third-party host send each visitor's IP address to that host. Upload fonts to Webflow instead.
Make Webflow compliantIn 5 steps
- 1
List what the site loads
Scan the published site. Everything that is not Webflow hosting itself is something you added, and something you can gate or remove.
- 2
Add a consent tool
Use a consent platform or a Webflow consent app that blocks scripts until the visitor chooses. A banner built only from Webflow elements blocks nothing by itself.
- 3
Put every tag behind it
Load analytics and pixels through the consent tool or through Tag Manager with Consent Mode, not directly in custom code.
- 4
Set Analyze and Optimize to wait
Choose “Don't track by default” and call wf.allowUserTracking() from your banner's accept action.
- 5
Test on the live domain
Check the custom domain and the webflow.io staging address separately, then reject and confirm nothing is stored.
// Analyze / Optimize only, with tracking set to "Don't track by default".
// Call these from your consent banner.
function onAccept() {
wf.allowUserTracking();
}
function onReject() {
wf.denyUserTracking();
}These calls do not affect Google Analytics or any other script on the page.
Tools that help: tracking script blocker · Consent Mode v2 generator · cookie reference
Common mistakesOn Webflow sites
A banner made of a div and a button
It looks like a consent banner and blocks nothing. The scripts in custom code have already run.
Assuming “no cookies” means no consent
Local storage and similar technologies fall under the same ePrivacy rule as cookies.
Tags in page-level custom code
A tag added to one landing page is easy to forget and is missed by a homepage check.
Fonts loaded from Google
Custom code that links Google Fonts sends visitor IP addresses to Google. Use uploaded fonts.
Checklist for Webflow sites
- A consent tool that blocks scripts, not just a styled notice
- No analytics or pixel code loading directly from custom code
- Analyze and Optimize set to “Don't track by default”
- Fonts uploaded to Webflow, not linked from another host
- Video and map embeds load only after consent
- Reject tested on the published custom domain
QuestionsAnd short answers
- Does Webflow have a built-in cookie banner?
- Not a general one. Webflow provides consent functions for its own Analyze and Optimize products and states that, without them, you must set up your own consent banner or platform.
- Does a Webflow site set cookies by default?
- Webflow's cookie policy says it adds no cookies to customer sites. Cookies appear when you add analytics, embeds or custom code. Scan your published site to check, since that policy predates some newer Webflow features.
- Does Webflow Analyze need consent?
- Webflow says Analyze uses local storage rather than cookies. The ePrivacy Directive covers any storage of or access to information on the visitor's device, so the cautious setup in the EU is “Don't track by default” plus consent.
- How do I add Google Analytics to Webflow with consent?
- Load it through a consent tool, or through Google Tag Manager with Consent Mode defaults set to denied, so the tag does not set cookies until the visitor accepts.
Sources
- Webflow Developers: Site Tracking and Consent Management
- Webflow Cookie Policy
- Webflow University: Tracking & consent (Optimize)
- Webflow University: Analyze tracking, consent and privacy
- Webflow: Changes to analytics cookie behavior on webflow.io sites
Reviewed 20 November 2026 against Webflow's own documentation. Platforms change their cookies and consent features; follow the links for the current state. General information about EU cookie rules, not legal advice.
Other platformsAnd guides by industry
Check your Webflow siteSee what loads before consent
Free scan · every cookie before consent, after Reject and after Accept