Chrome

Jump to How Tos Articles

'Chrome' How Tos

How to Export Your Passwords and Login Data From Google Chrome

In Chrome 66, rolling out now for Mac and iOS, Google has added a password export option to the web browser so that you can easily migrate your login details to another browser via a third-party password manager app. In this article, we'll show you how to export your passwords from Chrome on Mac and iOS. At the end of the process, you'll be left with a CSV file containing all your login credentials. Popular password managers like Enpass and 1Password accept CSV files for importing login data. Just be aware that the CSV file you export from Chrome is in plain text. That means your credentials could be read by anyone with access to it, so make sure you securely delete the file once you've imported the data into your password manager of choice.

'Chrome' Articles

Google Chrome 66 Browser Adds Default Mute Autoplay Feature, Password Export, and More

Google is currently rolling out its Chrome 66 update to users of the web browser on Mac and iOS. The Mac version now mutes autoplaying content by default, while both desktop and mobile versions include a passwords export option, security improvements and new developer features. Mute autoplay was originally slated for Chrome 64, which introduced autoplay settings on a per-site basis, but the function got pushed back for unspecified reasons. However, Chrome 66 now rolls out the default behavior for all users, and feeds into Google's wider intention to make the media playback experience more consistent when users navigate the web. Going forward, web-hosted media can only automatically play if it has no audio, if the user interacted with the page during a previous browsing session, or if the user frequently plays media on the site. Similarly on mobile, media can only autoplay if the site was added to the Home Screen by the user. The new passwords export option was previously hidden in Chrome's backend flag menus, but Chrome 66 adds the option to the user-facing settings. That said, it's still not obvious how to generate the CSV file containing your login credentials, so we've published a separate how-to article that goes through the process step by step. As for enhancing security, Chrome 66 follows through on Google's plan to deprecate Symantec-issued certificates, after the company failed to comply with industry security standards. The decision to end its trust for Symantec certificates was made when certificates for example.com and variations of test.com escaped

Google Removes Chrome Apps Section From the Chrome Browser Web Store

Google has shuttered the Chrome Apps section of its Chrome browser web store, following through on an announcement the company made more than a year ago. As of Wednesday, the Apps selection no longer appeared in the web store's search panel filters below Extensions and Themes. Prior to yesterday's removal, Chrome apps were available in two flavors: packaged apps and hosted apps. As Ars Technica notes, hosted apps were little more than desktop bookmarks, but they gave Chrome OS users a way to pin important web pages to certain parts of the GUI. Packaged apps, which first appeared on Mac in 2013, could be downloaded into the Applications folder where they were designed to function like native Mac apps, working offline, updating automatically, and syncing on any computer where a user was signed into Chrome. By 2016, Google had decided they were no longer worth the resources, because only around 1 percent of users across Windows, Mac, and Linux actively used Chrome packaged apps, and by that time the functionality of most hosted apps had been implemented as regular web apps. This week, Google began sending out emails to Chrome app developers informing them that Chrome Apps are now deprecated, and that the functionality of already installed apps will end early next year. As a replacement, Google is moving developers towards Progressive Web Apps (PWAs). The hybrid software was launched earlier this year on Android and brings similar app features to websites, including push notifications and offline sync. Apple has already started building support for PWAs into

Chrome Browser Updates Coming to Prevent Unexpected Web Page Redirects

Google this week revealed some upcoming enhancements to its Chrome browser that aim to protect users from encountering unwanted content on the web, such as when a site unexpectedly redirects them to another page when they click on a video play button. Google says that incidents of users being redirected by websites to unintended destinations are mentioned in 1 of every 5 Chrome feedback reports it receives, and it's now intent on putting a stop to the "abusive" behavior. One piece of feedback we regularly hear from users is that a page will unexpectedly navigate to a new page, for seemingly no reason. We've found that this redirect often comes from third-party content embedded in the page, and the page author didn't intend the redirect to happen at all. To address this, in Chrome 64 all redirects originating from third-party iframes will show an infobar instead of redirecting, unless the user had been interacting with that frame. This will keep the user on the page they were reading, and prevent those surprising redirects.Another example that Google says causes user frustration is when clicking a link opens the desired destination in a new tab, but the main window navigates to a different, unwanted page. The behavior is designed to circumvent pop-up blockers, but Google is planning a clampdown. Staring in Chrome 65, the browser will detect this abusive behavior, trigger an infobar, and prevent the main tab from being redirected, allowing the user to continue on to their intended destination. Lastly, starting in early January, Chrome's pop-up blocker will

