Chrome has a significantly more restricted extension API than Firefox; it mainly just consists of content scripts (with background pages) and a couple of hooks for context menus and popups and such. As such, it seems to me that a very significant subset of the Chrome API could be implemented in Firefox, either as a Firefox extension or a separate "extension compiler" like there exists for Greasemonkey scripts (which, incidentally, are another example of something that works exactly the same way as Chrome content scripts). If implemented, this would allow most Chrome extensions to install and run in Firefox.

I Googled around a bit and found several mentions of a very old attempt at this, but all of the links to the actual Mozilla repository for it are now dead. Even if they weren't, I'd be very surprised if this early effort still worked with either Firefox 4 or the latest changes to the Chrome extension API.

So my question is, does anybody know what the current state of the art is with regards to Chrome Extension API compatibility layers in Firefox? Have there been any extensions or extension compilers attempting to address the issues I brought up?

  • 1
    The source code of the Firefox add-on you mention is on BitBucket
    – niutech
    Mar 4, 2013 at 0:09

3 Answers 3


If there is such a beast, even Mozilla developers don't know about it!

Many Chrome "extensions" are just Greasemonkey scripts, and these can be used with the Greasemonkey extension or compiler on Firefox with no changes.

Unfortunately, extensions that use other APIs must be ported. If you're looking to port a Chrome extension to Firefox, or planning to write one for both, take a look at Mozilla's new Jetpack extension API, which was designed to work in a manner similar to the way Chrome's extensions work, but still offer the vastly increased access to the browser the original Firefox API is known for.

  • In that case, how can Chrome extensions be installed as GreaseMonkey scripts? (I think most (or all) of the Chrome extensions use the .crx file format.) Oct 30, 2012 at 3:47

As Mozilla is preparing its next-generation Servo engine, it's also phasing out older add-on technologies (e.g., XPCOM and XUL) and introducing new ones, like the WebExtensions API, which is "largely compatible with the model used by Chrome and Opera—to make it easier to develop extensions across multiple browsers". The WebExtensions API is nowhere near mature, so it's changing very fast; but if you're planning to port Chrome extensions over to Firefox with an eye towards the future, then I recommend installing Firefox Nightly and getting your hands dirty with the WebExtensions API today. You can read more about it in the links below.


You can use Extension Factory conversion tool in order to convert a Google Chrome extension to Firefox or Safari.

  • 1
    It no longer works, I tried.
    – JatSing
    May 9, 2013 at 17:24

You must log in to answer this question.

Not the answer you're looking for? Browse other questions tagged .