Auto-reject non-essential cookies, hide consent popups, block Google login nags and notification prompts
Users
9
+1 in 30 days
Rating
0.0 / 5
unchanged in 30 days
Ratings
0
0 in 30 days
Store rank
#203K
#170K among extensions
Version
1.0.0
updated 19 Apr 2026
Users
monthly, 6 months
Latest, 16 Oct 2026:9 usersMove the mouse over the chart for any month
Ratings count
monthly, 6 months
Latest, 16 Oct 2026:0 ratingsMove the mouse over the chart for any month
The Chrome Web Store rounds user counts down to the leading digit, so the user line moves in steps. The ratings count is exact and is the better signal of real adoption.
About Cookie Cutter
Tired of clicking "Reject All" on every website? Cookie Cutter handles it for you.
What it does:
Cookie Cutter automatically handles cookie consent popups using a 3-tier strategy:
1. Calls the website's own consent API to reject non-essential cookies — supporting all major consent management
platforms and the industry-standard IAB TCF v2 framework
2. Finds and clicks "Reject All" or "Necessary Only" buttons — in 9 languages
3. If it can't safely reject, it hides the popup so you can browse in peace
It never accepts all cookies. It always chooses the minimum necessary option.
Extra blockers (opt-in):
- Block "Sign in with Google" One Tap prompts
- Block "Allow notifications?" permission requests
These are off by default — enable them in the popup if you want them.
Features:
- Works on all websites automatically
- Supports 20+ cookie consent platforms
- Detects popups in 9 languages (EN, DE, FR, ES, IT, NL, PT, PL, SV)
- Per-site overrides — disable on specific sites
- Activity log — see what was blocked and where
- Three modes: Reject All, Hide Only, Ask Me
- Manifest V3 — modern, efficient, privacy-respecting
- No data collection, no analytics, no tracking
- Fully open source
How it works:
Cookie Cutter injects a tiny content script on each page that checks for known cookie consent platforms. If it finds
one, it calls the platform's own JavaScript API to reject non-essential cookies — the cleanest possible approach. For
platforms without an API, it finds and clicks the reject button. As a last resort, it hides the popup via CSS.
The extension badge shows you what happened:
- Green ✓ = cookies rejected
- Blue — = popup hidden
- Yellow ! = cookie wall detected (site requires cookies)