Google Chrome for iOS Updated With Drag and Drop Support, New Today Widgets

Google yesterday updated its Chrome for iOS app, which serves as an alternate browser option for those who would prefer to use Chrome instead of the default Safari browser. The latest version of Chrome includes support for the iOS 11 Drag and Drop feature on the iPad, allowing iPad users to drag a URL from Chrome into another app or vice versa. Also included in the update are new Today widgets, which can be accessed by swiping right on an iPhone or iPad to get to the Today view and then choosing "Edit" to access available widgets. The two new widgets are "Quick Actions" and Suggested Sites." Quick Actions offers access to a new search, an incognito search, a voice search, or an option to scan a QR code, plus it includes an area that lists your most recently copied link. Suggested Sites offers site suggestions based on browsing habits.What's New in Version 62.0.3202.60 - Check out Chrome's two new Today widgets. You will need to add them by tapping the Edit button at the bottom of the iOS Search screen - On iOS 11 iPads, you can now drag a URL from another app and drop it into Chrome's omnibox or the tab strip, or from Chrome's content area to another appChrome can be downloaded from the App Store for free. [Direct Link]

Fake Chrome Web Browser Extension Unwittingly Installed by 37,000 Users

A fraudulent browser extension was downloaded by 37,000 Chrome users after it sneaked past Google's Web Store vetting processes, it emerged on Tuesday. The fake extension was listed on the official Web Store until today and masqueraded as popular legitimate extension AdBlock Plus, which has over 10 million users. Once installed, the fake reportedly swamps infected computers with adverts and opens up tabs without the user's permission. The existence of the fake extension was revealed by anonymous cyber security personality @SwiftOnSecurity, but it's still not entirely clear if the fake compromised the data of the 37,000-odd users who inadvertently installed it on their browsers. Back in 2015, Google officially blocked Mac users from downloading Chrome extensions not hosted in its official Web Store, over concerns that malicious extensions were becoming rife. Given this latest breach of Google's vetting system, Chrome users are advised to carefully check the developer information of extensions before downloading them to ensure they are legitimate and not spoofing popular browser add-ons. We'll update this article if Google provides clarity on what went wrong this time

Google Chrome Desktop Browser to Introduce Autoplay Blocking Features

Google will follow Apple's lead by adding an autoplay blocking feature to its desktop web browser in an update set to arrive in January, the company announced on Thursday. One of the most common irritations of web browsing is unexpected media playback, which can eat up data allowance, consume more power, and cause unwanted noise. When Safari 11 is released as part of macOS High Sierra, Mac users will be able to control media playback settings on a per-site basis, ending the frustration of auto-playing media while browsing. Starting in Chrome 64, Google's desktop browser will feature a customization option along the same lines. In a post on its Chromium blog, Google said that with the new settings, autoplay will only be allowed if the media on a website doesn't play sound, or if the user has frequently chosen to play media on the site before. This will allow autoplay to occur when users want media to play, and respect users' wishes when they don't. These changes will also unify desktop and mobile web behavior, making web media development more predictable across platforms and browsers.Since not all users have the same preferences for autoplaying media, Google said it would add a new user option in Chrome 63 to completely disable audio for individual sites that will persist between browsing sessions. Based on the available evidence, Chrome's autoplay blocking options won't actually be as granular as Safari's, which will enable users to mute autoplaying media with sound, or block all autoplaying media completely, both for individual sites and globally.

