How to Turn Off Pop Up Blocker in Edge: Four Routes, a Per-Site Exception, and the Menu Path Most Guides Miss

Microsoft Edge does not have a single "pop-up blocker" switch. It runs two separate systems: the standard blocker at edge://settings/content/popups, and a stronger one called Block Third-Party Cookies that quietly blocks scripted pop-ups before the main toggle ever sees them. If you flipped the visible switch and nothing changed, the second system is why. This guide covers the standard toggle, per-site exceptions, that cookie-level failure, Edge on Android and iOS, and how to turn the blocker back on when someone else's setting is suppressing your own.

The Edge Pop-Up Blocker Lives in Three Different Menus Depending on Your Version

The toggle sits in the same place on every Edge build from version 79 onward, but the route to it depends on which release you're running. Edge 79 shipped in January 2020 and moved the browser onto Chromium, which is when the current settings layout appeared. Anything older than that is the legacy EdgeHTML design and no longer receives updates.

The fastest route on current versions is to type edge://settings/content/popups into the address bar and press Enter. That bypasses the menu entirely and lands directly on the toggle. You can also paste edge://settings/content/popups into any new tab — Edge treats edge:// URLs as internal navigation, so no search engine interference.

If the toggle reads "Block" and a pop-up still fails to appear, you haven't found the problem yet. Skip ahead to the section on third-party cookie blocking. That is where most people get stuck.

Toggle the Pop-Up Setting Off in Seven Clicks

Here is the exact sequence on a current Edge build running on Windows 11 or macOS. The same route works on Linux and on Chrome OS.

1: Open Edge and press Alt + F on Windows or Cmd + , on macOS to open the Settings menu. Alternatively, open Settings from the three-dot menu. 2: Select Cookies and site permissions from the left sidebar. 3: Scroll to All permissions and click Pop-ups and redirects. 4: Find the blue toggle under Block and click it once — it will switch to the left and turn gray, showing the state as off. 5: Close the Settings tab. The change applies immediately, with no restart needed. 6: If the toggle was already gray before you clicked, the blocker was already off and something else is suppressing the pop-up. 7: If a page still blocks the window, the site is probably using a method that bypasses the toggle — usually a window.open() call triggered inside a user gesture. That path is governed by a separate permission, which the next section covers.

If you clicked the toggle and nothing appeared to change, refresh the page. Edge sometimes requires a reload before permission state is re-read. Chrome-based rendering does not hot-reload content settings.

Per-Site Exceptions Beat Global Toggling Every Time

Turning the blocker off globally means every advertising network on the web gets a free pass to open windows on your desktop. The per-site allow list lets you leave the blocker on for everything except the two or three sites you actually trust. You reach it from the same page used for the toggle.

Under Pop-ups and redirects there is a section labeled Allow, with a blue Add button. Click that, paste the site's full domain (for example bank.example.com), and press Add. The site now opens pop-ups and redirects, and every other domain on the web stays blocked. You can also use [*.]example.com to allow all subdomains of a domain.

The allow list honors wildcards. A single asterisk acts as a wildcard within one domain segment. The bracketed asterisk pattern [*.]domain.com covers every subdomain under that domain. If you're unsure which form to use, copy the address from the address bar exactly as it appears and paste it in — Edge will normalize it.

To remove an entry, open the same page, find the domain in the Allow list, click the three-dot menu beside it, and choose Remove. If a site starts behaving badly after you've added it, removing the exception is faster than chasing the reason.

The Hidden Failure: Third-Party Cookie Blocking Stops Pop-Ups Independently

Here is the part most tutorials skip. Edge's Block third-party cookies setting — found at edge://settings/content/cookies — suppresses scripted pop-ups on many sites regardless of the pop-up toggle status. This is not a bug. Any script that calls window.open() inside an onclick handler that runs from a site with a cookie policy conflict will not launch under this setting, because Edge treats the pop-up as an unauthorized resource load.

If you have the standard pop-up blocker off and the site still shows "Pop-up blocked," look at your cookie policy. In Edge 82 and later, the cookie setting has three named options: Allow, Block third-party cookies, and Block third-party cookies in InPrivate. The second and third both interfere with pop-ups on certain sites.

Test this quickly. Open edge://settings/content/cookies, switch the setting to Allow, refresh the site, and try the action again. If the pop-up now appears, you've confirmed the interaction. The trade-off is real — that setting exists for tracking protection, and turning it off globally weakens privacy across all sites.

