Consent management for Webflow
A cookie banner for your Webflow site, published for you. Connect the site once and Consent Studio puts the banner live; after that its text, colours and categories change the moment you save them. No custom code to paste, and nothing to republish.
- One-click install
- Stays up to date
- Works with Webflow Analytics
From €10 a month. No credit card, no per-visitor billing.
A cookie banner that works with Webflow
Two separate things, and both matter: how the banner reaches your site, and what happens to Webflow’s own tracking once it is there.
We publish it for you
Authorise Consent Studio once and we register the banner as a script on your site through the Webflow API. When that installed script has to change, we push the new one the same way, so you never go back into Custom Code to swap it by hand.
- Connect once
- Recommended
Webflow Analytics Consent API
Webflow’s built-in analytics stays off until a visitor grants analytics consent, then activates through Webflow’s own API. Separate from the install, and worth switching on either way.
- Built in
- No code
Your own embeds and pixels
Embeds, pixels and scripts you added yourself can be held back too. You mark them in your Custom Code with the category they belong to, and the banner releases them only once a visitor grants it, so the page is governed past the parts Webflow knows about.
- Third-party embeds
Serving California as well as the EU?
The GDPR and the CCPA ask for opposite defaults, and a banner built for one of them quietly gets the other wrong.
Opposite defaults, one banner
The GDPR wants marketing denied until a visitor agrees. The CCPA runs the other way, as an opt-out. Region rules give each visitor the right starting state, so one banner answers both without a second install for the US.
Global Privacy Control is respected
California treats a browser opt-out signal as a request you have to honour. Consent Studio reads GPC and can apply it before the banner is ever shown, on every plan.
One record, both regimes
Whichever default a region gets, the decision goes into the same consent log. There is nothing separate to keep in step when an auditor asks for one history.
One answer controls every tool on your site
A banner that only governs the platform leaves everything you added on top of it running. Consent Studio speaks to the tools around it as well, and by default holds anything it does not recognise until the visitor says otherwise.
Discover All Integrations
Choose how to install the cookie banner
Every route ends with the same banner and the same consent record. Pick the one that fits how your site is built.
Automatic install
Recommended RouteAuthorise Consent Studio with your Webflow account, pick the site, and we publish the banner through the Webflow API. When the installed script itself has to change, we push that for you too.
- Connect once
- Stays up to date
Direct code
Prefer to keep everything in Webflow? Paste the snippet into Site Settings, Custom Code, Head. You publish the site yourself, and you update the snippet yourself when settings change.
- Full control
- No dependencies
How to set up cookie consent for Webflow
The connected route is four steps and no code. Nothing here happens in the Designer, and nothing here touches your layout.
Add your site
Create the site in Consent Studio and the banner is generated for your domain, with your categories, languages and styling already in it. It is served from consent.studio rather than a third-party CDN, which matters more on Webflow than most places: a Webflow site that was otherwise clean should not pick up an external origin at the moment it becomes compliant.
Connect Webflow
Authorise Consent Studio from your Webflow account and pick which site this banner belongs to. The authorisation covers reading and publishing your sites and reading and writing custom code, and you can revoke it from Webflow whenever you like. It never asks for access to your CMS collections or your form submissions, so those cannot be read even by accident.
Publish
We register the script with Webflow and apply it to the site, then you publish in Webflow and the banner is live. After that the banner itself is served from consent.studio, so text, colours and categories are live the moment you save them and nothing has to be republished. The connection is what keeps the installed script current when that changes, which is the part people forget on a pasted snippet.
Switch on Webflow Analytics
Open Web CMP, go to Integrations and enable Webflow Analytics. This is the one that gets forgotten, because Webflow Analytics is first-party and nobody added it deliberately, but it is still measurement and it still needs a legal basis. With the integration on it reads the Webflow Analytics Consent API and waits for analytics consent like every other tag on the site.
A cookie banner alone is not enough
Most sites are leaking before anyone notices. Not through malice, but through a tag somebody added in a hurry, a vendor that changed its script, a plugin that phones home.
- Unconsented tracking
- Unwanted overseas transfers
- Consent records you cannot produce
- Scripts you never approved
The Full Consent Stack.
Three products, one consent record. What a visitor agreed to in the banner is what every downstream tag sees.
Which plan Webflow needs, and why
Essential covers the whole of this page. Professional is aimed at people who build Webflow sites for other people.
Essential is enough
€10/month
- The Webflow integration and the connected route
- Published for you, with nothing to republish
- Unlimited pages, 200,000 consent actions a month
What Professional adds
€36/month
Worth it once a site publishes often, or belongs to a client.
- More depth: HTTP consent cookies, accessibility, re-prompting
- On-demand scans, right after a publish
- Sitemap scanning, for CMS collection pages
- Unlimited collaborators, Essential includes two
Every plan includes
Trusted by organisations that care about privacy
Frequently asked questions about Webflow
Does Webflow have a built-in cookie banner?
No. Webflow provides a cookie consent component in some templates and a place to paste custom code, but it does not ship a Consent Management Platform. It does not block third-party embeds, record consent, or produce the log an audit asks for.
Does Webflow Analytics need cookie consent?
Yes, in the EU. Webflow Analytics collects visitor data on your behalf, which makes it analytics rather than strictly necessary, so it needs consent before it runs. Consent Studio holds it back and activates it through the Webflow Analytics Consent API once a visitor agrees.
How do I add a cookie banner to a Webflow site?
Either connect your Webflow account to Consent Studio and let it publish the banner for you, or paste the snippet into Site Settings, Custom Code, Head. The connected route also keeps the banner current when you change settings later.
Do I have to republish my Webflow site after changing the banner?
Not for banner settings. The banner is served from consent.studio, so text, styling and category changes are live as soon as you save them, with nothing to republish. Consent Studio only pushes through the Webflow API when the installed script itself changes. Structural changes you make in Webflow still need publishing as usual.
Get Started with the Full Consent Stack
Everything you need in one bundle. Consent Studio provides you with a consent banner, scanner and client-side tag manager that guarantees no data ever gets transferred overseas.
Read the documentation
Our help center walks through every integration, plugin and template step by step, with screenshots. It is written and kept current by the people who build Consent Studio.