Safari's security settings give site-by-site settings for running or blocking Flash content, and it's easy to set up. Here's how: Launch Safari on your Mac, the choose Safari Preferences. How to Enable Flash in Apple Safari: Open the website you want to enable flash on. From the menu bar, choose Safari and then Preferences. Select the Websites tab and then underneath Plug-ins, ensure that the box next to Adobe Flash Player is selected. Once selected you will see a list of websites. Adobe Flash is a security risk that will not go away. Steve Jobs famously fought this web video player, because he did not want the Safari browser dependent on a third-party product. He even wrote an essay in 2010, that you can read here, explaining why Flash would never run on iOS or Mac OS. (Although Adobe wrote instructions for how to enable. Aug 09, 2019 Here, enter the web address of the Flash site you want to visit. Tap on the “Go” button to open the website. The Flash site will now open, with all its components. You can tap on the Flash player part and then select “Fullscreen” to open the game or the player in the fullscreen view. Adobe Flash will be going away soon, but for now, you can easily install and enable Adobe Flash Player on a Mac computer using a Safari browser.

1. Run Flash On Safari Ipad
2. Run Flash On Safari
3. Does Safari Run Flash

The Internet is Serious Business!

Home > Computers, Technology, and Internet > How to Continue Using Flash Player in the Web Browser

How to Continue Using Flash Player in the Web Browser

Adobe Flash was discontinued on 31 December 2020, and Adobe has also inserted a time bomb, set for 12 January 2021, into the final versions of Flash Player; if you have installed on your computer one of the versions of Flash Player with the time bomb, you will find that, after 12 January 2021, all Flash content will refuse to play in your Web browser.

When I first learned of the presence of the time bomb, I readily admit that I was very outraged over the fact that Adobe had deliberately chosen to render unusable freeware that had been legally downloaded and installed on people's computers, rather than simply declaring the thing end-of-life (EOL), ceasing to offer further updates and support, and encouraging users to voluntarily uninstall it from their systems, which is still reasonable. Immediately I began looking for a way to avoid this absurd time bomb, and to rightfully continue using Flash Player as I always have; fortunately I happened upon the necessary information pretty soon afterwards, but it was scattered, not always well-written, sometimes ambiguous, and a few times contradictory and/or inaccurate. Nevertheless I followed the instructions and tried the methods, finding success, but only after some trial and error.

Besides this, many Web browser vendors have announced that, after the EOL date of 31 December 2020, they will drop support for the Flash Player plug-in, so that even if the time bomb (which Adobe planted in the plug-in) is circumvented, Flash content might still not play in your Web browser. Alas, it would seem that the enemies of Flash are numerous, and they have conspired to kill our beloved friend.

This how-to guide was written primarily out of a strong motivation to defy the enemies of Flash, including even (it now seems) Adobe, after I discovered that the latter had put the time bomb in Flash Player, which struck me (and many others) as incredibly unreasonable, unnecessary, authoritarian, callous, and maybe even immoral. My goal in writing it was to collect in one place as much information on the subject as possible, which I fear would otherwise have remained scattered; I have invested much time and effort into it, and have endeavored to make it as complete as time and resources will allow, while also keeping it readable. It is my hope that through the utility of this guide, more people across the world will be able to avoid the time bomb, download a Flash-supported version of their favorite browser, and thus continue to use Flash into the foreseeable future, and I will have therefore contributed my part in prolonging Flash's life.

