How to Add Cookie Consent Popup in Webflow Easily 2026

Inside the Webflow Designer, the left-hand rail has an Apps icon that opens a searchable panel of installable extensions, separate from the elements and layers panels you use for regular page building. A New & Noteworthy section surfaces apps like HubSpot, Google Ads for Webflow, and consent-management tools including OneTrust and Cookie Consent, so this is the natural starting point rather than trying to assemble compliance logic by hand.

Searching "cookie" surfaces several dedicated apps — Cookie Consent, Cookie Consent Hub, Flowstar GDPR Cookie Consent, and others. Clicking one opens its detail view with screenshots of the popup, an Install on site button, a like count, and a written breakdown of what it does: customizable appearance, user control over preferences, compliance features, and a read-only versus edit-and-read access permission listed under App permissions. Reading this panel before installing tells you exactly what the app can touch in your project.

Clicking Install on site adds the app to the current Webflow project. Unlike a purely visual element you'd drag onto the canvas, this app comes with its own configuration surface — you're installing a small piece of functionality plus a UI to control it, not just a styled div.

Once installed, the Cookie Consent app opens its own dialog directly over your page canvas, with tabs across the top for Settings, Scripts, Templates, License, Help, and Feedback. The Settings tab is where the real configuration happens: a Consent Storing Endpoint field for where consent data gets saved, a Consent Webhook Endpoint for real-time updates to your own server, and a Choose Regions to Show Popup field defaulting to Global.

A visible notice inside the settings panel warns that you need to activate the license before Save settings will actually take effect — the fields can be filled in, but without an active license the configuration won't persist. This is worth checking before you spend time filling in endpoints and region rules, since a free or trial install may only let you preview the app rather than fully save a working configuration.

The Choose Regions to Show Popup field lets you scope the banner instead of showing it to every visitor worldwide — useful if your compliance obligations are regional, such as GDPR for EU visitors, rather than global. Leaving it on Global (Default) is the safest starting point if you're not sure which regions legally require it for your traffic.

After saving your settings with an active license, publish the site and load it in a fresh or private browser session to confirm the popup actually appears for a new visitor and that accepting it prevents the banner from reappearing on a repeat visit. Testing from a clean session matters here, since your own browser may already have a stored consent choice from earlier testing.