Managing (enabling, disabling) user-defined sets of add-ons/extensions

For Firefox

Please, is there anything?

For Chromium and Google Chrome

SimpleExtManager is simple and effective –

– and there’s active development.


In the 1990s, for System 7 and Mac OS we had Apple’s Extensions Manager:



Image sources:

Multiple Addon Deactivator (M.A.D.) was last released in 2012, no longer compatible with Firefox –

– or SeaMonkey (there’s a list of add-ons but check boxes don’t work, and so on):

More recently, Extensions Manager (aka Switcher) for Google Chrome –


not for Firefox and it’s reportedly abandoned (no longer able to work with user-defined groups/sets).


Have you already tried to install one of these Chromium Extensions via ? It might “just work” due to the similarity of the WebExtensions APIs.


A good idea, thanks – I used Chrome Store Foxified on a handful of occasions in the past – but I didn’t expect it to work in this case.

SimpleExtManager from Chrome Web Store does not recognise extensions, and can’t create groups, with Firefox:

In the absence of a suitable extensions manager

A combination of five legacy extensions can make things a little more manageable with Firefox 55:

I’d like to decrease the noise:

  1. LEGACY need not be shouted (UPPERCASE), emphasised or so heavily highlighted
  2. never show :information_source: Compatible with multiprocess

– maybe I can hack Add-on Compatibility Reporter to suppress that :information_source: line …


This extension might have potential:

Simple Add-on Manager

1 Like

Thanks @grahamperrin for this well done report.
I’m still looking for such en extension “toggler” and/or (better) “manager” neither…
A port of SimpleExtManager (Chrome) would be indeed very welcomed…

Have you found something since ?
Firefox is lacking on so many aspect … Have you considered switching browser ?

1 Like

Sorry, no.


1 Like

Anyone have suggestions on this topic about a year later? I’ve been looking for over an hour now with no luck.


Hi @neopatriota, you sound pretty distressed. I’d ask you to take a deep breath before continuing this conversation.

The transition to the WebExtensions API happened three years ago. You can read more about some of the factors that went into this decision on this blog post.

If you have questions about why certain features are not available with the API, I’m happy to look into it. Otherwise, I’d ask you to refrain from spreading fear and unfounded rumors on our forum.

1 Like