The better fix for most people: leave cookies blocked globally and add the specific site to the cookie allow list on the same page. That keeps the tracking protection and restores the pop-up. The allow list is separate from the pop-up allow list, which is why adding the site in one place doesn't fix it in the other — an edge case that appears in user reports on Microsoft's own support forums going back to Edge 80.

Edge on Android and iOS Needs a Firewall-Level Setting You Can't Reach From the App

The desktop toggle does not exist on mobile Edge, and that surprises people. On Android, Edge relies on the system's per-app pop-up control combined with the app's own Tracking Prevention setting. On iOS, the same is true — pop-ups are governed by Safari-level restrictions applied system-wide, not by Edge's own settings.

On Android, open Edge, tap the three-dot menu, choose Settings, then Privacy and security, then Tracking prevention. Setting this to Basic reduces interference but does not remove all pop-up blocking. Adding a site to the Exceptions list under the same menu is the only per-site route on Android.

On iOS, Edge cannot override Safari's pop-up settings. Apple's WebKit engine governs all browsers on iPhone and iPad, so the setting lives in Settings → Safari → Block Pop-ups, and it applies to Edge too. That is a policy boundary set by Apple, not a bug in Edge.

A version-specific quirk: on Android Edge builds before version 100 (released April 2022), the Tracking prevention menu appeared under a different name — Privacy and security had a subsection called Site permissions. If you're on an older build, look there. The setting has not moved since, only the label.

The practical consequence is that you cannot turn off the pop-up blocker from within Edge on a phone the way you can on desktop. That is a genuine limitation worth knowing before you upgrade another browser.

Check What Edge Is Actually Blocking Before You Change Anything

Edge tracks blocked pop-ups per site and shows a small icon in the address bar when the blocker intervenes. On current builds, clicking the lock or tune icon to the left of the URL reveals a Pop-ups and redirects section with the current status and a direct link to the setting. This is faster than hunting the menu.

There is also a way to see blocked counts. Type edge://settings/content/popups and click the Allow list header — Edge displays the number of sites following the default block rule. That number doesn't tell you what was blocked, just how many domains honor the default. For deeper debugging, open DevTools (F12) and watch the Console. A blocked pop-up logs a warning that names the blocked URL. That is the only place Edge tells you which site tried to open the window.

If you're troubleshooting a specific site, load it with the pop-up blocker off once, and confirm the pop-up originates from that domain. Cross-domain pop-ups (an ad network serving through a different domain) require an exception on the origin domain, not the target. Misidentifying this is the most common reason a supposed fix fails.

Some browsers show a manual option in the blocked notification. Edge shows one too, but only after the first block on that site — the icon in the address bar gains a "Show pop-up" link for the session. That is a temporary allowance, not a permanent setting.

The Return Trip: Restoring Defaults and Cleaning Out Old Exceptions

If you've toggled the setting multiple times and want the default behavior back, the safe reset is the per-site allow list and redirect list, not the global toggle alone. Edge stores exceptions in a separate list that survives toggling. A site you allowed two years ago may still get free passage even with the blocker enabled.

To check: open edge://settings/content/popups, find the Allow list, and remove entries you don't recognize. The same page has a Block list for sites you've explicitly blocked regardless of the toggle. Clearing stale entries from both lists is the cleanest reset short of wiping Edge's profile.

For a full reset, Edge's Settings → Reset settings option restores all content settings including pop-ups to factory state. That route also wipes your default search engine, home page, and pinned tabs, so it is heavier than it needs to be for this problem alone.

Enterprise environments are the exception that surprises people. On a device managed by Microsoft Intune, Group Policy, or a mobile device management system, the pop-up setting is often locked. The toggle will be grayed out with a small enterprise icon beside it, and no amount of clicking changes it. Track down your IT administrator or check the policy file — the setting name is DefaultPopupsSetting in the administrative templates.

How to Turn the Blocker Back On When a Site Refuses to Open Windows

The reverse problem — the blocker is off and you want it on — is usually driven by a misclicked toggle or a malicious browser extension that flipped the setting. The clean fix has four checks, in order.

First, verify the toggle at edge://settings/content/popups shows Block in blue. Second, open edge://extensions and disable any extension you don't recognize, then reload the page. Extensions with tabs and windows permissions can and do change site content settings programmatically, and some ad-ware or "shopping assistant" plugins do exactly that.

