How to Fix “This Page Has Been Blocked by an Extension” in Chrome

If Chrome just told you this page has been blocked by an extension, don’t panic — and don’t assume the website is broken. Nine times out of ten, the problem is in your browser, and the fix takes less than a minute.

Here’s how it usually happens: you click a link — a news article, a shopping page, a video — and instead of the page, Chrome shows a blank screen about an extension blocking it. Your internet is fine; every other tab works. So what changed? Almost always: nothing changed on the website. Something in your browser decided not to load it — usually an ad blocker doing its job a little too well.

I hit this exact error last year on a recipe site: one minute I was reading about sourdough, the next I was staring at a block page. The culprit was a privacy extension I’d installed months earlier and forgotten. It had updated its filter list overnight, and the new list flagged something. Two clicks later — pausing the extension for that site — the recipe was back. Total damage: ninety seconds and a mild sense of betrayal.

What “This Page Has Been Blocked by an Extension” Actually Means

The message means Chrome didn’t load the page — or part of it — because something on your side stopped the request. Underneath, the error code is usually ERR_BLOCKED_BY_CLIENT: Chrome’s way of saying the block happened inside your browser, before the request reached the website’s server, so the site never even saw you coming.

The usual suspect is an extension that filters network requests. Ad blockers are the best-known example — uBlock Origin, AdBlock, AdBlock Plus, AdGuard — but privacy tools like Privacy Badger and Ghostery do the same, as do some VPN extensions and antivirus browser shields. They work from filter lists: huge lists of addresses and patterns known for ads and tracking. When a page tries to load something matching a rule, the extension kills the request. Most of the time that’s exactly what you want. Sometimes the list is too aggressive, or the site changed something, and a harmless page gets caught in the net.

There are two versions. The first is the full-page block: Chrome replaces the whole page with the message, and nothing loads — usually a security, parental-control, or filtering extension refusing the main page. The second is quieter: the page loads, but an image, a video, or a button is missing, and the developer console shows a red line saying “Failed to load resource: net::ERR_BLOCKED_BY_CLIENT”. Same cause, smaller blast radius. Check the address bar: an address starting with chrome-extension:// means an extension built the block page itself.

The 30-Second Test: Open the Page in Incognito Mode

Before you change any settings, run this test. Thirty seconds, and you’ll know if an extension is the problem. It’s the fastest way to confirm this page has been blocked by an extension.

Press Ctrl+Shift+N (Windows) or Cmd+Shift+N (Mac) to open an Incognito window. Paste the same address in and press Enter. Chrome keeps extensions off in Incognito unless you specifically allowed them there — and most people never do. If the page loads fine in Incognito, an extension is the cause. Case closed — move on and find out which one.

If the page still doesn’t load in Incognito, the problem is probably something else: your antivirus web shield, a network filter, or a managed browser policy if the computer belongs to work or school. Skip ahead — the extension hunt won’t help you.

One more test: try the page in a different browser — Edge, Firefox, whatever you have. If it loads there, the problem is specific to Chrome and its extensions. If it fails everywhere, you’re looking at a network or security-software issue.

This test — the quickest way to confirm this page has been blocked by an extension — is the most useful diagnostic here, and the one most people skip. It turns a vague “the internet is broken” feeling into a definite answer in half a minute.

How to Fix “This Page Has Been Blocked by an Extension”: Find the Culprit

Once you’ve confirmed this page has been blocked by an extension, here’s how to find it.

Start with the usual suspects: type chrome://extensions in the address bar and press Enter. Start with ad blockers — uBlock Origin, AdBlock, AdBlock Plus, AdGuard — then privacy tools like Privacy Badger and Ghostery, then VPN extensions, then anything from your antivirus software. Toggle the first one off and reload the page. If it loads, you’ve found your culprit. If not, turn it back on and try the next one. Slow with twenty extensions, but most people find the answer within the first three. Also watch for extensions you don’t recognize — toolbars and coupon finders often arrive bundled with free software, and they filter traffic too.

Use the half-and-half trick if you have a lot of extensions: turn off the top half and reload. If the page loads, the culprit is in that half — turn them back on one at a time until the error returns. If it still doesn’t load, the culprit is in the half that’s still on. This binary search finds the answer in a handful of steps instead of twenty, and it’s the method support teams use when they’re in a hurry.

