Download 91.0.4472.77 from the Chrome Stable for macOS

Google Chrome 91.0.4472.77 is available here as part of the macOS Stable archive. Use this release page when you want the exact version, the current package details, and quick access to the correct installer.

Suggested names for File System Access API

One of my favorite APIs to come out of the Fugu project this year is the File System Access APIs. Once the user has granted permission, apps can interact with files on the users local device, in the same way other installed apps do, allowing you to create a more natural user experience.

Starting in Chrome 91, you can now suggest the name and location of a file or directory to interact with. To do so, pass a suggestedName property as part of the showSaveFilePicker options.

The same goes for the default starting directory. For example, a text editor probably wants to start the file save or file open dialog in the documents folder. Whereas an image editor probably wants to start in the pictures folder. You can suggest a default start directory by passing a startIn property.

Check out Tom's File System Access post for complete details.

Reading files from the clipboard

There's one other cool new API for interacting with files that lands in Chrome 91. On desktop, web apps can now read files from the clipboard. (Reading files from the clipboard has been available in Safari since 2018.)

Of course, you don't get unrestricted access to the clipboard, so you'll need to set-up a paste event listener. Then, in the event handler, you can access the content of each file on the clipboard.

Share credentials on affiliated sites

If your site has multiple domains, and they share the same account management backend, you can now associate your sites with one another, allowing users to save credentials once, and have the Chrome password manager suggest them to any of your affiliated sites.

This is ideal when your site is served from different top level domains, like google.com, and google.ca. Or maybe you've got multiple domains names.

To associate your websites, you'll need to create an assetlinks.json file that defines the relationship between the domains. In the example below, I'm telling the browser that both the .com and .co.uk domains are related and can share the credentials.

Then, host the assetlinks.json file in the .well-known folder for each domain.

This functionality will start to roll out gradually in Chrome 91, and may not be available on day one, so check out Enable Chrome to share login credentials across affiliated sites for the latest details.

And more!

Of course there's plenty more.

All the videos from I/O 2021 are online now, there's some great content there, so check it out!

Web Transport-previously called Quic Transport has undergone a number of changes and is starting a new origin trial.

Web Assembly SIMD has finished its origin trial and is available to all users.

The refreshed form elements have finally landed on Android, improving the user experience.

And the <link> element's media attribute will be honored for link rel="icon", meaning you can define different icons based on media queries. For example a different icons for dark and light modes.

Official source: Official Chrome update

Installation notes

After downloading the package, confirm that the branch and platform match your device before launching the installer or extracting the archive. If you only need a standard everyday browser, Stable is usually the safest choice. If you are testing new behavior, Beta, Dev, and Canary are better fits.

Related release pages

For newer or older builds in the same branch, open the category archive linked above. For different platforms, use the related desktop archives in the sidebar.