Cookie Consent 4.2.0 is a free cookie banner script that runs from options in your code, with no account and no dashboard.

No, Cookie Consent alone does not make a site compliant with the General Data Protection Regulation (GDPR). Cookie Consent holds only the scripts you tag, so an untagged script runs before consent. It does not keep a consent log, and proof of consent comes from your own code. You decide the category of each script and write the Privacy Policy the Preferences Center links to. Check which rules apply to your site with Do I Need a Cookie Banner? EU, UK, and US Rules.

Yes, Cookie Consent works on any platform that lets you add code to every page, including Shopify, WordPress, Wix, Squarespace, and Webflow. The code is 2 script tags, plus any script you add in the optional step of the generator, with no plugin or app to install. Wix, Squarespace, and Webflow offer code on every page only on some paid plans, and Shopify needs a plan with the theme code editor.

Each platform adds tracking and sometimes a consent banner of its own, and each install guide says whether to turn that consent banner off or keep it. TermsFeed AutoTerms, a WordPress plugin, loads the same script through its Cookie Consent kit. Find the steps for your platform in Install a Cookie Banner on Any Website.

No, Cookie Consent shows the same consent banner to every visitor, wherever the visitor is. Cookie Consent does not detect a location or read an IP address. No option limits the consent banner to the European Union (EU), the United Kingdom (UK), or Switzerland. Express consent holds your optional tagged scripts by default for every visitor, including visitors in places where no law asks for consent. Check every limit of Cookie Consent in Limits of Free Cookie Consent: What It Does Not Do.

Set every Consent Mode signal to denied in the first script in <head>, after only the charset meta, load the Google tag untagged, and update the signals from the user_consent_saved callback. Cookie Consent does not send consent signals of its own, so your callback sends each one. Set user_consent_saved_on_page_load: true with the callback, because without it the callback skips later page loads of a visitor who answered. The callback runs before any tagged script and sends denied for each refused category. Follow the steps in Set Up Google Consent Mode v2.

Block a YouTube video with a placeholder that a tagged script replaces with the player after consent. Cookie Consent holds only <script> elements, so an <iframe> in your page loads at once. Keep the video address in a data- attribute of the placeholder, and let a script tagged with functionality swap in the player. Offer a button in the placeholder that opens the Preferences Center. Build the placeholder with Block YouTube Embeds Until Consent, and apply the same pattern to other iframes with Block Embeds and Iframes Until Consent.

Cookie Consent stores the answer for 365 days (12 months) by default, counted from the last time the cookies were written, and Safari keeps it for 7 days. Change the lifetime in whole days with the cookie_duration option. The answer sits in 3 first-party cookies in the browser, with no copy on a server. Visitors who answered keep their answer through any option change except demo, and through text edits in a self-hosted copy. The Safari limit applies to every cookie written by JavaScript. Read what each cookie holds in Consent Cookie Storage and Duration.

No, Cookie Consent does not delete cookies that other scripts set, whatever the visitor answers. A declined script that never ran did not set any cookie, so tagging before consent prevents the cookies. After a withdrawal, scripts that already ran keep running until the next page load, unless page_refresh_confirmation_buttons reloads the page. A Consent Mode denied sent from your user_consent_saved callback applies at once. From your own callback code, delete the first-party cookies your scripts set. Copy the cleanup callback from Rejecting Does Not Delete Cookies Already Set.

Change the wording of the Cookie Consent banner with a short script on your page, because no option changes the text. The only values you set that visitors see are website_name, above the Preferences Center title, and the 2 legal page addresses. The Preferences Center links the Privacy Policy, and the consent banner shows both links only with notice_banner_insert_legal_urls. Every other text comes from the translation of the chosen language. A modified copy does not get the updates and bug fixes TermsFeed ships at the hosted address, so TermsFeed does not recommend it. Copy the script that sets the title and the button labels from Change the Cookie Banner Text With Free Cookie Consent.

The Cookie Consent banner shows the language the language option sets, or, without the option, the browser language, then English. With the option set, the browser language plays no part, and an unsupported value gives English. Cookie Consent offers 36 languages, and Arabic and Hebrew read right to left. The language menu of the Preferences Center switches both the consent banner and the Preferences Center for the current page only. Find every language code in Cookie Banner Languages.

How does Cookie Consent affect page speed?

Cookie Consent adds 3 requests to www.termsfeed.com on each page load: the loader, the script, and a ping that carries the page hostname. The Cookie Consent script holds its styles and translations, so it does not load any stylesheet, font, or image. In express mode, an optional tagged script outside page_load_consent_levels loads only after the visitor accepts its category, so a visitor who declines never downloads it. The default headline layout sits in the page flow and pushes the content down, while the other 3 layouts float above the page. Pick a layout with Cookie Banner Layouts.

Close every private window, then test Cookie Consent in a new one with Chrome DevTools open, because a saved answer hides the consent banner. The checks assume express consent with page_load_consent_levels left out or at the generator value ["strictly-necessary"]. In the Network tab, filter for the host of an optional tagged script, such as googletagmanager.com for a tagged Google tag, then load your site. No request to that host appears before you answer, and the request appears after a click on the "I agree" button, without a reload. The Application tab then lists the 3 Cookie Consent cookies. Run the full installation checks with Check That Your Cookie Banner Works.

The TermsFeed generator writes the Cookie Consent code, and the script address in it, https://www.termsfeed.com/public/cookie-consent/4.2.0/cookie-consent.js, serves a small loader that loads cookie-consent-code.js from the same host. Read every request the loader makes in How the Cookie Consent loader works.

Run the browser checks of the troubleshooting section first, then contact TermsFeed with the details of your page. Most problems show in the browser console with the debug option on, in the Network tab, or in the Application tab cookies. Run those browser checks with Fix Cookie Banner Problems.

Collect these details before you write to TermsFeed, so that the answer does not wait for a second message.

  • The address of a page that shows the problem.
  • The Cookie Consent block of that page, with the options passed to run().
  • The console lines with debug: true turned on, from a private window.
  • The browser and device where the problem happens.

Leave passwords and the personal data of visitors out of the message. Send the message to the email support address that the TermsFeed contact page lists.