Skip to main content

Comparison · SuperchargePerformance

Chrome Pop-Up Blocker vs Extensions: Do You Need One? (2026)

Chrome's pop-up blocker stops pop-up windows but not the cookie banner that reopens every visit. Find what each layer blocks and whether an extension helps.

4 min read Verified Chrome 158

A new window snaps open over your page and the thing you were reading is covered. The cookie banner you dismissed last time is already back. Chrome’s built-in pop-up blocker stops script-triggered pop-ups and redirects on by default. SuperchargePerformance, an extension, adds 195K+ blocking rules on top. Whether you need that layer depends on what’s interrupting you.

Key takeaways

  • Chrome’s built-in pop-up blocker stops script-triggered pop-ups and redirects on by default. Cookie banners and interstitials are inline, so they sit outside its scope.
  • The extension is a layer on top of the native filter, not a replacement. It blocks ads, trackers, and annoyances the built-in filter does not target.
  • The extension’s own pop-up blocker lives in Smart Page Cleanup, which is off by default, so nothing extra is running until you switch it on.

The built-in filter and its limits

Chrome blocks pop-ups automatically. When one is stopped, a “Pop-up blocked” chip appears in the address bar. The master switch lives at Settings → Privacy and security → Site settings → Pop-ups and redirects. From there you allow or block a site on its own, either through the chip’s “Always allow pop-ups and redirects from [site]” option or by adding a wildcard like [*.]example.com to the site list.

The filter’s scope is pop-ups and redirects, which are new windows a script opens. A cookie banner is not a new window. It is part of the page you are already on, so the filter never sees it. An interstitial that pushes over your content before you can reach it is in the same position. Notification prompts are a third system entirely, a separate permission the pop-up filter does not manage. If pop-ups keep appearing after you block them, the usual suspects are subscribed notifications or a malware entry point, per Chrome’s own troubleshooting page.

What the extension layer adds

The extension does not replace the native filter. It sits above it and keeps everything the browser already stops, then adds its own blocking on top. The engine behind that is 195K+ declarativeNetRequest rules packaged into the extension.

Content blocking runs at four levels: Off, Low, Med, and High. It is on by default at High, the maximum tier, which adds blocklists for malware and phishing sites on top of ads and trackers. Cookie-banner auto-reject is on by default. It is a low-risk reject that does not change the page layout, powered by DuckDuckGo AutoConsent and without EasyList filterlists.

The extension also has a dedicated pop-up blocker, separate from Chrome’s. It allows pop-ups that stay on the same domain and login or auth URLs (login, signin, oauth, sso, passport), and it blocks the cross-domain pop-ups everything else opens. That blocker is part of Smart Page Cleanup, and Smart Page Cleanup is off by default, so this part is not active until you switch it on.

Two guardrails keep the blocking from biting. A pop-up opened within two seconds of a real user click is allowed, so a checkout or payment flow that opens a window is not interrupted. Safe Mode is on by default and recovers pages that break under the feature injections. As of November 2026 the live build is version 1.5.6.

Built-in vs extension, side by side

LayerWhat it stopsWhere it livesNotable default
Chrome’s built-in filterScript-triggered pop-ups and redirectsSettings → Privacy and security → Site settings → Pop-ups and redirectsOn by default. Shows a “Pop-up blocked” chip. Per-site allow via the chip or a [*.]example.com wildcard
Extension (content blocking + pop-up blocker)Ads, trackers, annoyances (incl. cookie-banner auto-reject), plus cross-domain pop-ups inside Smart Page CleanupExtension popup. Content blocking on by default at High. Pop-up blocker inside Smart Page Cleanup (off by default)195K+ declarativeNetRequest rules. Cookie-banner auto-reject on by default. Checkout pop-ups within two seconds of a click are allowed. Safe Mode on by default

Where the built-in filter is enough

If the only thing interrupting you is a script-triggered pop-up window, the built-in filter already handles it. Leave the default on. When one specific site is the problem, the per-site allow list covers it without an extension.

Turning on the extension’s pop-up blocker

Smart Page Cleanup is off by default, so the extension’s own pop-up blocker is not running when you install the extension. Turn on Smart Page Cleanup in the extension’s popup. Once it is on, cross-domain pop-up blocking becomes active, same-domain pop-ups and login or auth URLs keep working, and a checkout window opened within two seconds of a real click is still allowed. If a page breaks after the switch, Safe Mode (on by default) recovers it. To exclude one site, the per-site toggle adds or removes the current site and reloads the tab, applying a full bypass for that site.

Which one, decided

If the pop-ups you see are only script-triggered windows, the built-in filter already covers them. Leave the default on and stop. If the nuisance is the cookie banner that returns every visit, or a cross-domain pop-up, the extension layer is the fix. Add it on top of the native filter. Cookie-banner auto-reject is on by default, so it works from the first page after you install. Turn on Smart Page Cleanup and the cross-domain pop-up blocking is live.

Frequently Asked Questions

Does Chrome have a built-in pop-up blocker?
Yes. Chrome blocks script-triggered pop-ups and redirects automatically, on by default, and shows a 'Pop-up blocked' chip in the address bar when it stops one. The setting lives at Settings → Privacy and security → Site settings → Pop-ups and redirects. As of November 2026 this is the behavior on Chrome stable, version 158.
Why does Chrome still let some pop-ups through?
The built-in filter only covers pop-ups and redirects, which are new windows a script opens. Inline cookie banners and interstitials are part of the page, not new windows, so the filter does not see them. Notification prompts are a separate permission system the filter does not manage.
Do I need an extension to stop cross-domain pop-ups?
SuperchargePerformance's own pop-up blocker blocks cross-domain pop-ups while allowing same-domain pop-ups and login or auth URLs. It is part of Smart Page Cleanup, which is off by default, so you must turn Smart Page Cleanup on. Cookie-banner auto-reject, on the other hand, is on by default and works from the first page after you install.
Will blocking pop-ups break my checkout?
SuperchargePerformance allows any pop-up opened within two seconds of a real user click, so checkout and payment flows keep working. If a page breaks after you enable Smart Page Cleanup, Safe Mode (on by default) recovers it.