Sling TV Debuts Desktop In-Browser Player for Google Chrome

Sling TV announced its first in-browser desktop content player on Tuesday. Using the latest version of Google Chrome, subscribers to the streaming television platform can log in at sling.com to access their favorite content and start playback right from within the browser. It's not yet clear at what quality the content is played within the browser, but Sling TV customers watching on Google Chrome do get access to popular features like "My TV", the "Continue Watching" ribbon, account settings, parental controls, and more. Sling TV cautions that the Chrome in-browser player is still a beta version, but no app, plug-in or flash player download is necessary. The service says it will continue to roll out additional features as the browser player matures, including access to cloud DVR and a grid guide. For more information on Sling TV-supported devices, visit sling.com/devices.

Chrome 60 Update Brings Touch Bar Support for New MacBook Pro Models

Google today released Chrome 60, introducing support for the Touch Bar built into 2016 and 2017 13 and 15-inch MacBook Pro models. After installing Chrome 60, MacBook Pro owners are able to add, remove, and rearrange Chrome shortcuts. The Touch Bar settings can be accessed by through the Menu bar by going to View -> Customize Touch Bar. The new settings can be combined with existing Touch Bar options for things like controlling brightness and volume, and there's a toggle for turning off predictive typing suggestions. Today's update also includes a long list of security fixes, which are listed in the Chrome release notes, and new and updated Web Budget, Payment Request, Paint Timing, and Credential Management APIs for developers. Also new is support for the CSS @font-face descriptor and font-display property for faster font loading on websites. The new version of the Chrome browser can be downloaded from the Chrome website.

Google Confirms Ad-Blocking Feature Coming to Chrome in Early 2018

Google will introduce an ad-blocking feature in both its mobile and desktop Chrome web browsers early next year, according to the company. Thursday's announcement confirms rumors back in April that the tech giant was seriously considering the feature for Chrome, and provided more details on Google's motives behind the move. In a blog post, Sridhar Ramaswamy, Senior VP of Ads and Commerce, said Google wanted to "build a better web for everyone" by eradicating intrusive ads online without removing all ads entirely, since so many sites rely on ads as their source of revenue. The vast majority of online content creators fund their work with advertising. That means they want the ads that run on their sites to be compelling, useful and engaging--ones that people actually want to see and interact with. But the reality is, it’s far too common that people encounter annoying, intrusive ads on the web--like the kind that blare music unexpectedly, or force you to wait 10 seconds before you can see the content on the page. These frustrating experiences can lead some people to block all ads--taking a big toll on the content creators, journalists, web developers and videographers who depend on ads to fund their content creation. Google said efforts to find a solution to the problem involved several steps, one of which is the ad blocking software, or "ad filter". Chrome's ad filter won't block all ads, but only those that are classified as intrusive or annoying. To help with its classifications, Google said it had joined the Coalition for Better Ads, an industry group dedicated to

Google Could Include Ad-Blocker in Future Versions of Chrome Browser

Google is planning to introduce an ad-blocking feature in both the mobile and desktop versions of its Chrome web browser, according to sources who spoke to The Wall Street Journal. The feature could be turned on by default within Chrome and would be designed to filter out certain online ad types that result in poor user experiences on the web, as defined by industry group the Coalition for Better Ads. According to the coalition's standards, ad formats like pop-ups, auto-playing ads with audio, and ads with countdown timers fall under "a threshold of consumer acceptability" and could therefore be targets of any blocker. Google could announce the feature within weeks, according to the paper's sources, but it is still working out specific details and could still decide to reverse course and can the feature. One possible implementation of the filter includes blocking all advertising on a website if it hosts just one offending ad, ensuring a set standard is kept by website owners. Another option is to target specific ads. For a company that generated over $60 billion in revenue from online advertising in 2016, the feature would seem a surprise move. However Google appears to be reacting against the growth of third-party blocking tools – some of which charge fees to let ads pass through their filters – by considering offering its own solution, which would let it control which ads pass through filters. In the U.S., Chrome commands nearly half of the browser market across all platforms, according to online analytics provider StatCounter.

