Firefox Add-On Workarounds: Install & Remove

If Firefox blocks an add-on installation or an extension won’t remove, the workarounds involve using the official Mozilla Add-ons (AMO) site, enabling legacy extension support in the about:config settings, or manually deleting the extension’s files from your Firefox profile folder. For removal issues, the fix typically involves restarting Firefox in Troubleshoot Mode or clearing the startup cache.

Why Firefox Restricts Add-Ons

Mozilla has progressively locked down add-on installation to protect users from malicious or poorly coded extensions. Since Firefox 40, the browser only allows extensions that have been reviewed and signed by Mozilla. This means you cannot simply download a .xpi file from an arbitrary website and drag it into the browser window; Firefox will reject it with a message stating the add-on could not be verified. This is a security measure designed to prevent malware from hijacking your browser, but it also blocks legitimate, niche extensions that developers have not submitted for review.

Additionally, Firefox has moved to the WebExtensions API, which is a standardized system that limits what an add-on can do. This broke thousands of older extensions that relied on the legacy XUL/XPCOM framework. When you try to install an outdated add-on, Firefox often refuses it because the code is incompatible with the current browser engine.

The Official Workaround: Using about:config

For users who need a specific extension that is unsigned or uses legacy code, the most common workaround is to disable the signing requirement. This is done through the hidden configuration menu.

1. Type about:config in the address bar and press Enter. Click the button that accepts the risk.
2. In the search bar at the top, type xpinstall.signatures.required.
3. Double-click the preference to change its value from true to false.
4. Restart Firefox completely.

After this change, you can install unsigned add-ons by downloading the .xpi file and dragging it into the browser window. However, this only works for extensions that are still compatible with the WebExtensions API. For truly legacy extensions that use old code, you will also need to set extensions.legacy.enabled to true in the same menu. Note that Mozilla only guarantees this works on the ESR (Extended Support Release) and Developer Edition channels; the standard release channel may ignore these flags in newer versions.

Installing from a Local .xpi File

If you have a downloaded add-on file (with the .xpi extension) that you have verified is safe, you can install it directly. The simplest method is to open the file with Firefox. Navigate to the file in your Downloads folder, right-click it, and select “Open With” then choose Firefox. Alternatively, you can drag the file from your file manager directly into an open Firefox window. If the browser blocks it, check the address bar—Firefox often displays a shield icon or a notification that says “Firefox prevented an unverified add-on from installing.” Click that icon and select “Allow” to proceed.

Another method involves using the Add-ons Manager. Open the menu (the hamburger icon) and select “Add-ons and themes.” Then, click the gear icon in the top right of that page and select “Install Add-on From File.” This opens a file picker where you can select your .xpi file. This method is often more reliable than dragging and dropping, especially if the browser is blocking drag-and-drop actions.

Forcing Removal of a Stuck Add-On

Sometimes an add-on refuses to uninstall. The Remove button is greyed out, or the add-on reappears after restarting. The first workaround is to restart the browser in Troubleshoot Mode (formerly Safe Mode). Hold down the Shift key while clicking the Restart button in the Firefox menu. This starts Firefox with all add-ons disabled. Go to the Add-ons Manager and try removing the problematic extension from there. If that works, restart normally.

If the add-on still persists, you must delete its files manually. This is a more advanced step but is effective.

• Click the menu button and select “Help” then “More Troubleshooting Information.”
• In the “Application Basics” section, find the “Profile Folder” row and click the “Open Folder” button. This opens your profile directory in your file manager.
• Close Firefox completely.
• In the profile folder, look for a subfolder named extensions. Open it and delete the file or folder that matches the name of the add-on you want to remove. The names are usually a random string of letters and numbers, but the file will have a .xpi extension or be a folder containing the extension’s files.
• Also check the extensions.json file. This is a database of installed add-ons. If the add-on reappears, you may need to delete this file (Firefox will rebuild it on the next start).

After deleting the files, restart Firefox. The add-on should be gone.

Resetting the Startup Cache

A common cause of “stuck” add-ons is a corrupted startup cache. Firefox stores data about your add-ons in a cache to speed up launch times. If this cache becomes corrupted, the browser may think an add-on is still installed even after you remove it. To clear this cache, go to about:support and click the “Clear startup cache…” button in the top right corner. Firefox will ask you to restart. This action does not remove your bookmarks or passwords; it only rebuilds the temporary data files that track your browser components.

Using the Profile Manager as a Last Resort

If manual deletion fails and the add-on is causing severe issues (like crashing the browser on startup), the most drastic workaround is to create a new Firefox profile. This is not a removal of the add-on, but rather an isolation of it. Open the Profile Manager by closing Firefox and running firefox -p from your command line (or Run dialog on Windows). Create a new profile and launch Firefox with it. Your old profile remains untouched, and you can copy over your bookmarks and passwords using the built-in sync feature or by manually copying the places.sqlite file. This essentially gives you a clean browser without the problematic extension.

Frequently Asked Questions

Will disabling signature verification make my browser unsafe?
Yes, it increases risk. Unsigned add-ons have not been reviewed by Mozilla, so they could contain malware. Only do this if you trust the source of the add-on completely and understand the risk.

Why is the “Remove” button greyed out?
This usually happens when the add-on is an enterprise policy or was installed by the system administrator. It can also occur if the extension is corrupted. Restarting in Troubleshoot Mode often fixes the latter.

Can I install Chrome extensions in Firefox?
Not directly. Firefox uses WebExtensions, which are similar to Chrome extensions, but they must be packaged and signed for Firefox. You cannot take a .crx file and install it directly.

What if the add-on reappears after I delete it?
This indicates a sync issue. If you have Firefox Sync enabled, the add-on may be syncing from another device. Disable sync for add-ons in your Sync settings, then remove it again.

Does this work on mobile Firefox for Android or iOS?
No. These workarounds are for the desktop version only. Mobile browsers do not allow access to about:config in the same way, and the file system is restricted.

I set the flag to false, but it still won’t install. Why?
Mozilla occasionally removes the effect of these flags on the standard Release channel. Try using Firefox ESR or Developer Edition, which respect these settings for testing purposes.

Related

• How to Use Winget on Windows 11
• Fixed Stray Crashing on PC? Here’s the Fix
• Bedtime Mode on Samsung Galaxy Watch: How to Use It