Chrome extensions stop working in several recognizably different ways, and which one you’re seeing matters. An extension that’s completely gone from the toolbar is different from one that’s there but does nothing when clicked, which is different from one that keeps reverting to disabled. Figuring out which category you’re in saves time before trying fixes. This fits into the wider topic we cover in our Google Chrome Errors.
The fastest universal test: disable and re-enable the broken extension. Go to chrome://extensions, toggle the extension off, wait five seconds, toggle it back on, then reload the page you were trying to use it on. This reinitializes the extension process and fixes a surprising number of “it stopped working” cases — particularly after Chrome updates where the extension’s background process didn’t restart cleanly.
Check Permissions First
Chrome became significantly stricter about extension permissions in recent years. An extension that previously worked without asking now needs explicit permission for each site. If an extension toolbar button appears but does nothing on a specific website, click the puzzle-piece icon in the toolbar, find the extension, click the three-dot menu next to it, and select “Manage extension.” Look at the “Site access” setting — if it’s set to “Ask,” you need to manually grant the extension access to the current site by clicking its icon while on the page and allowing access.
Also check the extension detail page for a “Why it can’t be turned on” message — Chrome sometimes disables an extension after detecting that it violated a policy, and the detail page will say so. This usually means the extension needs to be updated or reinstalled from the Chrome Web Store.
Extension Conflicts Are More Common Than You’d Think
Two extensions that both modify the same thing on a page — ad blockers, script injectors, dark mode tools, shopping assistants — frequently conflict with each other. The result is one or both extensions failing silently, behaving inconsistently, or breaking the page functionality they’re supposed to enhance.
The test: go to chrome://extensions and disable everything except the specific extension that’s not working. Reload the page. If the extension now works, something you disabled was conflicting. Re-enable other extensions one at a time until the conflict returns. Common conflict pairs: uBlock Origin + Privacy Badger (both intercept requests); multiple dark mode extensions active simultaneously; a VPN extension + a proxy extension; two password manager extensions.
Once the conflicting pair is identified, adjust one extension’s settings to give ground on whatever they’re competing over — usually which requests they block, or whether they have access to the same page elements.
Update or Reinstall the Extension
Extensions that worked fine and then suddenly stopped often did so because Chrome updated and the extension’s code is no longer compatible with the new Chrome APIs. Chrome updates happen automatically, but extension updates don’t always follow immediately. The extension developer may need a day or two to update after a major Chrome release.
Extensions update automatically by default, but you can force an immediate update: go to chrome://extensions → enable “Developer mode” in the top right → click “Update.” This triggers updates for all installed extensions immediately.
If updating doesn’t help, remove and reinstall from the Chrome Web Store. This gives you a clean install of the latest version without any cached state from the old installation that might be causing the issue. For paid or subscription extensions, contact the developer before reinstalling — some require reactivation after reinstall.
The Profile Corruption Fix
This is a less obvious fix but worth knowing about. Chrome stores extension data inside the user profile, and when the profile gets corrupted — after a hard shutdown, a failed Chrome update, or disk errors — extensions may fail to load, throw errors on specific sites, or lose their settings. The tell-tale sign: the extension worked in a different Chrome profile or on the same machine in a different user account.
Create a test profile: click the profile icon (top right) → Add → without signing in. Install the broken extension in the new profile and test it. If it works correctly there, your original profile’s extension data is corrupted. You can either continue using the new profile (syncing your bookmarks and passwords by signing into Google), or try repairing the old profile by resetting Chrome settings (Settings → Reset settings → Restore settings to their original defaults) and then reinstalling the extension.
Incognito and Guest Mode Behaviour
By default, extensions are disabled in Incognito mode. This is intentional — Incognito is supposed to be a clean, extension-free session. If an extension you need works in normal mode but not Incognito, go to the extension’s detail page (chrome://extensions → click Details on the extension) and enable “Allow in incognito.” Not all extensions support Incognito mode — some with persistent data or authentication requirements fundamentally don’t work in it.
Guest mode is stricter — no extensions work there at all, by design. That’s normal and expected.
Security Software Blocking Extension Scripts
Some enterprise antivirus and endpoint security products actively block extension behavior — particularly extensions that make network requests or inject scripts into pages. If extensions worked before a new security product was installed, or if they work on a home machine but not a work machine, endpoint security interference is the likely cause.
Temporarily disabling web protection in the security software and testing whether the extension works confirms this. On corporate managed devices, the fix belongs with IT — they can add Chrome extensions to the security product’s allowlist or adjust the policy for specific extension IDs.
When to Reset Chrome
If multiple extensions are failing simultaneously and none of the above has helped — not a conflict, not permissions, not a profile issue — Chrome’s core extension engine may have a configuration problem. Settings → Reset settings → Restore settings to their original defaults → Reset settings. This resets Chrome’s internal state including extension permissions and configuration without deleting bookmarks or passwords. After reset, reinstall the extensions that were failing and check whether they work with a clean configuration.
Our guide on Chrome freezing is worth reading if extensions returning to work still doesn’t stop Chrome from becoming unresponsive — extension conflicts are a common cause of Chrome freezing in addition to stopping individual extensions from working. For extensions that affect video playback specifically, our videos not playing guide covers the extension-specific video fixes in more detail. Chrome’s own extension developer documentation includes a troubleshooting section for users experiencing specific extension API failures, which is useful when an extension is partially working but failing on specific operations.
Chrome extension permissions system changed substantially in Chrome 112 and later releases, with the introduction of more granular “site access” controls. Extensions that previously had broad permissions (“read and change all data on websites you visit”) were transitioned to a per-site model where users must explicitly grant access on a site-by-site basis. Many users experienced previously working extensions suddenly appearing to “stop working” on specific sites after this change — the extension was still installed and enabled, but it no longer had permission to act on the current page. The fix is clicking the extension’s toolbar icon while on the affected page and selecting “Allow” when prompted for site access, or going to the extension’s detail page and changing “Site access” from “When you click the extension” or “On specific sites” to “On all sites” if you trust the extension broadly. This permission change affects particularly ad blockers, privacy tools, and productivity extensions that need to interact with page content to function.
Enterprise-deployed Chrome extensions — installed and managed through group policy rather than the Chrome Web Store — behave differently from user-installed extensions in several ways. They may be force-installed (can’t be removed), force-enabled (can’t be disabled), or configured with admin-controlled settings that override user preferences. If an enterprise extension stops working, the cause is often a change in the group policy configuration or an extension update that conflicts with the admin-configured settings rather than a Chrome-side problem. The chrome://policy page shows which extensions are managed by policy and what settings are enforced. Changes to enterprise extension behaviour are IT’s responsibility — attempting to fix managed extension issues through the standard user-facing troubleshooting steps often doesn’t work because the admin policy overrides the changes.
Chrome extensions that interact with native applications (native messaging extensions) have an additional failure mode: the native messaging host application may be missing or out of date. Extensions that connect to desktop applications — password managers like 1Password or Bitwarden that communicate with their desktop app, download managers, screen recording tools — use Chrome’s native messaging API to talk to a companion application installed on the operating system. When that companion application is uninstalled, not running, or out of date, the extension fails when it tries to communicate with it. The error in Chrome’s extension page or in the DevTools console usually says “Native messaging host not found” or similar. The fix is reinstalling or updating the companion desktop application rather than anything in Chrome itself.
Extensions accessing protected resources — PDF files, local file system paths, certain chrome:// pages — require specific permissions that must be explicitly granted. An extension designed to work with PDFs needs the “Access to file URLs” permission enabled in its detail page (chrome://extensions → Details → toggle “Allow access to file URLs”). Extensions that should work on chrome:// pages generally cannot do so without a specific permission that must be requested by the developer, so extensions failing specifically on Chrome’s own pages (New Tab page, Settings, Extensions page itself) are often just hitting a security boundary by design. Checking whether the failure is specific to those protected pages versus normal http/https pages narrows down whether it’s a permission issue or something else.
Chrome Sync can inadvertently break extensions across devices in a specific way. When Chrome sync includes extension settings and data, removing or modifying an extension on one device can affect how it appears on other synced devices. An extension deleted on a desktop and then re-installed on a laptop may come back with the settings from the deletion event rather than the current state. Similarly, if an extension’s settings get corrupted on one device and sync is enabled, the corruption can propagate to all other devices where Chrome is signed in. If extension problems appeared on multiple devices around the same time without each device independently having an issue, sync is spreading the corrupted state. Disabling extension sync (Settings → You and Google → Sync and Google services → Manage what you sync → Extensions) and letting each device manage its own extension state independently breaks the cross-device propagation of corrupted states.
The Chrome Web Store’s extension validation process means that extensions distributed outside the store — loaded as unpacked extensions or installed via CRX files — face additional restrictions in Chrome. Developer mode must be enabled for these to work, and Chrome periodically prompts users to disable non-store extensions as a security measure. If a non-store extension keeps getting disabled on Chrome startup, Chrome is actively trying to remove it because it doesn’t trust its source. The permanent solutions are either getting the extension published on the Chrome Web Store or using a Chrome variant like Chromium or an enterprise Chrome deployment that allows unverified extensions through policy. Repeatedly re-enabling a disabled non-store extension is a temporary workaround that Chrome will continue to undo.
Chrome’s extension debugging tools are genuinely useful for diagnosing extension failures that aren’t obvious from the user interface. Go to chrome://extensions, find the broken extension, and click the “background page” link (or “service worker” for Manifest V3 extensions) if it’s available. This opens a DevTools window specifically for that extension’s background process, showing any JavaScript errors, network failures, or console output from the extension’s background logic. Error messages here often pinpoint exactly why the extension is failing — a failed API call, a network request blocked by CORS, an undefined variable error after an update — which is far more useful than the vague “extension not working” description that arrives without this context. For extension developers or technically inclined users, this debugging approach can reveal actionable information in under a minute that would otherwise require hours of trial-and-error troubleshooting.
Manifest V2 to Manifest V3 migration is causing real extension disruptions that many users are experiencing without realizing why. Google is in the process of deprecating Manifest V2 extensions (the older extension API format) in favour of Manifest V3, which has stricter limitations on what extensions can do — particularly affecting how ad blockers and request-modifying extensions work. Extensions that haven’t been updated to Manifest V3 may stop functioning correctly in Chrome 127 and later, displaying warnings or reduced functionality without a clear explanation. If an extension you rely on suddenly became partially broken around a Chrome update and the extension hasn’t been updated on the Web Store in over a year, Manifest V2 deprecation is the likely cause. Check the extension’s Chrome Web Store page for recent updates and developer announcements — extensions still on V2 with no V3 version in development may need to be replaced with an alternative that has been updated to the current extension platform. Our guide on Chrome Extensions Slowing Down Your Browser covers an adjacent issue.
