EU cookie banner requirements come from two laws read together: Article 5(3) of the ePrivacy Directive says you need consent before storing or reading non-essential cookies and similar trackers, and the GDPR defines what valid consent is. In practice that means no tracking before a choice, a "Reject all" option as easy as "Accept all", granular choices by purpose, no pre-ticked boxes, clear information about who sets what, and an easy way to change your mind later.

Below is a checklist you can test your banner against, with the regulatory decisions behind each point. It applies to EU and EEA visitors; the UK has relaxed some rules since February 2026, which we cover separately.

General information, not legal advice. National rules and regulator expectations vary, so check the guidance of the authority in each market you target.

The ePrivacy Directive is implemented differently in each Member State, for example Article 82 of the French data protection law and section 25 of Germany's TDDDG. Its consent requirement points to the GDPR standard: consent must be freely given, specific, informed and unambiguous, given by a clear affirmative action, and as easy to withdraw as to give.

Two things have not changed the position. The proposed ePrivacy Regulation, which was meant to replace the Directive, was withdrawn by the Commission in 2025. The Commission's Digital Omnibus package, published in November 2025, proposes moving cookie rules into the GDPR and reducing banner fatigue, but it is still going through the legislative process. Until anything is adopted and in force, today's rules apply. Track progress in our explainer on the Digital Omnibus cookie proposals.

The rules cover more than cookies. The EDPB's Guidelines 2/2023 on the technical scope of Article 5(3) confirm that tracking pixels, local storage, URL-based tracking and some IP-based techniques are caught too.

Non-essential cookies and trackers must not load until the visitor has agreed. This is the most common failure in audits and the easiest to test: open your site in a private window, don't touch the banner, and check developer tools for cookies and third-party requests.

The CNIL's €150 million fine against Shein in September 2025 included advertising cookies being placed as soon as a visitor arrived, before they could interact with the banner. Consent given afterwards does not cure tracking that has already happened.

Strictly necessary items (session, security, load balancing, the consent cookie itself, a shopping basket) can load immediately. Analytics generally cannot, except where a national regulator has a specific exemption, such as the CNIL's for narrowly configured audience measurement.

The reject all button requirement

EU law does not literally say "you must have a Reject all button". Regulators have interpreted the consent standard to mean refusal must be as easy as acceptance, and a reject option on the first layer is now the expected way to achieve that.

  • The CNIL fined Google €150 million and Facebook €60 million (decisions announced in January 2022) because refusing cookies took several clicks while accepting took one.
  • In January 2023 the EDPB's cookie banner taskforce reported that most authorities considered a first layer with no reject option, when there is an accept option, to be an infringement.
  • In September 2025 the CNIL fined Google entities €325 million in total, finding among other things that refusing personalised advertising cookies was harder than accepting them.

"Equal ease" also covers design. Making Accept a bright button and Reject a faint text link, or hiding Reject behind "More options", is the kind of deceptive design the taskforce flagged. For the wider dark-patterns rules, see our guide to dark patterns law in the EU.

Cookie banner checklist for EU visitors

RequirementWhat good looks likeCommon failure
Prior consentOnly strictly necessary items load before a choiceAnalytics or ad tags fire on page load
Accept / reject parity"Accept all" and "Reject all" on the first layer, same size and prominenceReject hidden in a second layer or styled as a link
GranularitySeparate choices per purpose (analytics, advertising, personalisation)One switch for everything except "essential"
No pre-ticked boxesAll optional purposes off until the user turns them onToggles defaulting to on
Clear informationPurposes in plain language; third parties named; link to cookie policyVague "to improve your experience" wording
No consent by browsingScrolling, closing the banner or continuing does not count"By using this site you accept cookies"
Legitimate interest not used for cookiesConsent is the basis for non-essential storagePre-enabled "legitimate interest" toggles
Easy withdrawalPersistent link or icon to reopen settings; withdrawal stops trackingNo way back once the banner closes
Accurate classificationOnly genuinely essential items marked essentialAd or affiliate scripts labelled "necessary"
RecordsTimestamped consent records and banner version historyNo evidence of what the user saw

Granularity in practice

Group cookies by purpose, not by vendor, and let users choose each purpose. Offer vendor-level detail in a second layer. If you use the IAB Transparency and Consent Framework, your CMP will present TCF purposes and vendors; the CJEU held in March 2024 (C-604/22) that the TCF consent string can be personal data, so treat the framework as a tool, not a compliance guarantee.