Check the developer console for proof: press F12 (or Ctrl+Shift+I on Windows, Cmd+Option+I on a Mac), click the Network tab, and reload the page. Blocked requests show up in red, with net::ERR_BLOCKED_BY_CLIENT as the status — proof the block is in your browser, not on the network. uBlock Origin has its own logger showing every request and which filter rule matched; open it from the dashboard. Seeing the exact rule that fired is deeply satisfying.

A jigsaw puzzle — finding which extension is behind the message this page has been blocked by an extension is a process of elimination

Allow the Site in Your Ad Blocker Instead of Turning It Off

Found the culprit? Good. Now don’t just switch it off and forget about it — that’s like removing your front door because the lock stuck once. The better fix is to allow that one site while keeping the blocker running everywhere else. Once allowlisted, you won’t see this page has been blocked by an extension again on that site.

In uBlock Origin, click the toolbar icon, then press the large power button. The site goes on your trusted list, and the blocker stops filtering it. Reload the page and it should load. You can manage the trusted list later from the dashboard if you change your mind.

In AdBlock or AdBlock Plus, click the icon and look for “Pause on this site” or “Don’t run on this site”. Same idea: the blocker stays on everywhere else, and this one site gets a pass. AdGuard has a similar toggle. The wording changes, but every major blocker has a per-site switch, because the developers know false positives happen.

You can also limit an extension’s reach from Chrome itself: go to chrome://extensions, click Details, and look at “Site access”. Set it to run only on chosen sites, or only when you click it. That’s a stronger fix if an extension keeps causing trouble where it has no business being — say, a coupon finder injecting itself into every page you visit.

Why allowlist instead of disabling? Because the extension is probably doing useful work on the other 99 percent of the web. Ad blockers stop trackers and malicious ads, not just the annoying ones. Turning one off entirely because it misfired once is a bad trade. Allow the site, keep the protection, move on.

When It’s Not an Extension at All

Sometimes the Incognito test rules out that this page has been blocked by an extension, and the page still won’t load. Here’s what to check next, roughly in order of likelihood.

Clear your cache and cookies: press Ctrl+Shift+Delete, set the range to “All time”, and clear cached images and files plus cookies. Then reload the page. A corrupted cached file can make a page fail in ways that look exactly like a block, and clearing it costs nothing. It’s the oldest fix in the book, and it still works embarrassingly often. Worried about logins? Clearing just the cached images and files — without the cookies — is usually enough.

Check your antivirus web shield: Avast, AVG, Norton, and others have a “web shield” that filters web traffic like an extension does. If a site is blocked in every browser, not just Chrome, this is a strong suspect. Open your antivirus settings, find the web shield, and either add the site to its exceptions or pause the shield for a few minutes to test. If the page loads with the shield off, you’ve found it — add the exception and turn the shield back on. Don’t leave it off.

Check whether your browser is managed: type chrome://management in the address bar. If it says your browser is managed by your organization, your employer or school controls which sites you can visit and which extensions run. You can’t override that. Same for chrome://policy — active policies there are doing the blocking. Talk to your IT admin. It’s their rule, and they’ll know whether the site is blocked on purpose.

Run a malware scan: malicious software can install extensions you didn’t ask for and block pages to steer you elsewhere. If extensions keep reappearing after you remove them, or the block hits sites you’d never expect — your bank, Google, Wikipedia — that’s a red flag. Run a full scan with your antivirus, and if it finds nothing, get a second opinion with the free version of Malwarebytes. Our guide on how to remove malware from Windows 11 walks through the cleanup. And if your connection is acting strangely, how to speed up Wi-Fi at home covers the network side.

Reset Chrome’s settings: if nothing else works, go to Settings, then Reset settings, then “Restore settings to their original defaults”. This switches all extensions off and resets your startup pages and search engine, without deleting bookmarks, history, or saved passwords. It’s the nuclear option — only use it after the simpler fixes fail, since you’ll need to turn your good extensions back on. Google’s help pages cover this: https://support.google.com/chrome/

A yellow warning sign — a visual reminder of the browser message this page has been blocked by an extension

Common Problems (and the Fix for Each)

