Plugin Roadmap for Firefox

Plugins are a security and performance problem for Firefox users. NPAPI plugins are an obsolete technology, and Mozilla has been moving toward a Web which doesn't need plugins.  The last remaining NPAPI plugin, Adobe Flash, has announced an end-of-life plan. To support the transition away from Flash, Firefox is working with other browsers to progressively and carefully make Flash usage less common. Below is the roadmap of past and future support for plugins in Firefox.


June 2016

Starting with Firefox 47 in June 2016, all plugins other than Adobe Flash are click-to-activate. Users choose which sites are allowed to activate each plugin. In addition, the 64-bit version of Firefox for Windows only supports the Flash plugin.

March 2017

Starting with Firefox 52 in March 2017, plugins other than Adobe Flash are no longer supported in Firefox. Firefox Extended Support Release 52 continued to support non-Flash plugins until mid-2018.

August 2017

Starting with Firefox 55 in August 2017, users must choose which sites are allowed to activate the Flash plugin. Users will have the choice to remember the Flash setting per-site. This change was rolled out progressively during August and September 2017.

In order to improve security and performance, Mozilla will maintain a list of sites which cannot use any plugins.

September 2017

Starting with Firefox 56 in September 2017, Firefox for Android removed all support for plugins (bug 1381916).


In September 2019, Firefox 69 removed the "Always Activate" Flash option so Firefox always asks for the user's permission before activating Flash on a website.


In January 2021, Firefox 85 was the first Firefox version to ship without Flash support. Firefox now has new behavior when an attempt is made to embed an external object using the <object> or <embed> elements:

  • If the element lists a MIME type other than x-shockwave-flash or x-test then the behavior is unchanged. This means that non-plugin types behave as expected and unknown types are displayed at a size of 0 x 0.
  • If an <object> element has an HTML fallback in the DOM then the fallback is shown as expected.
  • For x-shockwave-flash or x-test types, the element is shown as a transparent region with the size specified in its width and height attributes.

See also End of support for Adobe Flash.

See also

Mozilla Firefox

Adobe Flash

Google Chrome

Microsoft Edge and Internet Explorer

Apple Safari