How to Enable Flash in Chrome on Mac

Overview

Adobe Flash reached end of life in December 2020, and modern Chrome versions on macOS no longer support Flash by default. However, organizations with controlled environments may still need to enable Flash for legacy internal apps or published assessments. This guide explains the current deprecation status, security considerations, and the limited scenarios in which Flash can still be enabled in Chrome on macOS, using enterprise policies or temporary workarounds where applicable. These steps are provided for informational and legacy support purposes only, with strong caution against routine use on public websites.

Flash status and context for Chrome on macOS

Current deprecation and support timeline

Adobe Flash is officially end-of-life across all platforms, and major browsers including Google Chrome have removed or restricted Flash support. On macOS, Chrome no longer includes Flash, does not offer an installable Flash plugin, and blocks Flash content by default. The Flash-related features in Chrome flags (such as Chrome://flags/#enable-flash) have been removed in recent stable releases. Any remaining use of Flash should be limited to controlled, local content, and organizations should plan to migrate to supported technologies. The following sections describe historical context and conditional workflows for reference environments only.

Verify your Chrome and environment

Confirm Chrome version and Flash availability

First confirm the Chrome version running on your Mac and whether any Flash-related flags or enterprise policies are still present. Follow these steps to verify your environment before considering any legacy workarounds.

• Open Chrome and go to chrome://version to record the version number and channel (Stable, Beta, or Dev).
• In the address bar, try chrome://settings/content/flash. If the page loads, review the top-level setting; note that recent versions do not expose an Allow toggle for third-party Flash.
• Go to chrome://settings/help to check for updates and confirm you are on the latest stable build for macOS.
• Check chrome://flags and use the search box to look for any remaining references to Flash; absence of Flash flags is expected in current releases.

Organization-managed scenarios

Enterprise policies for legacy internal sites

If you are in a managed organization that still requires Flash for internal tools, use Chrome enterprise policies to control behavior on a whitelist of URLs only. This approach is strongly discouraged for general web browsing and should be limited to controlled intranet applications that cannot be migrated. Contact your IT administrator before applying any policy changes.

• Locate the appropriate policy template for your OS (macOS property list or Windows ADM/ADMX).
• Specify only the minimal set of origins that require Flash under FlashAllowList.
• Set DefaultPluginSetting to block by default and explicitly allow only when necessary.
• Deploy the policy through your MDM or configuration manager and validate behavior on a test device.

How policies affect Flash behavior in Chrome

Enterprise policies can define whether Flash is blocked globally, allowed from specific sites, or prompted per session. On macOS, policies are applied via the Chrome preferences file (Preferences in the user data directory) or through platform-specific configuration profiles. Even when a policy permits Flash, Chrome may still block it if a plugin is not installed or if the content is served from untrusted origins. Always verify policy application in chrome://policy and test locally before broad deployment. Note that policies cannot restore Flash if the underlying plugin binary is missing.

Check site and browser settings

Site-specific and per-session allowances

If you are using a legacy enterprise scenario where Flash is minimally allowed, you can review and adjust site-specific settings inside Chrome. These settings only work if a compatible plugin is present and policies do not block it outright. Adjustments are managed on a per-site basis and do not enable Flash on sites that are blocked by enterprise policy or missing plugin binaries.

1. Navigate to the site that requires Flash.
2. Click the Lock or Info icon to the left of the address bar and open Site settings.
3. Select Flash and choose Allow or Block for that origin, if the option is available.
4. Reload the page and confirm that Flash content behaves as expected.

If the Flash content still does not run, check chrome://settings/content/flash and ensure the site is listed under allowed sites (where visible). Also verify that no conflicting enterprise policy overrides the site-level setting.

Security considerations and risks

Why Flash is blocked and the importance of avoiding workarounds

Flash is blocked by default in modern browsers because it has a long history of security vulnerabilities, performance issues, and lack of support on macOS. Enabling Flash increases exposure to malicious content, especially on untrusted or unknown sites. Do not install older Flash versions or NPAPI plugins obtained from unofficial sources. Avoid browser extensions or developer modes that claim to restore Flash functionality unless they are officially supported enterprise tools. Prioritize migration to HTML5, WebAssembly, or native applications that receive ongoing security updates.

Alternatives and migration guidance

Replace Flash content with modern technologies

The sustainable path forward is to replace Flash-based experiences with current web standards or native tools. For interactive content, use HTML5, CSS animations, and JavaScript frameworks. For media, prefer <video> and <audio> with widely supported codecs. For authoring, move to tools that export to HTML5 or web-based formats. If a vendor still requires Flash, request updated builds or documentation that confirm compatibility with modern browsers. Use browser developer tools to identify embedded Flash objects and plan replacements.

• Check chrome://settings/content/flash for any allowed origins and remove obsolete entries.
• Audit internal applications for Flash dependencies and set migration deadlines.
• Validate alternatives in a test environment before rolling out changes to users.

Summary checklist

Use this concise checklist to confirm your understanding and next steps for Flash in Chrome on macOS.