Withdrawal and re-prompting

Withdrawal must stop new tracking and, ideally, delete what was set. Shein's fine also covered cookies that kept being set after a user refused. Don't re-ask people who refused on every visit; the CNIL suggests remembering a refusal for a reasonable period, and many sites use six months.

What the banner should say

Informed consent depends on the words as much as the buttons. The Shein decision criticised banners that didn't explain advertising purposes in plain language and second layers that didn't identify the third parties placing cookies. A sound structure:

  • First layer: one or two sentences naming the main purposes (for example, measuring how the site is used, showing and measuring advertising, tracking which partner sent you), a note that partners are involved, and the three buttons: Accept all, Reject all, Manage choices.
  • Second layer: each purpose described in plain words with its own toggle, the list of vendors under each purpose and a link to your cookie policy.
  • Cookie policy: each cookie or tracker, who sets it, what it does and how long it lasts.

Hypothetical example of plain first-layer wording: "We and our partners use cookies to measure visits, show and measure ads, and track which sites we refer you to so we can earn commission. You can accept, reject or choose by purpose. You can change your mind at any time." Adapt it to what your site actually does; overclaiming or underclaiming are both problems.

A cookie wall blocks access to content unless the visitor accepts tracking. The EDPB's consent guidelines (05/2020) say consent obtained this way is not freely given. Some regulators take a more nuanced view of "pay or consent" models, where users can choose between accepting tracking and paying for a tracking-free version:

  • The CNIL assesses these case by case and has published criteria, including whether the paid alternative is real and reasonably priced.
  • The EDPB's Opinion 08/2024 found that large online platforms will usually struggle to rely on a simple pay-or-consent choice and should offer a free option with less or no behavioural advertising.

For a typical affiliate or adult content site, a hard cookie wall is high risk. If you are considering a paid tier as an alternative, take advice and check the guidance in each target country first.

The CNIL is the most active cookie enforcer in Europe and its guidance is the most detailed. Its main points align with the checklist above, plus a published exemption for audience measurement that meets strict conditions (single site, limited purpose, truncated IPs, 13-month cookie lifetime and 25-month data retention). Other differences to know:

  • Germany: the TDDDG requires consent for non-essential access to the device; there is no general analytics exemption, and German authorities expect refusal to be as easy as acceptance.
  • Spain: the AEPD's cookie guide expects reject options on the first layer.
  • Italy: the Garante's guidelines say closing the banner with the "X" should be treated as refusal.

If you serve several markets, build to the strictest common denominator rather than maintaining many variants.

A consent management platform (CMP) makes most of this manageable: script blocking, geo-targeting, records, TCF support and integration with Google's Consent Mode. If you serve Google ads in the EEA or UK, Google requires a Google-certified CMP that integrates with the TCF. Read our guides to choosing a consent management platform and Google Consent Mode v2, and compare providers in our software and services directory.

Test like a regulator: on desktop and mobile, try to reject everything in one click, then confirm in developer tools that no advertising or analytics requests are sent. Then reopen the settings and withdraw consent after accepting. Screenshot each step and keep it with your records.

Frequently asked questions

Is a "Reject all" button legally required in the EU?

The law requires refusal to be as easy as acceptance. Regulators, including the CNIL and most authorities in the EDPB's taskforce, treat a first layer with "Accept all" but no equivalent reject option as non-compliant, so in practice you should have one.

Do I need consent for analytics cookies in the EU?

Generally yes. A few authorities, notably the CNIL, accept narrowly configured audience measurement without consent if strict conditions are met. Most popular analytics tools in their default setup don't meet those conditions.

How long can I keep a user's consent?

The law doesn't fix a period. Many regulators and sites re-ask after six to thirteen months, or sooner if your purposes or vendors change significantly. Keep records showing when and how consent was given.

Has the ePrivacy Regulation replaced the Directive?

No. The Regulation was withdrawn in 2025. The Directive, as implemented nationally, still applies, and the Digital Omnibus cookie changes are only proposals.

Next steps

Run the regulator-style test above, fix anything that fires before consent and make sure Reject all sits next to Accept all. Then pick or reconfigure a CMP that handles geo-targeting for UK and EU rules. More guides are in our GDPR and cookies section.