Google plans to make Flash plugin click-to-play by default in Chrome in Q4'16, rendering HTML5 instead when available, except for 10 top sites relying on Flash
Google has outlined a plan to push HTML5 by default in Chrome, instead of Flash. In Q4 2016, the company plans to only serve Flash …
Context & Ripple Effects
This plan is the middle beat of a phase-out Google had been telegraphing for over a year: YouTube switched its video default from Flash to HTML5 back in January 2015, and in February 2016 Google announced it would stop running Flash display ads on its network from January 2, 2017. Making Flash click-to-play in Chrome extends that pressure from Google's own properties to every site on the web.
The later coverage confirms Google executed on schedule — a September block of behind-the-scenes Flash content, then Chrome 55 shipping in December with HTML5 as the default, keeping only Flash-only sites and the top 10 exempted — and that the move set a template rivals copied.
First-order effects
- Sites still serving central content in Flash face an immediate choice when Chrome flips the default: convert to HTML5 or accept that most visitors hit a click-to-play prompt instead of their content.
- The ten whitelisted top Flash-dependent sites get a temporary reprieve, but everyone else loses passive plugin loading overnight.
Second-order effects
- Microsoft followed within weeks — the next version of Edge blocks Flash by default and loads HTML5 where available, also exempting popular sites — so publishers converting for Chrome get cross-browser cover rather than doing the work twice.
- With Google's own ad network cutting off Flash display ads on January 2, 2017, agencies and advertisers have no demand-side reason left to build Flash creatives, accelerating the inventory shift to HTML5.
Third-order effects
- Browser vendors are now the de facto arbiters of which web technologies live or die — a single default flip retires a plugin ecosystem without any standards body vote, and the whitelist mechanism shows they'll manage transitions by exception rather than by spec.
- If the pattern holds, plugin-based web content gives way entirely to built-in browser capabilities, concentrating more power over the open web's feature set in the hands of Chrome and whoever matches its defaults.
The trend: Browser defaults are replacing standards committees and market adoption as the mechanism that kills legacy web plugins, with Chrome setting the pace and Edge ratifying it.