Percentage of Chrome users who've loaded at least one page containing Flash content per day has dropped from 80% in 2014 to under 8% today, according to Google
Catalin Cimpanu / BleepingComputer.com : Tweets: @davezatz . Thanks: @campuscodi Tweets: Dave Zatz / @davezatz : Uh huh, and what about IE8? http://twitter.com/... Thanks: @campuscodi
Context & Ripple Effects
This number is the scoreboard for a campaign Google has been running since at least 2015, when Chrome began automatically pausing less important Flash content. The squeeze tightened through 2016: first a click-to-play default with an exemption carved out for ten top Flash-reliant sites, then blocking 'behind the scenes' Flash outright, then Chrome 55 defaulting desktop rendering to HTML5 while exempting Flash-only sites.
First-order effects
- Publishers and ad networks still serving Flash now face a Chrome audience where fewer than 1 in 10 users loads any Flash page per day — their inventory is effectively invisible to the dominant browser without a rewrite.
- The small set of sites holding Flash-only exemptions from Google are now outliers whose traffic depends entirely on continued tolerance from one vendor.
Second-order effects
- Web development shops and CMS vendors can treat HTML5 migration as table stakes rather than a premium service, since the Flash fallback audience has collapsed below viability.
- Browser makers gain a proven playbook — degrade defaults gradually, exempt a handful of majors, publish usage stats — that lowers the political cost of killing other legacy technologies.
Third-order effects
- If the pattern holds, plugin-based web content follows the path of unmigrated archives: technically extant but practically unreachable unless ported, making browser defaults the de facto curator of what survives the web's format transitions.
The trend: Browser vendors are retiring plugin-era web technologies by resetting defaults rather than removing features, letting measured usage collapse justify each next restriction.