New Chrome Runs A Few Too Many Flash Plug-Ins. Here’s How To Disable Them

New Chrome Runs A Few Too Many Flash Plug-Ins. Here’s How To Disable Them

Last month, Google updated Chrome to version 20. As part of the upgrade, the browser’s built-in Flash plug-in was moved from the ancient Netscape plug-in API (NPAPI) to Google’s newer Pepper API (PPAPI). Unfortunately, by default, Chrome doesn’t disable the legacy plug-in and leaves it running side-by-side with the PPAPI one. Fortunately, it’s simple to switch the old one off.

New Chrome Runs A Few Too Many Flash Plug-Ins. Here’s How To Disable Them

As Locker Gnome advises, just type “about:plugins” into a Chrome tab and you’ll be directed to the browser’s plug-in configuration page. “Shockwave Flash” is what you’re looking for — the screenshot here shows what you should see. If you can’t see the extended options, make sure to hit the “Details” box in the top-right corner to expand each item.

The API used by each plug-in is listed next to the word “Type”. The new Flash will specify “PPAPI (out-of-process)” while the old one will have “NPAPI”. All you have to do is click the “Disable” link next to the NPAPI plug-ins to deactivate them. If you don’t see a PPAPI plug-in, chances are you haven’t updated to the latest Chrome.

Alternatively, if you’ve found Chrome’s Flash capabilities have been letting you down since you updated, you can disable the new PPAPI plug-in.

How to fix Shockwave crashes in Chrome [Locker Gnome]


  • I’ve been having some flash crashes lately and wondered if this was the reason, so I updated to the most recent chrome and went to disable the plugin, but didn’t see the PPAPI plug in listed. After googling, I’ve discovered this is because its not available to Mac users yet. So, just an FYI in case any other Mac users didn’t know. : )

  • I’m confused. You’ve said to disable any NPAPI ones, however the linked article says to “disable the file located in Chrome’s AppData folder and not the separate stand-alone Flash installation”.

    My PPAPI plugin is in my Chrome App Data folder, and I have an NPAPI one that is not. (I also have a third NPAPI that is in the App Data folder).

    Which one is the one to keep?

  • I have noticed YouTube video problems with the bottom pixel of Flash videos display the page behind the Flash and after clearing cache and viewing something with Flash the first page view displays an empty area where the Flash is. If the flash is clickable or has audio you can hear the audio and click on the Flash but it does not display on the page you just see the page background where the Flash should appear.

    Disable one of the two Flash plugins under chrome://plugins solves the youtube video pixel problem and the problem where Flash does not displaying on the first page view after clearing the cache.

    I don’t know why if you disable one of the flash plugins it seems to clear up several Flash related issues bot on Mac and PC. I looked at my plugins and they are the same version but located in different directories. I think the mime-type has a race condition between the system flash and the chrome flash plugin. The race condition results in possibly rendering multiple version of the flash plugin on top of each other causing the dancing video issues or in the other case not displaying the content at all even though it is running and clickable and you can hear the flash audio but not see the flash.

    Chrome has two flash plugins that cause unexpected behavior. There seems to be a race condition or mime-type issue by disabling either one and leaving the other one enabled it resolves flash video artifacts and some Flash movie does not render on page correctly issue and after clearing the cache and the first page view containing Flash does not render the Flash but reserves the area on the page where the flash is supposed to live and the Flash plays audio and is clickable but not displaying.

    Chrome Version (type about:version into your omnibox):
    Operating System (Windows 7/8/Vista/XP, Mac, Linux, Android, iOS):
    Extensions (type Chrome:extensions into your omnibox):

Show more comments

Log in to comment on this story!