YouTube Dark Mode Surfaces in Latest Desktop Chrome Browser Update

Google appears to be testing a Dark Mode feature for YouTube in the latest version of its Chrome 57 desktop browser. The built-in mode was discovered on Thursday and shared in a Reddit post, and while the setting doesn't appear by default, a quick command in the developer console is all that's required to enable it. YouTube Dark Mode in Chrome with black theme enabled Follow these steps to enable the YouTube dark mode in Chrome on Mac. Make sure you're signed in to YouTube before performing the steps. Press the keyboard combination shortcut Option + Command + I to open the developer tools sidebar. Click the Console tab. Paste document.cookie="VISITOR_INFO1_LIVE=fPQ4jCL6EiE" into the console and press enter. Close the developer tools sidebar and refresh the YouTube page. Click your YouTube profile picture, select Dark Mode from the dropdown, and toggle the switch to enable the mode. Google Chrome is available to download for free on the Chrome website. [Direct Link]

Chrome Browser Gains 'Scroll Anchoring' to Prevent Annoying Web Page Jumps

Google yesterday announced a new feature in the latest update to its Chrome browser that aims to make the progressive loading of web pages less jumpy and annoying. The idea behind progressive loading is to allow users to begin consuming web content immediately before the page has fully loaded, but the offscreen loading of pictures and so on can cause unexpected page jumps and push down what's already on screen, making for a frustrating experience, especially on mobile devices. Google's answer to this problem is something called Scroll Anchoring. Similar to other features designed to protect our users from bad experiences, starting in version 56 Chrome prevents these unexpected page jumps with a new feature called scroll anchoring. This feature works by locking the scroll position on an on-screen element to keep our users in the same spot even as offscreen content continues to load. Google claims scroll anchoring is already preventing about three page jumps per page-view, but says it understands there might be some content for which scroll anchoring is either unwanted or misbehaving. For this reason, the feature ships alongside a CSS property to override it. While the focus of this feature is on mobile, scroll anchoring is actually also on by default on Chrome for Mac. Meanwhile, Google is encouraging web developers to participate in a community group to discuss the feature's functionality, offer feedback, and learn how to design websites or services "with a no-reflow mindset". Google Chrome is available to download for free on the App Store. [Direct Link]

Chrome 57 Reduces Desktop Power Consumption By Throttling Background Tabs

Version 57 of the desktop Chrome web browser includes a new CPU throttling feature that Google says will lead to 25 percent fewer busy background tabs and help reduce overall power consumption. Charges that Chrome is a battery hog have long dogged Google's browser, leading the company to make efficient power usage a key pillar in its long-term development strategy for the software. Throttling background tabs by limiting Javascript timers is the latest attempt by Google to improve the browser's reputation. Javascript timers are often used by news sites and social media networks to update web page content in tabs, which uses up valuable CPU cycles. From version 57 of the browser, Chrome will delay timers in individual background tabs if their power usage oversteps the mark. Tabs that play audio or use real-time connections won't be affected, however. Chrome has focused on improving the user experience by throttling tab performance for many years. Like many browsers, Chrome has limited timers in the background to only run once per second. Via the new throttling policy, Chrome 57 will delay timers to limit average CPU load to 1% of a core if an application uses too much CPU in background. Tabs playing audio or maintaining real-time connections like WebSockets or WebRTC won’t be affected. According to Google, the new throttling mechanism leads to fewer busy background tabs, which typically consume a third of Chrome's power usage on desktop computers. In the long term, Google aims to fully suspend timers in background tabs and instead rely on new APIs to do the work

Latest Chrome Canary Build Includes Support for MacBook Pro Touch Bar

