Google Chrome Support For Flash Ads Ends Sept. 1

Google's Chrome browser will no longer support Flash-based ads starting Sept. 1. This follows several months of problems with Adobe's Flash platform.

Larry Loeb, Blogger, Informationweek

August 31, 2015

3 Min Read
<p align="left">(Image: gmutlu/iStockphoto)</p>

9 Reasons Flash Must Die, And Soon

9 Reasons Flash Must Die, And Soon

9 Reasons Flash Must Die, And Soon (Click image for larger view and slideshow.)

Google's Chrome browser will be blocking Adobe Flash content as of Tuesday, Sept. 1. This comes on the heels of Amazon's announcement that it would no longer support Flash-based ads on its websites.

Chrome has a 27% share of the total browser market, so this is a major hit to Adobe Flash.

This change in Chrome first showed up in a June 4 Google Adwords blog posting about a new setting in the browser that affected Flash content. In the post, Google wrote that it was "designed to increase page-load speed and reduce power consumption by pausing certain plugin content, including many Flash ads."

Google also noted in the post, "As soon as September, this setting will be turned on by default so Chrome users can enjoy faster performance and view more content before charging their batteries."

September has arrived.

Conceptually, this is very similar to a feature Apple uses in Safari. Flash is blocked from autoplaying content, and a "power saving" button requires a click to activate Flash.

The feature already exists in Chrome. It can be switched on by opening "advanced settings," under "content settings," then choosing the "detect and run important plugin content" option. Now it will be on by default.

Chrome won't pause all Flash content with this action. Flash video will not be paused, because it is considered "important," but the Flash items that surround that video -- which are usually ads -- will be paused.

Google's true motivation in this move may not be faster performance and better battery life -- not those.

The rise of malvertising attacks, in which malicious code can be injected into a user’s machine simply by viewing an image, that were using Flash as an entry vector undoubtedly played a part in this.

Google's revenues come from ads. Anything that might cause users not to view them or click on them hits it right in its bottom line. Consequently, the company views the Flash problem as a serious one, and it has taken some serious action to mitigate it.

Google has been fairly open about giving advertisers a way around Flash.

For example, AdWords can convert Flash to HTML5 code. As Google put it, "Eligible Flash campaigns, both existing and new, are now automatically converted to HTML5 when uploaded through AdWords, AdWords Editor, and many 3rd party tools."

[Read more about handy HTML5 tips you can use.]

There are free tools to allow pre-upload testing to see if an ad can be automatically converted.

Google will also encourage advertiser creation of HTML5 code with supported tools for this purpose.

Google Web Designer is one of these tools that work directly with the Google Display Network. Google has also provided non-Flash templates for use by advertisers.

About the Author(s)

Larry Loeb

Blogger, Informationweek

Larry Loeb has written for many of the last century's major "dead tree" computer magazines, having been, among other things, a consulting editor for BYTE magazine and senior editor for the launch of WebWeek. He has written a book on the Secure Electronic Transaction Internet protocol. His latest book has the commercially obligatory title of Hack Proofing XML. He's been online since uucp "bang" addressing (where the world existed relative to !decvax), serving as editor of the Macintosh Exchange on BIX and the VARBusiness Exchange. His first Mac had 128 KB of memory, which was a big step up from his first 1130, which had 4 KB, as did his first 1401. You can e-mail him at [email protected].

Never Miss a Beat: Get a snapshot of the issues affecting the IT industry straight to your inbox.

You May Also Like

More Insights