How to Disable a Chrome Extension on One Website (2026)

Right-click the extension’s toolbar icon, choose “This can read and change site data,” then pick “When you click the extension.” That turns the extension off on the site you’re currently viewing while leaving it fully active on every other tab. No uninstall and no lost settings, in about 10 seconds. Menu labels described here match Chrome 151 (August 2026).

Turn Off the Extension on Just This Site

1. Go to the site that’s misbehaving, the one the extension is interfering with.
2. Right-click the extension’s icon in the toolbar. If it’s hidden, click the puzzle-piece icon first, then the three-dot menu next to the extension’s name.
3. Choose “This can read and change site data.” A submenu opens with three options.
4. Select “When you click the extension.” This is the site-scoped setting, not a global one, so it only applies to the domain you were on when you opened the menu.
5. Reload the page.

The extension’s content scripts stop firing on that domain. Every other site keeps whatever access level it already had. If the extension has a companion popup or side panel, that stays reachable too, since only automatic page injection was switched off.

Why This Beats Uninstalling

Uninstalling throws away saved settings, whitelist entries, and any paid state tied to that install ID. It also solves a problem you may not actually have: if only one site is broken, the extension is probably fine everywhere else, and the conflict is specific to something on that page (a script it injects, a DOM change it makes, a resource it blocks).

Reinstalling later, if the same extension turns out to work fine, means redoing every setting from scratch. A site-level exception is reversible in one click and costs you nothing while you figure out whether the extension is actually the problem.

What the Three Site-Access Levels Actually Do

Not every extension exposes all three; it depends on what the manifest requests.

If you don’t see this submenu at all for a given extension, it’s built on activeTab rather than broad host permissions, meaning it already only runs when clicked and there’s nothing broader to restrict. Manifest V3’s permission model pushed more extensions toward exactly this narrower default.

When Per-Site Disabling Isn’t the Real Fix

Some extensions need broad access to function at all, not because they’re poorly built but because of what the feature does. A volume booster injecting audio into the page is the clearest example: the permission reflects the API it uses, not how many sites it’s misbehaving on. Turning it off on one broken site doesn’t change that it still needs that access on the sites where you want the feature.

Site-level toggles also won’t help if an update broke something globally rather than on one domain. Extensions sometimes get disabled outright after a Chrome or extension update, which shows up as the extension missing everywhere, not misbehaving on one page. That’s a different problem with a different fix.

If the Site Still Breaks, Then What

If turning off site access fixes the page: leave it there. You’ve isolated the conflict without losing the extension anywhere else.

If the page is still broken after reloading with the extension off on that domain, the extension wasn’t the cause, so check for a stale cache, a blocked resource, or a site-side bug instead.

If you find yourself disabling the same extension on site after site, that’s a sign the extension’s default behavior doesn’t fit how you browse, and swapping it for one with narrower defaults (or one that lets you whitelist instead of blacklist) will save more time than toggling it repeatedly.