The newest build (58.0.3020.0) of Chrome Canary, Google's experimental browser, includes support for the Touch Bar built into the 2016 MacBook Pro, indicating Touch Bar support will soon be added to the Chrome browser. On the Touch Bar, the current Chrome Canary build offers a search/URL bar, forward and back buttons, a refresh/stop option, a button for opening a new tab, and a button for adding a new bookmark. It's much a simpler implementation than Touch Bar support in Safari, which includes preview tabs for quickly switching between windows. There are also no controls available for video or music playback in the browser. Features are tested in Canary before being added release builds of the Google Chrome browser, so Touch Bar support is expected in Chrome 58, set to be released during the week of April 25th. Those who want to give Touch Bar support a try ahead of the release of Chrome 58 can download Chrome Canary from Google.

Google Makes Chrome Browser for iOS Open Source

Google today announced that the code for Chrome for iOS is being added to its Chromium project and will be available through the company's open-source repository going forward. According to Google, Chrome for iOS was previously kept separate from the rest of the Chromium project because of the "additional complexity" required for the platform, such as the need for the browser to be built using the WebKit rendering engine. Google says the company's engineers have spent "a lot of time" over the last few years tweaking the Chrome for iOS code needed to upstream into Chromium, a process that was recently completed.Today, that upstreaming is complete, and developers can compile the iOS version of Chromium like they can for other versions of Chromium. Development speed is also faster now that all of the tests for Chrome for iOS are available to the entire Chromium community and automatically run any time that code is checked in.Designed as an alternative to Safari, Chrome for iOS is available for free to all users from the iOS App Store. [Direct Link] Chrome users won't notice any obvious changes to the browser, but the shift to open source will make it easier for Google to release new versions of Chrome for

Chrome 56 Offers Faster Reloads, Better Security, Lower Power Usage, and More

Version 56 of Google Chrome browser started rolling out to Macs today, bringing with it several new security enhancements, lower power consumption, and a performance boost. To begin with, Chrome now presents a clearer warning to users when a website requests password or credit card information over a non-HTTPS, unsecure connection. Chrome 56 is also the first version to make HTML5 the default standard for all users, with Flash content automatically blocked by the browser. Support for the HTTPS-secure Web Bluetooth API has also been included, allowing websites to connect to Bluetooth Low Energy (BLE) devices like printers and lightbulbs for a more interactive online experience. Chrome 56 also brings 51 additional security fixes to the browser. According to a Google blog post, in the latest version of Chrome, changes to page reload behavior now produce reloads that are 28 percent faster and result in 60 percent less validation requests. The new behavior is said to maximize the reuse of cached resources which results in lower latency, power consumption, and data usage. In addition, Chrome 56 brings built-in FLAC support for the first time, meaning users of the (non-iTunes compatible) audio format can listen to tracks from within the browser. Lastly, in an attempt to deal with resource hogging Chrome tabs, Google has introduced a new Browser Timer feature that automatically throttles background pages overstepping their allotted runtime allowance, provided they aren't playing media. Chrome 56 is available to download for Mac users now. Existing users can

Google Chrome Browser 55 Fixes Security Holes and Defaults to HTML5

Google this week began rolling out the latest update to its desktop Chrome web browser ahead of schedule, with Chrome 55 fixing multiple security vulnerabilities and defaulting to HTML5 on the majority of websites. Google Chrome has been phasing out Flash support since September, when version 53 of the browser started blocking Flash-based page analytics and background elements. Version 54 brought a YouTube code rewrite that forced YouTube Flash players to switch to HTML5. Chrome 55 brings the most visible move away from Flash by defaulting to HTML5 across the board. Users are now prompted to enable Flash when they visit sites that still use it, exempting 10 of the most popular sites on the web, including Facebook and Amazon. Chrome 55.0.2883.75 for Mac contains a number of other fixes and improvements, including 26 patches identified by external researchers as part of Google's bug bounty program, and another 10 security fixes implemented by Google itself. The addition of CSS automatic hyphenation means Chrome can now hyphenate words when line-wrapping, which improves the visual appearance of text blocks. Chrome 55 should be available to download for most Mac users now. Existing users can update by selecting Chrome -> Preferences via the menu bar and clicking the About section. Users downloading Chrome for the first time will automatically receive the updated version from the Chrome download page. An update for the iOS browser app is expected soon.

