Version article

Download 54.0.2840.59 from the Chrome Stable for macOS

Download Google Chrome 54.0.2840.59 with the branch, platform, release date, and file size shown clearly on the same page.

Stable macOS Published 2016-10-13
Version 54.0.2840.59
Release date 2016-10-13
Platform macOS
File size 60.44MB
Quick facts

What users usually want to know first

Branch Stable
Clicks

What changed in Chrome 54.0.2840.59

Google Chrome 54.0.2840.59 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.

Custom elements v1

Complex user interfaces often require a large amount of HTML. Most languages allow developers to create their own components built on top of language primitives to mitigate this kind of verbosity. But until now, creating reusable components on the web has been difficult.

Custom elements allow you to create your own custom HTML tags, and define the new element's API and behavior in JavaScript. The result, a browser-native way to build reusable, interoperable components.

Chrome 54 provides support for the latest custom elements V1 spec, and will continue to support the V0 API until enough of you have moved to V1.

Check out our primer on custom elements to how you can use it to create reusable web components for your site or application.

BroadcastChannel API

It is not uncommon for desktop users to have multiple windows or tabs open simultaneously, and some sites even encourage this behavior, such as web editors that open documents in their own tabs.

Communicating between those tabs can be difficult. The BroadcastChannel API is a new one-to-many messaging API between windows, tabs, iframes, web workers, and service workers. It allows scripts to establish named channels to send messages between browsing contexts of the same origin.

Other BroadcastChannel resources

requestFullScreen

Media is an increasingly important part of the browsing experience.

In addition to a user gesture, you can now use Element.requestFullScreen() to trigger full screen mode after a screen orientation change - and allows you to create richer media experiences that include rotate to full screen.

Foreign fetch

Imagine if a commonly used origin like an API provider, web font service or other service had the ability to deploy its own service worker.

Instead of always going to the network, the provider could implement their own custom networking logic, and take advantage of a single, authoritative cache instance for storing its responses.

Now, thanks to foreign fetch, which is available in Chrome 54 as an origin trial, it's a reality. Check out Jeffrey's post linked in the comments below!

Closing

These are just a few of the changes in Chrome 54 for developers.

Check the description for more details and links the documentation and specifications.

Oh, and don't forget to check out the Chrome Dev Summit, we'll be streaming it on YouTube on November 10th and 11th.

If you want to stay up to date with Chrome and know what's coming, click that Subscribe button up there.

I'm Pete LePage, and as soon as Chrome 55 is released, I'll be right here to tell you -- what's new in Chrome!

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.

Frequently asked questions

These FAQ blocks help the page read like a complete release article instead of a download stub, which is better for trust and better for SEO.

Should I use this release or stay on Stable?

If you just want the safest everyday browsing experience, Stable is usually the right default. Preview branches are better for testing, compatibility checks, and early feature access.

Why show exact version numbers so prominently?

Because exact-version queries are common in English search behavior, especially for QA teams, enterprise users, and people trying to reproduce a bug or environment.

Why keep a full article around the download buttons?

A stronger page body gives users context and gives Google clearer signals about what the release page actually covers.

Where should older releases live?

Older versions belong in the category archive page, with this article template handling exact-version landing pages one release at a time.