How to Disable the Popup Blocker in Chrome (And When You Should)

Chrome's built-in popup blocker does a solid job keeping unwanted ads and redirect storms off your screen. But occasionally, it catches something legitimate — a payment gateway, a document viewer, a work portal — and blocks it outright. Knowing how to turn it off, either globally or for specific sites, gives you back that control without compromising your security posture more than necessary.

What Chrome's Popup Blocker Actually Does

Chrome blocks popups by default, and has for years. When a site tries to open a new window or tab without a direct user action, Chrome intercepts that request and shows a small icon in the address bar instead of opening the window.

This covers two main behaviors:

• Popups — new browser windows or tabs triggered by a site's script
• Redirects — automatic page changes that send you somewhere you didn't ask to go

Chrome handles these separately in its settings. You can block one without touching the other. Most users only need to adjust one of them, and usually only for a specific site rather than the whole browser.

Two Ways to Disable the Popup Blocker in Chrome

Option 1: Allow Popups for a Specific Site (Recommended)

This is the targeted approach — you're telling Chrome to trust one domain without opening the door everywhere.

1. Open Chrome and visit the site where popups are being blocked
2. Click the padlock icon (or info icon) to the left of the URL in the address bar
3. Select Site settings from the dropdown
4. Scroll to Pop-ups and redirects
5. Change the setting from Block to Allow
6. Reload the page

The change applies only to that site. Every other site on the web stays blocked. This is the cleanest way to handle a legitimate site that needs popup access — an online banking portal, a school's learning management system, or a file-export tool.

Option 2: Disable the Popup Blocker Globally

This turns off popup blocking across all sites. It's rarely necessary, but some users in specialized environments (internal tools, local development, kiosk setups) find it useful.

1. Open Chrome and click the three-dot menu (⋮) in the top-right corner
2. Go to Settings
3. Click Privacy and security in the left sidebar
4. Select Site settings
5. Scroll down to Content and click Pop-ups and redirects
6. Toggle from Sites can't send pop-ups or use redirects to Sites can send pop-ups and use redirects

🔓 Once this is set globally, every site you visit can open popups. This meaningfully increases your exposure to aggressive ad behavior and redirect chains, so it's worth understanding the tradeoff before making the change.

Managing Exceptions Without Fully Disabling Anything

Chrome's site settings let you build a granular exception list. Instead of toggling a global switch, you can add specific sites to an Allow list while keeping everything else blocked.

In the same Pop-ups and redirects settings page (Settings → Privacy and security → Site settings → Pop-ups and redirects), there's an Allow section where you can paste in site URLs directly — without even visiting them first. This is useful for IT administrators setting up managed devices or for users who know in advance which sites need access.

The format typically looks like: [*.]example.com to cover all subdomains, or https://app.example.com for a specific page.

Why Popups Get Blocked in the First Place

Chrome's algorithm flags a popup when it's triggered without a direct, traceable user gesture — like a click or keypress. Sites that open windows in response to page load events, timers, or scroll triggers get caught by this logic, even when the popup itself is something useful.

That's why some legitimate tools trip the blocker:

• PDF or file preview windows opened by a button click that routes through a redirect first
• OAuth authentication flows (logging in with Google/Facebook) that open a small verification window
• Payment processors that launch a secure checkout window
• Help chat widgets that open in a separate tab

In each case, Chrome sees a script-triggered window and blocks it — not because the content is harmful, but because the trigger pattern matches how spam popups behave.

Variables That Affect How This Works for You

Not everyone's Chrome setup behaves identically. A few factors shape the experience:

🔍 If you disable Chrome's popup blocker and popups are still being blocked, check your installed extensions. A separate extension may be the one doing the blocking.

The Difference Between Chrome's Native Blocker and Extension-Based Blockers

This distinction trips people up regularly. Chrome's built-in popup setting and extensions like uBlock Origin are separate systems. One doesn't control the other.

• Chrome's native setting handles browser-level popup interception
• Extensions apply their own rule sets, often more aggressively, and some specifically target scripts that attempt to open new windows

If you've allowed popups through Chrome's settings and they're still not appearing, the next step is checking your extensions individually — usually by disabling them one at a time to find which is responsible.

What "Allowing" Popups Actually Risks

Globally disabling the blocker removes a layer of defense that works silently in your favor every day. Many ad networks, malicious redirects, and phishing setups rely on popup chains to move users where they want them.

The per-site approach sidesteps this problem entirely. Whether that level of precision fits your workflow, or whether you're working in an environment where a global toggle is the practical choice, depends entirely on how you use Chrome and what sites you're dealing with daily.