“It only happens on one site.” That’s the classic false positive. An ad blocker rule is matching something there — often a script or an image with a name that looks like an ad. Allowlist the site and move on. If you’re the site’s owner, the fix is on your side: rename the resource so it doesn’t match common filter lists, and check your content security policy headers.

“It happens on every site.” That’s not a filter list problem — an extension or a security program is blocking everything. Try Incognito first. If it works, disable all extensions and re-enable them one at a time. If Incognito fails too, check your antivirus web shield and browser policies.

“Incognito doesn’t fix it either.” Then it’s not an extension at all. Work through the section above: clear the cache, check the antivirus shield, check chrome://management, run a malware scan. One of those four is almost always the answer. If all four come back clean, try a different network — your phone’s hotspot, for example. If the page loads there, your home network or router is filtering traffic.

“The extension keeps coming back after I remove it.” This is the one that worries me most. A legitimate extension stays removed when you remove it. If it reappears, something is reinstalling it — usually malware, or a management policy from work or school software. Check chrome://policy first. If a policy forces the extension, that’s your employer or school, and you can’t remove it yourself. If there’s no policy, run a full malware scan and check your installed programs for anything unfamiliar. An extension that reinstalls itself is not a browser quirk. It’s a problem.

“The page loads, but images and videos are missing.” Same cause, smaller symptom. An extension is blocking individual resources rather than the page itself. Open the developer console (F12), look for the red ERR_BLOCKED_BY_CLIENT lines, and allowlist the site. Nine times out of ten, it’s the same ad blocker you’d find with the full-page method.

Frequently Asked Questions

What does ERR_BLOCKED_BY_CLIENT mean?

It means something inside your browser stopped a request before it left your computer — usually an ad blocker, a privacy extension, or a built-in shield. That is exactly what happens when this page has been blocked by an extension. The request never reached the website’s server, so the site has no record of the visit and nothing it can do about it. The fix is on your side: find the extension and allow the site. It’s different from ERR_CONNECTION_REFUSED, which means the server itself couldn’t be reached — a server problem, not a browser one.

Is the site dangerous? Should I avoid it?

Not necessarily. This error says nothing about whether the site is safe — only that your browser blocked something on it. A filter list can flag a perfectly safe site because of one script or image name that looks like an ad. That said, don’t ignore every warning Chrome gives you. If it’s a site you’ve never heard of, stop and think. If it’s your bank, your email, or a site you’ve used for years, it’s almost certainly a false positive.

And if you use a VPN, make sure it’s trustworthy — see our guide to the best free VPN for USA 2026. Seeing this page has been blocked by an extension on a site you trust is almost always a false positive, not a warning about the site itself.

Will disabling my ad blocker let all the ads in?

Only if you disable it everywhere. That’s why allowlisting is the better fix: the blocker keeps working on every other site, and only the one site you trust gets a pass. Most blockers make this a two-click job. If you do disable an extension entirely, do it for a reason — not because one site misfired, but because it keeps causing problems.

Does this happen in Edge, Firefox, and Brave too?

Yes. Edge and Brave are built on the same Chromium engine as Chrome, so they show the same error and the same fixes apply — Edge uses edge://extensions instead of chrome://extensions, and Brave has its own built-in shield that can block pages the same way. Firefox shows a different message, but ad blockers there cause the same failures, and the Incognito test — Private Browsing in Firefox — works the same way. The method is the same everywhere: test in a private window, find the extension, allow the site. To lock down your browsing, how to set up two-factor authentication is a good next step. The same steps clear this page has been blocked by an extension in Edge and Brave too.

Your Quick Checklist

  • See the error? First test: open the page in Incognito (Ctrl+Shift+N).
  • Loads in Incognito? It’s an extension — open chrome://extensions.
  • Turn extensions off one at a time, starting with ad blockers.
  • Found it? Allowlist the site instead of disabling it.
  • Still blocked in Incognito? Clear cache, check antivirus shield, check chrome://management.
  • Extension keeps coming back? Run a malware scan and check chrome://policy.
  • Page loads but images are missing? Check the console (F12) for blocked requests.
  • Nothing works? Reset Chrome settings — and turn your good extensions back on after.

Leave a Comment

Your email address will not be published. Required fields are marked *

Scroll to Top