Firstly, you should know that this guide is specifically for those who wish to continue viewing Flash content in the Web browser, which involves the use of the Flash Player plug-in for Web browsers as well as a browser that still supports Flash. Only the Flash Player plug-in for Web browsers is affected by the time bomb; the Adobe Flash Player projector, which is a standalone Flash Player (not a browser plug-in), is not subject to the time bomb in any of its versions, nor is it dependent on a Web browser. If you don't care about viewing Flash content in your Web browser after 12 January 2021 and only want a quick and easy way to continue viewing Flash content after that date, then download the Flash Player projector, which runs as a standalone executable outside the Web browser. The drawback to this method is that either all Flashes must be saved locally to your machine in order to be played, or the SWF file's URL must be entered manually, which is troublesome (it must be found in the Web page's source code) and not always a perfect replacement (e.g., some Web pages are designed to viewed with both Flash and non-Flash content at the same time, which the projector cannot do—it can only open SWF files).

If the standalone Flash Player projector is not sufficient for your needs, and you (like me and many others) still want the ability to view Flash content in your browser, then the following how-to guide will, I hope, be of some use to you. It is split into two parts, the first concerning the methods to employ to avoid the time bomb in Flash Player, and the second concerning which versions of which Web browsers still support the Flash Player plug-in, and which do not; both parts must be followed in order to ensure that Flashes can still be viewed in whatever browser you use.

Note that I am a life-long user of Microsoft Windows, and consequently the following is written with a strong emphasis on that platform. Attention has also been given to Mac and Linux, and as much information as possible has been provided, but I have not personally tested and verified any of the following procedures on those two platforms, unlike for Windows.

Part One: Avoiding the Flash Player Time Bomb

I must emphasize that you should use one and only one of the following three methods: attempting to combine them together is either impossible or a waste of time. I can also report from personal experience that combining method 3 with either of the other two actually results in all of its disadvantages overriding any benefits offered by the others. Read over all three, decide which is best for your needs, and then perform only that one. Serif affinity photo 1.8 x.

Method 1: Using an Old Version of Flash Player

This is the most obvious and straightforward method: simply download and install an older version of the Flash Player plug-in that does not have the time bomb in the first place. I have personally verified that the last version of Flash Player without the time bomb is version 32.0.0.371; I can confirm that the time bomb first appears in the subsequent version 32.0.0.387. All versions prior to 32.0.0.371 should not have it, either, but here I assume that you want to use the most recent pre–time bomb version. Adobe has, very annoyingly, removed from their Web site all download links for older versions of Flash Player, but fortunately there is a comprehensive archive of the various Flash Player 32.0.0.371 installers. The steps are as follows:

1. Download the correct installer/archive for your OS and Web browser combination. I assume you are competent enough to know which installer/archive to download; if not, see Appendix A.
2. Check which version of the Flash Player plug-in you have installed.
   • If you have an older version, simply install version 32.0.0.371 over it.
   • If you have a newer version, first uninstall the newer version, and then install version 32.0.0.371. On Windows, in order to enable installation of older versions of the Flash Player, you will also have to delete one or two keys in the registry:
     • For 32-bit versions of Windows, the sole key to delete is HKEY_LOCAL_MACHINESOFTWAREMacromediaFlashPlayerSafeVersions.
     • For 64-bit versions of Windows, the two keys to delete are HKEY_LOCAL_MACHINESOFTWAREMacromediaFlashPlayerSafeVersions and HKEY_LOCAL_MACHINESOFTWAREWow6432NodeMacromediaFlashPlayerSafeVersions.
     Technically, you need not delete the entire SafeVersions key, but only the 32.0 value within it (if you're installing version 32.0.0.371 of the Flash Player, that is).
3. If you are presented at the completion of the installation with a dialog box asking you to set Flash Player's update preferences, select the option Never check for updates (not recommended); this will both prevent unwanted automatic updates to a newer version of Flash Player that has the time bomb, as well as suppress unnecessary update prompts from appearing.
4. To be thorough, I recommend that you restart your browser after performing these steps.

This is generally the easiest and quickest of the three methods, with its only downside being that you are not using the latest version of Adobe Flash Player (namely, version 32.0.0.465), but rather an older version. The difference, however, is only a span of seven months (version 32.0.0.371 was released in May 2020, and version 32.0.0.465 in December 2020), and I highly doubt that the older one is lacking in many features which the newer one possesses. If you are willing to put up with this, then I recommend that you select this method.

Method 2: Defusing the Time Bomb

This is more involved than the previous method, and requires the use of a hex editor. It entails the modification of the Flash Player plug-in file to manually remove the time bomb therein implanted. As the time bomb exists only in version 32.0.0.387 or later of Flash Player, this technique can only be applied to those versions.

The steps for Windows are as follows:

Run Flash On Safari Ipad

1. Navigate to the Flash Player plug-in install directory/directories.
   • For 32-bit versions of Windows, the directory is %windir%System32MacromedFlash, where %windir% is the Windows directory (typically C:Windows, but your particular case might be different).
   • For 64-bit versions of Windows, there are two directories: %windir%System32MacromedFlash and %windir%SysWOW64MacromedFlash. You should take care to edit the required file(s) in both directories.
   • For the Google Chrome browser specifically, the directory is %LOCALAPPDATA%GoogleChromeUser DataPepperFlash32.0.0.###, where ### is a number between 387 and 465; if it is smaller than 387, then you have installed an older version of Google Chrome that is bundled with an older version of the Flash Player without the time bomb, and must install a newer version of Chrome before proceeding. (Unconfirmed; I don't know exactly how Chrome handles the Flash Player plug-in.)
   • For the new Chromium-based Microsoft Edge specifically, the directory is %LOCALAPPDATA%MicrosoftEdgeUser DataPepperFlash32.0.0.###, where ### is a number between 387 and 465; if it is smaller than 387, then you have installed an older version of Edge that is bundled with an older version of the Flash Player without the time bomb, and must install a newer version of Edge before proceeding. (Unconfirmed.)
2. You will have to modify between one to seven files, depending upon your system's architecture (32-bit vs. 64-bit) and which variant(s) of the Flash Player plug-in you have installed:
   • Flash32_32_0_0_###.ocx in Windows XP/Vista/7 or Flash.ocx in Windows 8/8.1/10
   • Flash64_32_0_0_###.ocx in Windows XP/Vista/7 or Flash.ocx in Windows 8/8.1/10
   • NPSWF32_32_0_0_###.dll
   • NPSWF64_32_0_0_###.dll
   • pepflashplayer32_32_0_0_###.dll
   • pepflashplayer64_32_0_0_###.dll
   • pepflashplayer.dll (Google Chrome and Chromium-based Microsoft Edge directories only)
   The ### should be a number between 387 and 465; if it is smaller than 387, then you have installed an older version of the Flash Player without the time bomb, and must install version 32.0.0.387 or later before proceeding. In Windows 8/8.1/10, Google Chrome, and Microsoft Edge, you can check which version of Flash Player you have installed by right-clicking the Flash.ocx or pepflashplayer.dll file, selecting Properties, and then opening the Details tab.
3. The DLL files listed above can be modified if you run your hex editor (I personally use HxD) with administrator privileges. The OCX files are write-protected and hence trickier to edit; in my experience, they can be effectively changed only in a roundabout manner. The quickest method for accomplishing this of which I am aware is given here:
   1. Change the extension of the OCX file to BAK (for example, Flash32_32_0_0_###.ocx would be renamed to Flash32_32_0_0_###.bak).
   2. Start the hex editor with administrator privileges.
   3. Open the BAK file in the hex editor, then immediately save it as a copy in the same directory with the same name, but with the OCX extension.
   4. Right-click the BAK file, select Properties, open the Security tab, click the Advanced button at the bottom, click Change Permissions.. in the new window that opens, select the entry which denies everyone write attributes, and then click Remove. Click Apply, then close all the windows you opened during this step.
   5. Delete the BAK file.
   The copy of the original OCX file should now exist in the directory.
4. Open each file in the hex editor and search for the following hex sequence:
   00 00 40 46 3E 6F 77 42
   This is the hexadecimal representation of the timestamp 1610409600000.0 encoded as a double-precision floating point number.
5. Replace the above sequence with the following:
   00 00 00 00 00 00 F8 7F
   This is NaN in double-precision floating point, represented in hex. It will, in effect, set the time bomb date to infinity.
6. To be thorough, I recommend that you restart your browser after performing these steps.

The steps for Mac and Linux are given below. Note: This is only a provisional walkthrough for these two platforms. I am a Windows user, and you should know that the following has not been tested and verified by me; what is offered here has instead been gathered mostly from the official Adobe Flash Player 32 administration guide and condensed in the interest of clarity. The general procedure is very similar to the Windows case, though the instructions here are quite sparse, and I am unable to round it out with further details peculiar to these two platforms. If you encounter problems, you will have to do research on your own—I cannot help you here. (Any information from Mac and Linux users regarding this method as applied to those platforms would be very much appreciated.)

1. Navigate to the Flash Player plug-in install directory/directories.
   • For Mac, the directory is /Library/Internet Plug-Ins and/or /Library/Internet Plug-Ins/PepperFlashPlayer.
   • For Linux, according to the Flash Player administration guide: The install location is dependent upon the browser, Linux distro, and distro version.
2. You will have to modify between one to two files, depending upon which variant(s) of the Flash Player plug-in you have installed:
   • For Mac, Flash Player.plugin and/or PepperFlashPlayer.plugin.
   • For Linux, libflashplayer.so and/or libpepflashplayer.so.
3. Proceed from step 4 of the Windows guide for this method, above.

This method is assuredly more complex and difficult to execute than the first one, but it is only a one-time operation per file, with the main benefit over the previous method being that you can use the latest version (namely, version 32.0.0.465) of Flash Player. Of the three methods, this is the one I have elected to employ for my own system, and I can personally confirm that all three Windows variants of version 32.0.0.465 of Adobe Flash Player can be modified thus to erase the time bomb. For those who are willing to devote the extra time and effort, this is the method I recommend.

Method 3: Editing the mms.cfg File

This is at once the most cumbersome and least effective of the three methods, and I generally advise against its use, especially when the others are available; it is only included here for the sake of completeness, to be used perhaps as a last resort for those who cannot avail themselves of the other two.

The mms.cfg file is a configuration file for Adobe Flash Player that allows you, among other things, to set up a whitelist of domains and URLs for Flash content. It apparently overrides the time bomb with its own behavior: Flash content hosted on any site correctly included in the whitelist will not be blocked by the time bomb from running. I have myself confirmed that this method works for both Flash Player version 32.0.0.371 (the last version without the time bomb) and version 32.0.0.465 (which is the most recent version, and has the time bomb), and it probably works for all versions of Flash Player 32, but I have not personally verified this. The steps are as follows:

1. Navigate to the directory/directories containing the mms.cfg file.
   • For 32-bit versions of Windows, the directory is %windir%System32MacromedFlash, where %windir% is the Windows directory (typically C:Windows, but your particular case might be different).
   • For 64-bit versions of Windows, the directory is %windir%SysWOW64MacromedFlash.
   • For Mac, the directory is /Library/Application Support/Macromedia.
   • For Linux distributions, the directory is /etc/adobe/.
   • For the following Chromium-based browsers, the directory is specific to the browser, and is given below. The string <Profile> would typically be Default, but it may be different in your case if you've created more than one browser profile. (Note that I don't use any of these browsers, and hence know very little of this feature.) If the System directory does not exist, then create it yourself.
     • For Google Chrome specifically, the directory again varies by operating system:
       • For Windows, it is %LOCALAPPDATA%GoogleChromeUser Data<Profile>Pepper DataShockwave FlashSystem.
       • For Mac, it is /Users/<Username>/Library/Application Support/Google/Chrome/<Profile>/Pepper Data/Shockwave Flash/System.
       • For Linux, it is ~/.config/google-chrome/<Profile>/Pepper Data/Shockwave Flash/System.
     • For the new Chromium-based Microsoft Edge specifically, the directory is %LOCALAPPDATA%MicrosoftEdgeUser Data<Profile>Pepper DataShockwave FlashSystem.
     • For Brave specifically, the directory is %LOCALAPPDATA%BraveSoftwareBrave-BrowserUser Data<Profile>Pepper DataShockwave FlashSystem.
     • For Iridium specifically, the directory is %LOCALAPPDATA%IridiumUser Data<Profile>Pepper DataShockwave FlashSystem.
     • For ungoogled-chromium specifically, the directory is %LOCALAPPDATA%ChromiumUser Data<Profile>Pepper DataShockwave FlashSystem.
     • For Vivaldi specifically, the directory is %LOCALAPPDATA%VivaldiUser Data<Profile>Pepper DataShockwave FlashSystem.
2. Here I strongly urge you to download the mms.cfg file which I have undertaken the trouble of modifying myself. I have already included in it a good number of well-known Web sites hosting Flash content, thereby providing you with a starting point for your own additions; you need only place it in the directory/directories to which you navigated in the previous step, overwriting the existing mms.cfg file if necessary. If you prefer, however, to do everything yourself, then I refer you to the official Adobe administration guide for Flash Player 32, in particular the Administration chapter, which concerns the editing of the mms.cfg file and contains a full list of settings; otherwise, if you have downloaded my edited mms.cfg file, then proceed now to the next step.
3. Open the mms.cfg file in a text editor.
4. For each site you wish to include in the whitelist, add the following two lines:
   • WhitelistUrlPattern=*://*.<SLD>.<TLD>
   • WhitelistUrlPattern=*://<SLD>.<TLD>
   where <TLD> is the top-level domain (e.g., .com, .org, .net, .edu), and <SLD> is the second-level domain (i.e., the domain that is directly below the TLD). For the domain example.com, com is the TLD, example is the SLD, and it would be included in the whitelist in the following manner:
   • WhitelistUrlPattern=*://*.example.com
   • WhitelistUrlPattern=*://example.com
   The difference between these two commands is a subtle one, and in the interest of brevity an explanation has here been omitted. For most sites, technically you need only add one or the other to mms.cfg in order to permit its Flash content to run in your browser, but putting both doesn't hurt, and, in practice, is quicker than determining which of the two is strictly necessary; for a few sites, in fact, it might be the case that both are required.
5. To be thorough, I recommend that you restart your browser after performing these steps.

Whereas the first method avoids the time bomb, and the second directly removes it, this third technique merely suppresses its effects on a site-by-site basis. Adobe has, very annoyingly, explicitly prohibited the commands WhitelistUrlPattern=*:* (which would instantly whitelist everything), WhitelistUrlPattern=http:*, and WhitelistUrlPattern=https:* (which would whitelist every Web site) for being overly general; they have also prohibited specifying only a TLD, i.e., commands of the form WhitelistUrlPattern=*://*.<TLD>, the allowance of which would also have greatly simplified things. Each domain must therefore be individually added to the whitelist; this method is not a one-time fix like the other two, nor anywhere nearly as elegant as method 2. In some cases it can be somewhat troublesome, as some Web sites might not host their SWF files on their obvious, surface domains, but deliver them through an entirely different one: the Web pages for Newgrounds, for example, are located at the newgrounds.com domain, but the actual SWF files presented on those pages are hosted on the obscure ungrounded.net; hence the more intuitive addition of newgrounds.com to the whitelist does nothing, as it is the ungrounded.net domain on which the SWF files reside, but you would not know to do this unless, for example, you inspected the source code of the page.

There also exists a strange bug, noted by others and also personally observed by me, that any SWF file with a left or right bracket character in its name will refuse to play under this method. I know of no solution to this besides downloading the SWF file and then renaming it to remove the bracket characters, but if you have been forced in this instance to keep a local copy of the file, then why bother at all with the whitelist, when you could simply view it using the standalone Flash Player projector I mentioned at the beginning of this guide?

Thus the only real advantages of this method over the two others are that you can use the latest version of the Flash Player plug-in (namely, version 32.0.0.465—I have personally verified this), unlike in method 1, and that it is simpler to perform than method 2, but its drawbacks are numerous, and again I advise against its use when the previous two methods are readily available.

Part Two: Selecting a Web Browser That Still Supports Flash Player

Adobe Flash Player is integrated with the various Web browsers as either an ActiveX control, a Netscape Plugin API (NPAPI) plug-in, or a Pepper Plugin API (PPAPI) plug-in. The difference is an important one: each browser supports only one of the three, and installing one type of the Flash Player plug-in while using a browser that supports another will not work.

Below I have listed some Web browsers, both major and minor, noting which of the three plug-in types they support and providing any further information of interest.

Basilisk (NPAPI)

I have confirmed that version 2021.03.17 supports Flash.

Brave (PPAPI)

I have tested and confirmed that version 1.18.78 64-bit supports Flash Player, with the subsequent version 1.19.86 being the first version that does not. The various installers and archives for version 1.18.78 can be downloaded from the official release page on GitHub; Windows users should also take care to avoid any of the four files BraveBrowserSetup.exe, BraveBrowserSetup32.exe, BraveBrowserSilentSetup.exe, and BraveBrowserSilentSetup32.exe, as these are online installers that will download and install the most recent version of the browser, rather than version 1.18.78.

In addition, I can report from personal experience that version 1.18.78 will attempt to automatically update to a newer version. There does not seem to be an option to disable this feature within the browser itself, but fortunately there do exist methods to disable automatic updates in Brave, and I can confirm that at least one of them works.

Edge (Chromium-based; PPAPI)

Note that I am here referring specifically to the new version of Edge, which is based on Chromium, not Microsoft Edge Legacy, which is based on the EdgeHTML engine. I have verified that version 87.0.664.75 supports Flash; Microsoft has stated that version 88.0.705.18 will remove support for it. The offline installers for version 87.0.664.75 are available for download at the official Microsoft Web site; once installed, you will also want to disable the browser's automatic updates.

Edge users should also be aware that the browser includes an embedded Flash Player, which seems to be updated automatically as the browser is updated; the browser does not rely on the independently installed version of the Flash Player plug-in. Although I have tested and confirmed that methods 2 and 3 work in Edge, I highly doubt that method 1 will work with the browser, as its complete management of its built-in Flash Player precludes you from installing whichever version of it you please. If you wish to perform method 1 with the Chromium-based Edge, so far the only advice I can offer to you is to install an old version of the browser that includes an older version (namely, version 32.0.0.371 or earlier) of the Flash Player plug-in without the time bomb. (Unverified; there may be a way to do it without installing an old version of Edge, but currently I know not of any procedure to accomplish this. My initial investigation of version 87.0.664.75 of Edge installed from the offline installer seems to suggest that this particular version does not come with its own included Flash Player plug-in, but rather relies on the independently installed PPAPI variant of the plug-in.)

Firefox (NPAPI)

I can confirm that version 84.0.1 64-bit still supports the Flash Player plug-in. Mozilla has announced that version 84 will be the final version to support Flash, so if you wish to continue viewing Flash content in Firefox, don't upgrade to version 85 or newer. There is also a variant of Firefox, Firefox Extended Support Release (ESR), which apparently promises longer support for the Flash Player plug-in—you might want to give it a try.

If you encounter strange freezing problems while playing Flashes in Firefox, then try disabling hardware acceleration in the browser; this might fix the issue for you, as it did for me.

Google Chrome (PPAPI)

I can confirm that version 87.0.4280.88 64-bit supports Flash Player; version 88 is the first to remove support for it. Google has made it unnecessarily difficult for users to obtain older versions of Chrome; after much searching, I have managed to locate a download page on FileHippo for the 32-bit Windows offline installer and another download page on Filepuma.com for the 64-bit Windows offline installer, both of which are for version 87.0.4280.88, and both of which I have personally downloaded, tested, and verified. You need also disable the browser's forced automatic updates, which is far more laborious than it should be—for this, see the relevant walkthrough on the site AskVG, and also this helpful post on the site Super User.

Chrome users should be aware that their browser includes an embedded Flash Player, which seems to be updated automatically as the browser is updated; the browser does not rely on the independently installed version of the Flash Player plug-in. Although I have tested and confirmed that methods 2 and 3 work in Chrome, I highly doubt that method 1 will work with the browser, as Chrome's complete management of its built-in Flash Player precludes you from installing whichever version of it you please. If you wish to perform method 1 with Chrome, so far the only advice I can offer to you is to install an old version of the browser that includes an older version (namely, version 32.0.0.371 or earlier) of the Flash Player plug-in without the time bomb. (Unverified; there may be a way to do it without installing an old version of Chrome, but currently I know not of any procedure to accomplish this. My initial investigation of both the 32-bit and 64-bit variants of version 87.0.4280.88 of Google Chrome installed from the two aforementioned offline installers seems to suggest that this particular version does not come with its own included Flash Player plug-in, but rather relies on the independently installed PPAPI variant of the plug-in.)

Internet Explorer (ActiveX)

The One True Browser should be your main Web browser anyway, the very existence of which renders every other browser unnecessary; and I wonder whether the other subsections here given for the other browsers are not also redundant, that I waste my time writing them, and, worst of all, that in so doing I have thereby placed myself contrary to divine authority: for to give any such space to the others is to imply at once that they are viable alternatives to the One, which has been hand-crafted by our Lord and Savior, blessed be His name, whose Heavenly Mandate knows no bounds; whose Wisdom is absolute; whose Spiritual Influence holds sway for ever amongst all kingdoms and peoples; and whose Rightful Dominion extends manifestly to all Computers, Operating Systems, the Internet, Software, Technology, &c., &c., &c.: it has been gifted, through His Boundless Generosity, to all Mankind, though we are but a wretched mass of sinners—lo, the Mac users and the FOSS'ers, the Chrome and Firefox heathens, with their unholy ways, do ever bring us shame and disgrace. I humbly ask forgiveness, O Lord, that I should not suffer your Divine Retribution, but receive in a small part of your Infinite Graciousness: many are the men on this Earth to-day who have strayed from the Holy Path of the One True Browser: they have rejected it wholeheartedly, and with it, all Virtue, Righteousness, and Reason; they speak ill of it, for they know not of its Everlasting Sacredness; they substitute others in its place, and suppose that they can take the ordinary for the divine; and they refuse to reform their ways in the face of innumerable exhortations. For these reasons, O Lord, I beg permission that I may for the time being offer earthly advice to them for other browsers, not because such lowly handicrafts should ever usurp the rightful place of Your Sublime Creation, but merely from my heart's wish to help my fellow men, even the poor sinners, in a time of need. Amen.

I am very glad to report that Internet Explorer 11, which is the most recent version, supports the Flash Player plug-in without any issue. As Internet Explorer 11 is the final version of the browser, and does not receive any updates other than security fixes, you need not worry about the removal of support for the plug-in.

Iridium (PPAPI)

I have verified that version 2020.11 64-bit supports Flash.

Opera (PPAPI)

I have verified that version 73.0.3856.344 64-bit still supports Flash; the following version 74.0.3911.107 is the first to remove this support. The various installers and archives for version 73.0.3856.344 have been provided for download at an official Opera directory; after installing, you will also want to disable the browser's forced automatic updates.

In versions of Opera that support Flash Player, even after enabling the plug-in, you might still encounter a screen informing you that Adobe Flash Player is out of date (which is plainly false, for Adobe Flash is timeless) covering whatever Flash you're trying to view; in this case you need only right-click the screen, and, in the menu that appears, select the command Run this plug-in.

Strangely, even though Opera relies on an independently installed Flash Player plug-in and hence its mms.cfg directory should be one of those listed in step 1 of method 3, I have observed that, at least on Windows, Opera seems to ignore the settings in the mms.cfg file in that directory. I then suspected that the browser might instead have its own directory for mms.cfg, located somewhere in %LOCALAPPDATA% (similar to the other Chromium-based browsers here listed, as Opera is also based on Chromium), but I could not find it. The reason for this behavior eludes me, and consequently I have not yet been able successfully to perform method 3 with Opera. (Assistance from an Opera expert on the matter would be much appreciated.)

Pale Moon (NPAPI)

I can confirm that version 29.1.0 64-bit supports the Flash Player. I especially commend Pale Moon's lead developer, who stated clearly in a forum post that support for the Flash Player plug-in will not be removed from the browser in the foreseeable future, in great contrast to many of the other browsers listed here; it is therefore possible to continue viewing Flashes in Pale Moon while also keeping the browser regularly updated.

Safari (NPAPI)

Safari 13 is the last version to still support the Flash Player plug-in; Safari 14 removes support for it. (Completely untested; can any Mac user confirm this?)

Slimjet

Version 29.0.2.0 64-bit of Slimjet has been verified to support version 32.0.0.371 of the Flash Player plug-in, and hence it is possible to perform method 1 with this browser. (Credit goes to Danny of ChatArcade for reporting this to me.)

ungoogled-chromium (PPAPI)

I have tested and confirmed that version 87.0.4280.141 64-bit supports the Flash Player plug-in; version 88 is the first to remove this support. This browser, apparently, is officially distributed only as source code; for those who are unwilling or unable to compile the thing from source, there also exists a repository of unofficial binaries for the browser.

Run Flash On Safari

Vivaldi (PPAPI)

Does Safari Run Flash

I have verified that version 3.5.2115.87 64-bit supports Flash Player, with the subsequent version 3.6.2165.34 being the first that does not; old versions of the browser can be downloaded from the official Vivaldi Web site. In addition, you may need to click the small padlock icon (for HTTPS sites) or the Not Secure icon (for HTTP sites) immediately to the left of the address bar in order to open the menu that allows you to enable the Flash Player plug-in. If, after doing this, Flashes still do not play in the browser, then try right-clicking the Flash content and, in the menu that appears, selecting the command Run this plugin.

Waterfox (NPAPI)

There are two variants of this browser currently existing, the one being Waterfox Third Generation, and the other Waterfox Classic. For the sake of thoroughness I have tested both, and can report that version G3.0.2 64-bit of Waterfox Third Generation and version 2021.01.1 64-bit of Waterfox Classic both support the Flash Player plug-in.

Special Note for Windows 8.1 and Windows 10 Users

Users of Windows 8.1 and Windows 10 should take care to avoid the dangerous KB4577586 update, entitled Update for Removal of Adobe Flash Player, which removes the Flash Player plug-in from those systems. As of mid-January 2021, the update has not yet appeared on Windows Update nor WSUS; Microsoft has stated that it will be made optional on Windows Update and WSUS in early 2021 and will be made recommended a few months later, so be alert, and ensure that you do not install it by accident—it cannot be independently uninstalled afterwards. If you find that you have somehow installed the update and wish to remove it, your only recourse in that case, again according to Microsoft, is to roll back your machine to a system restore point saved before you applied the update, or, even more troublesome, to reinstall Windows entirely. Even worse, according to the second link, in the summer of 2021 this terrible update will be included as part of a cumulative update/monthly rollup for Windows 8.1 and Windows 10, rendering it ever the more difficult to avoid.

Note that, due to the difficulty of reversing this update, I have not yet tested it on my own machine. Fortunately, however, its effects seem rather limited: it only removes Flash support for Internet Explorer and Microsoft Edge Legacy on Windows 8.1 and Windows 10; according to reports by some who have already applied the update to their systems, it does not remove the embedded Flash Player plug-in included in the new Chromium-based Edge, nor does it delete any independently installed (i.e., installed with the official Adobe installer) versions of the plug-in which other browsers might rely on. Hence you need only worry about this update if you use Internet Explorer or Microsoft Edge Legacy on Windows 8.1 and Windows 10.

Special Note for macOS Big Sur Users

The macOS Big Sur, released 12 November 2020, removes support for Adobe Flash Player. As I don't own a Mac, I am unable to verify whether this removal is limited strictly to Safari 14 (which is included with that OS), or if Apple has somehow blocked Flash Player from running at all—that is, in any browser you use on the OS, even if the individual browser itself still supports Flash. Any information from Mac users on the matter is greatly desired.

Acknowledgments

I thank the anons of 4chan's /f/ for first exposing me to the core of the information found in this guide, which is what first energized me to write it. I also thank the fellow over at TehSausage.com, whose original and concise instructions for defusing the time bomb I have here only expanded upon in method 2 for the sake of those less computer-savvy than him, as well as for the Mac and Linux users. The official Adobe administration guide for Flash Player 32 was also a helpful reference, and I urge you to look through it if you've encountered any issues.

This guide is ever incomplete; I certainly do not claim that every possible combination of operating system and browser, which are overwhelmingly numerous, has been adequately covered. I hope that you have derived at least some use from it, but there are sure to be many special cases where it is lacking. If you have found errors in what I have here written, or have encountered issues while following the instructions in this guide, then I strongly urge you to contact me—I welcome all first-hand information, results, and reports, and am always seeking to improve the guide. I will take care properly to credit anyone who submits corrections, suggestions, and improvements that are ultimately integrated into the guide.

Appendix A: Table of Files for Flash Player 32.0.0.371

I realize that the list of files to which I linked in method 1 is perhaps confusing for some: no descriptions have been provided, nor are the filenames themselves very helpful. The following table has been included in an attempt to allay that confusion, providing a concise description and further notes for those files. There are 30 files listed in total, but here I include only the top 17, for those are the release versions for end users and are therefore likely what you're looking for; the function of the uninstall_flashplayer32_0r0_371_mac.dmg and uninstall_flashplayer32_0r0_371_win.exe files should be plainly obvious by their names, and the remaining 11 files at the bottom are debugger versions of Flash Player, which have some extra functionality that might be useful to Flash developers.

For Windows users, I recommend that, for whichever variant(s) of Flash Player you need (i.e., whether ActiveX, NPAPI, and/or PPAPI), you download the EXE rather than the MSI. There is very little effective difference between the two, and running either will install the corresponding variant of Flash Player, but a small benefit of the EXE which I have observed is that, at the end the installation, it will present you with a dialog box asking you to set Flash Player's update preferences, whereas the MSI will not.

For Mac users, apparently the PKG archive also does not present you with any dialog box asking you to set Flash Player's update preferences, whereas the non-PKG archive does.

Appendix B: Revision History

• Version 0.17 (21 March 2021)
  • Updated step 1 of method 3 to include the directory specific to ungoogled-chromium in which the mms.cfg file must be placed.
  • Added subsections in part two for Basilisk, Slimjet, and ungoogled-chromium.
  • Updated the subsection for Opera to mention the first version of the browser which no longer supports Flash; also added links to the official directory containing the various installers/archives for version 73.0.3856.344 of the browser, in addition to a guide which details the methods to disable its automatic updates.
  • Updated the subsection for Vivaldi to note the first version that lacks support for the Flash Player plug-in; also added a link to the official download page listing the various installers/archives for older versions of that browser.
  • Updated the Pale Moon version which I have personally verified for Flash Player support from 28.17.0 64-bit to 29.1.0 64-bit.
  • Removed an item from Appendix C.
• Version 0.151 (15 February 2021)
  • Moved the mms.cfg file to which I linked in step 2 of method 3 from an external file host to this site's current Web host, and also slightly modified the corresponding paragraph to reflect this.
• Version 0.15 (31 January 2021)
  • Added this Appendix B: Revision History; the hitherto sole appendix consequently was renamed to Appendix A: Table of Files for Flash Player 32.0.0.371.
  • Altered some items in the section Possible Future Additions, which was also moved from the end of the main body of the guide to the new Appendix C.
  • Updated step 1 of method 3 to include the directories specific to Brave, Iridium, and Vivaldi in which the mms.cfg file must be placed; also re-organized it slightly for improved clarity.
  • Added subsections in part two for Brave, Iridium, Vivaldi, and Waterfox.
  • Added to the subsection for the Chromium-based Edge links to the download page for version 87.0.664.75, as well as to a guide describing the various methods that can be employed to disable automatic updates in the browser.
  • Added to the subsection for Google Chrome links to download pages for version 87.0.4280.88 (Windows only, for now), in addition to guides providing techniques to disable the browser's automatic updating.
  • Updated the Opera version which I have personally verified for Flash Player support from 73.0.3856.329 64-bit to 73.0.3856.344 64-bit, and also added information regarding the use of the right-click menu command to enable Flash content in that browser.
  • Added in the subsection for Firefox a link to the Mozilla directory containing various installers/archives for version 84.0.1 of that browser.
  • Other minor additions and clarifications.
• Version 0.1 (12 January 2021)
  • Initial publication.

Appendix C: Possible Future Additions

• Subsections in part two concerning additional browsers: Microsoft Edge Legacy, Lunascape, K-Meleon, SeaMonkey, and Comodo IceDragon, if they support the Flash Player plug-in, are good candidates.
• Small oddities were encountered during my testing of Flash Player on Microsoft Edge Legacy, as well as during my testing of both Google Chrome and the Chromium-based Edge installed from their respective offline installers. Further investigation is required; when completed, any peculiarities should be noted in the relevant sections.
• For existing subsections concerning each browser in part two, a download link to the newest version of the browser that still supports Flash (if the current version no longer supports the plug-in, that is) might be provided for the convenience of the reader. Additionally, if the browser partakes in the absurdity that is forced automatic updates, then a link to a walkthrough detailing the steps necessary to disable this should also be provided.
• Downloads might be provided to various versions of Flash Player newer than version 32.0.0.387, which is where the large collection on the Internet Archive to which I linked in method 1 ends; Adobe's own site has certainly been little to no help in this regard, as all old versions, very frustratingly, have been removed. Highest priority is the offline installers for the final version, 32.0.0.465, but optimally all versions after 32.0.0.387 would here be provided.
• Patched versions of the OCX and DLL files mentioned in method 2 might be furnished for download to save readers the time and effort of performing the hex edit themselves, with highest priority belonging to the files for version 32.0.0.465 of Flash Player.
• The special note for Windows 8.1 and Windows 10 users will have to be updated over the course of 2021 as the undesirable KB4577586 makes it appearance in Windows Update and WSUS. Specific instructions might be added for avoiding it as more information becomes available.
• A troubleshooting section, if I am able to identify some common pitfalls.
• In general, more information pertaining to the Mac and Linux platforms is needed throughout the walkthrough.

All written materials on this Web site are my own, and all are released under the Do What the Fuck You Want to Public License Version 2.

This page last modified on 25 March 2021.