Find a faulty extension without deleting all your add-ons
A controlled way to isolate blockers, password managers, theme extensions, and script modifiers.
Extensions have permission to change how some pages behave. That can be useful, but it also makes browser behavior harder to diagnose. Broken buttons, login pop-ups, distorted layouts, and unusual redirects can result from a conflict with an extension or from the website itself. Testing them in a repeatable order is better than removing every extension and hoping the problem disappears.
Change one extension at a time. Do not enter passwords on unverified pages or bypass browser security warnings.
Make the problem reproducible
Pick one URL, one account state, and one action that fails—for example, clicking “Upload file” opens nothing. Note whether the failure occurs on every website or only one. If the problem is intermittent, write down the approximate time and any other extension or browser update that preceded it. Avoid gathering private page data; the aim is to reproduce behavior, not collect sensitive content.
Use a clean or reduced-extension state
Try a guest profile or browser-supported troubleshooting mode. Firefox Troubleshoot Mode temporarily disables add-ons and several customizations; if the issue disappears there, you have narrowed the investigation, not proven which component caused it. Chrome or Edge users can test by turning off extensions temporarily. A private window might help, but extensions can be permitted there, so do not assume it is extension-free.
Re-enable one factor at a time
When reduced-extension mode works, restore extensions individually and retest the identical action. Start with those that modify content, block scripts, or fill forms, but do not assume a particular category is always responsible. Once you identify a conflict, check for an update and inspect site access permissions. Avoid disabling security protections globally; limit any adjustment to a trusted site and understand the trade-off.
Review the permissions you granted
An extension’s requested access matters as much as its functionality. An extension that reads all site content deserves more scrutiny than one that only modifies its own toolbar area. Remove tools you no longer recognize or use, especially if their publishers have changed. Install updates through official browser stores. Avoid downloading “fixed” extensions from links in unsolicited messages or search ads.
When disabling extensions does not help
If the failure persists in a clean profile and another browser, the site or network may be responsible. If only one regular browser profile fails, investigate profile settings and stored site data next. Do not reset your entire browser unless lower-impact diagnostics have failed and you understand what settings will change. Document the smallest working configuration for later comparison.
How this looks in practice
A spreadsheet web app suddenly refuses to download files after a privacy extension update. In a clean profile, the same workflow succeeds. Turning extensions back on one at a time reveals that a download-filtering rule is the trigger. The user adjusts the extension’s rule for the trusted app rather than disabling all protections, and confirms the workflow still works after restarting.
Your short checklist
- Reproduce a single failure consistently.
- Try guest/profile troubleshoot mode.
- Restore extensions one by one.
- Inspect permissions and update sources.
- Re-test the same site and action.
- Document the smallest change that fixed it.
Official documentation and verification
These publisher links support the browser behavior and instructions discussed above. BrowserSignal’s example cases are illustrative scenarios, not claims of hands-on vendor testing.
Menu labels, software versions and policies can change. If a device is managed by an employer or school, follow its instructions. Avoid sharing passwords, tokens, or private account details with support forums.
Use the interactive Pathfinder, then record what actually fixed the issue.