Chrome 55 for desktop starts rolling out, blocking Flash even further by defaulting to HTML5; sites that only support Flash and top 10 sites are exempted
Over the past year, Google Chrome has been implementing a multi-phase plan to de-emphasize Adobe Flash.
Context & Ripple Effects
This rollout is the payoff of a year-long choreography Google announced in May, when it said Chrome would make the Flash plugin click-to-play by default in Q4 while rendering HTML5 where available. The September step already cut off "behind the scenes" Flash content (blocked ahead of schedule), leaving today's change — HTML5 as the default for the main content itself — as the phase that actually moves what users see.
The carve-outs matter as much as the block: Flash-only sites and the ten most-visited Flash-dependent sites keep working, an acknowledgment that Google can only push as fast as the top of the web migrates. Days later, Microsoft confirmed Edge would follow with its own default block and a similar popular-sites exemption (without naming which ones).
First-order effects
- Sites still serving central content in Flash now render HTML5 instead for most Chrome desktop users, forcing publishers to complete migration or accept broken experiences outside their exemptions.
- Adobe's plugin loses its default distribution channel on the dominant browser, shrinking Flash's install base to the exempted top-10 list and legacy-only pages.
Second-order effects
- Microsoft Edge's matching default-block, announced within two weeks, removes any incentive for developers to hold out for non-Chrome browsers — the exemption-list model becomes the industry template.
- With both major engine vendors converging on HTML5 defaults, ad networks and analytics vendors built on hidden Flash elements face forced rewrites rather than gradual attrition.
Third-order effects
- Browser vendors are now the effective enforcement mechanism for web standards, and the power to grant exemptions gives the market-share leader case-by-case gatekeeping over which sites may run legacy code — a dependency structure that recurs whenever one client controls access to the web.
The trend: Browsers are retiring third-party plugins in favor of native web standards on a schedule set by Chrome, with competitors adopting its exemption mechanics rather than charting their own pace.