Webflow itself sets almost no cookies on published sites — but the analytics, marketing, and embed tools you add certainly do. Generate a cookie policy that covers what your site actually uses.
A published Webflow site is nearly cookie-free out of the box. In practice, almost every cookie on a Webflow site comes from tools added via custom code or embeds — and those are exactly the ones that need consent.
These are the tools most commonly added to Webflow sites via Project Settings → Custom Code or embed elements. Each one sets cookies that require consent from EU visitors before loading.
Website analytics
Advertising and retargeting
Heatmaps and session recording
Marketing automation and forms
Embedded video players
Embedded video players
From scan to full compliance in four steps.
Run PolicyForge's free cookie scanner on your Webflow site to see which of your integrations actually set cookies.
Use PolicyForge to generate a cookie policy that discloses each detected tool, its cookies, and their durations.
Create a new static page in the Pages panel, paste the policy into a Rich Text element, and link it from your footer.
Webflow has no built-in consent banner for visitors. Paste PolicyForge's banner embed into Project Settings → Custom Code (head) to block tracking scripts until visitors consent.
AI covers Webflow's cookies and your third-party tools. Ready in under 5 minutes.
No credit card required. GDPR, CCPA, and ePrivacy compliant.
What Webflow site owners need to know about cookie compliance.
Undisclosed cookies can trigger fines up to 20 million euros. Generate a compliant cookie policy in minutes — free to start.
Trusted by 10,000+ businesses