Download 62.0.3202.62 from the Chrome Stable for Windows 64-bit
Download Google Chrome 62.0.3202.62 with the branch, platform, release date, and file size shown clearly on the same page.
What users usually want to know first
What changed in Chrome 62.0.3202.62
Google Chrome 62.0.3202.62 is available here as part of the Windows 64-bit Stable archive. Use this release page when you want the exact version, the current package details, and quick access to the correct installer.
Network Quality Indicator
The Network Information API has been available in Chrome for a while, but it only provides theoretical network speeds given the user's connection. Imagine you're on WiFi, but connected to a cellular hotspot that only has 2G speeds? The API would report WiFi!
In Chrome 62, the API has been expanded to provide actual network performance metrics from the client. Using these network quality signals, you can tailor content to the network. For example, on very slow connections, you could improve page load performance by serving a reduced version.
To simplify your application logic, the API returns the measured network performance in terms of how it would compare to a cellular connection. For example, connected to a super fast fiber connection, the API would report 4G.
These signals will also be available as HTTP request headers and enabled via Client Hints. Checkout out the sample and have a look at the spec for a deeper dive.
OpenType Variable Fonts
Traditionally, one font contained only a single instance of a font family, for example one weight or one stretch. If you wanted regular, bold and italic, you'd need to include three separate fonts, increasing the weight of your page.
An OpenType variable font is the equivalent of multiple individual fonts that can be compactly packaged within a single font file. By adjusting the font-variation-settings CSS property, stretch, style, weight and more, can easily be adjusted, providing an infinite number of stylistic variations. Those three fonts can now be combined into a single, compact file.
OpenType variable fonts gives us a powerful new tool to create responsive typography, and reduce our page weight. Check out Introducing OpenType Variable Fonts by John Hudson for more details.
Media capture from DOM elements
You can now live-capture content into a MediaStream directly from HTMLMediaElements like audio and video, with the Media Capture from DOM Elements API.
After invoking captureStream() on an HTML media element, the streamed content can be manipulated, processed, sent remotely or recorded. Imagine using web audio to create your own equalizer or vocoder. Or stream the content to a remote site using WebRTC. The possibilities are almost endless.
Not Secure labels for some HTTP pages
As we announced previously, starting in Chrome 62, when a user enters data on an HTTP page, Chrome will mark the page as "Not Secure" with a label in the address bar. This label will also be shown in Incognito Mode for all HTTP pages.
And more!
These are just a few of the changes in Chrome 62 for developers, of course, there's plenty more.
- The Payment Request API is now available on Chrome for iOS.
- You can start building experimental rich VR experiences with the WebVR origin trial.
Then subscribe to our YouTube channel, and you'll get an email notification whenever we launch a new video.
I'm Pete LePage, and as soon as Chrome 63 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.