Google Chrome 55 Will Have Memory-Optimization Features for Faster Browsing

Google has announced that an update coming to its website browser, Chrome, will include an upgraded JavaScript engine to aid in reducing the memory usage on websites that were programmed using JavaScript (via CNET). Planned for launch on December 6, Chrome 55 will see performance improvements predominantly if a device doesn't have much memory to start with (such as low-cost smartphones), and if a user runs Chrome with multiple tabs or other apps open at the same time. Google's V8 JavaScript engine team said it has "significantly reduced the memory footprint of several websites," helping to improve performance on the browser. These websites include The New York Times, Reddit, YouTube, and others, and were all picked to gauge Chrome's specific enhanced performance features. The team discovered that Chrome used a total of 50 percent less of a device's RAM on average in comparison to Chrome 53, which updated in September to emphasize HTML5 content over Adobe Flash. Most noticeably, the average V8 heap memory consumption of the mobile New York Times benchmark reduced by about 66%. Overall, we observed a 50% reduction of average V8 heap size on this set of benchmarks. Another optimization introduced recently not only reduces memory on low-memory devices but beefier mobile and desktop machines. Reducing the V8 heap page size from 1M to 512KB results in a smaller memory footprint when not many live objects are present and lower overall memory fragmentation up to 2x. It also allows V8 to perform more compaction work since smaller work chunks allow more work to be done

Google Chrome 53 Browser to Block Flash Content By Default

Google announced yesterday that it will "de-emphasize" Adobe Flash in its Chrome browser in favor of HTML5 from next month. As of Chrome 53, whenever the web browser comes across a site that loads Flash "behind the scenes" it will block the offending content and switch to the faster HTML5 web standard whenever it is available. Google notified users of the change to its browser's behavior ahead of time in a blog post: Today, more than 90% of Flash on the web loads behind the scenes to support things like page analytics. This kind of Flash slows you down, and starting this September, Chrome 53 will begin to block it. HTML5 is much lighter and faster, and publishers are switching over to speed up page loading and save you more battery life. You'll see an improvement in responsiveness and efficiency for many sites.In December, Chrome 55 will make HTML5 the default experience, except for sites which only support Flash, in which case users will be prompted to enable it on initial visit. The move is another nail in the coffin for Adobe's web standard, which used to serve the majority of online media content before former Apple CEO Steve Jobs decided not to support it on the iPhone. In Safari 10, set to ship with macOS Sierra, Apple plans to disable Flash by default, along with Java, Silverlight, and QuickTime, in an effort to focus on HTML5 content and improve the overall web browsing experience. The plug-in has long been problematic for Apple, requiring frequent security fixes and forced updates to patch a stream of vulnerabilities. Chrome can be

Google Testing Support for Native OS X Notifications in Chrome

Google's Chrome browser has long supported push notifications, but it's always used its own notification center instead of relying on the OS X Notification Center that was built into Apple's operating system in 2012. That may change in the near future, as Google is experimenting with the built-in OS X Notification Center. Available to all Chrome users as an experimental feature, OS X notifications can be turned on in the current version of the Chrome browser by inserting "chrome://flags/#enable-native-notifications" in the address bar and choosing the "enable" option. It should be noted that a more current version of the feature is available through Chrome Canary, as the implementation on the release browser is 6-12 weeks behind the current state of development. Native OS X notifications are more visually attractive than standard Chrome notifications and they're also listed in the Notification Center window, something that wasn't possible with Chrome notifications. OS X notifications coming from Chrome will also obey Do Not Disturb settings. As The Next Web points out, the Notification Center feature is still in active development so users who choose to turn it on could run into some bugs. Google developers say work on OS X Notification Center integration is being actively pursued, but it is not "100% clear either way" whether support will become official as "certain roadblocks" could potentially prevent that from