Third, clear the site's own permission footprint. Click the lock icon beside the address bar, open Permissions for this site, and confirm pop-ups are set to Ask (default) or Block. This overrides the global setting either direction. Fourth, if the toggle is grayed out, check edge://policy for forced settings.

If it's still off after all four, the culprit is a managed profile. Sign out of the managed profile (usually labeled with your work email in the profile icon) and check again on a fresh profile. That's an edge case but a real one in BYOD workplaces.

Windows, Mac, and Linux All Share the Same Toggle — With One Exception

Edge runs the same Chromium settings underneath on Windows, macOS, and Linux, so the toggle, the allow list, and the cookie interaction behave identically. That consistency breaks in one place: Windows 10 and Windows 11 ship a system-level pop-up control in Settings → System → Notifications & actions, and it can close Edge pop-ups independently of the browser toggle.

On macOS, no such system-level pop-up control exists, but there is one macOS quirk worth knowing. The AppleScript Event and popen calls in system automation can be silently denied by Gatekeeper, producing a "blocked pop-up" notice when Edge itself never intercepted anything. That fits the broad pattern: the browser is blamed for a permission that belongs to the OS.

On Linux, where Edge is installed from Microsoft's signed repository, the toggle has no OS-level suppressor. If a pop-up fails, the browser is the culprit and the standard debugging route applies. That makes Linux the cleanest platform for isolating whether a problem is Edge or the OS.

FAQ

Does turning off the pop-up blocker in Edge turn off the ad blocker too?

No. The pop-up blocker and the ad blocker are separate systems in Edge. Edge's ad blocker lives in Settings → Privacy, search, and services → Tracking prevention and operates through the same content filter list engine. Turning off pop-ups does nothing to the ad blocker, and vice versa. The two can be configured independently across all sites and per-site exceptions.

Why does a pop-up still get blocked after I added the site to the allow list?

The allow list accepts only the exact origin that matches the site's registered domain, so a form hosted on a subdomain — apply.example.com when you added example.com — won't pass. Paste the exact hostname from the page's address bar, or use [*.]example.com to cover the subdomain tree. A related cause: 90% of the time the block notice names a different domain than the one you're looking at.

What is the difference between "Block" and "Ask (default)" for pop-ups?

The Ask option is the browser default that appears in per-site permissions, not the global setting. Globally, Edge only offers Block or Allow. Per-site, Ask means the site's own request for a pop-up opens a small prompt in the address bar instead of blocking outright. A user reported through Microsoft Answers described the per-site prompt as easy to miss, which is why many people hop to global toggling instead.

Can I turn off pop-ups for one website only in Edge?

Yes — the per-site allow list covered above is the correct route. Add the exact hostname under Pop-ups and redirects → Allow. Do not toggle the global setting. This leaves you protected on every other domain you visit.

Why is the pop-up setting grayed out in Edge?

A grayed-out toggle with a small enterprise icon means a policy is enforcing it from an administrator. Check edge://policy to see which policy file is applied, or ask your IT team. On a personal Windows device, a third-party security suite can install a policy and gray out the toggle — check your antivirus's browser protection module.

Do pop-up blockers in other browsers behave differently from Edge's?

Firefox ships a built-in pop-up blocker enabled by default, and its per-site exceptions work similarly to Edge's allow list. Safari's blocker is controlled in Safari's own settings and, on iOS, is the only setting that matters because Apple's WebKit engine governs all browsers. Brave routes pop-up behavior through its Shields system, which ties it to the site shield rather than a standalone toggle.

Which Edge version first introduced the current pop-up settings page?

Edge 79, released January 15, 2020, was the first Chromium-based release and introduced the current settings layout. Earlier EdgeHTML builds used Settings → View advanced settings → Block pop-ups under a different transfer path. The toggle behavior has not changed since Edge 79, only the labels and menu arrangement.

Turning off pop-ups in Edge is not complicated, but the second-line interference from third-party cookie settings and the mobile platform limits are why simple toggle guides fail in the field. Two settings at edge://settings/content control almost all of it. The fourth — the managed policy on a work device — is the one no tutorial can fix for you. For everything else, a per-site exception is faster, safer, and more privacy-preserving than flipping the global switch.