Download 75.0.3770.80 from the Chrome Stable for Windows 32-bit
Download Google Chrome 75.0.3770.80 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 75.0.3770.80
Google Chrome 75.0.3770.80 is available here as part of the Windows 32-bit Stable archive. Use this release page when you want the exact version, the current package details, and quick access to the correct installer.
Change log
This covers only some of the key highlights, check the links below for additional changes in Chrome 75.
- What's new in Chrome DevTools (75)
- Chrome 75 deprecations & removals
- ChromeStatus.com updates for Chrome 75
- What's new in JavaScript in Chrome 75
- Chromium source repository change list
Hint for low latency canvas contexts

Drawing on screen with the canvas element requires the page to synchronize graphics updates with the DOM. This synchronization can sometimes cause latency. For example, in a drawing app, latencies longer than 50 milliseconds can interfere with hand-eye coordination, making them difficult to use.
The desynchronized hint, when creating a canvas context, uses a different code path, that bypasses the usual DOM update mechanism. The hint tells the system to skip as much compositing as it can. In some cases, the canvas's underlying buffer is sent directly to the screen's display controller. This eliminates the latency that would be caused by using the renderer compositor queue.
Using the desynchronized hint is simple, just add desynchronized: true to the options object when creating the canvas.
Check out Joe's article Low-latency rendering with the desynchronized hint for more details, including how to do feature detection for it.
Share files with the Web Share API
The Web Share API allows you to plug into the share service provided by the OS, making it easy to share web pages and apps with other installed apps on the user's device.
In Chrome 75, the Web Share API now supports the sharing of files! I'm particularly excited about this because it makes it way easier for apps to share photos, videos and more. Squoosh is adding support for this to share a file once you've finished compressing it. The Web Share API currently supports the sharing of audio files, images, videos, and text documents.
It's best to use feature detection to see if the Web Share API is supported, and fallback to your traditional mechanism if it's not. And you can use navigator.canShare to check if file sharing is supported.
If navigator.canShare returns true, sharing of those files is supported, so you can call navigator.share, and pass an object with the array of files you want to share. Chrome will open the system share sheet and give you a list of installed apps that you can share the files to.
Try the demo and check out the article Share files with Web Share for complete details.
Numeric separators
Numeric literals now allow underscores (_, U+005F) as separators to make them more readable. For example, 1_000_000_000 will be interpreted by mathematical operations as equivalent to 1000000000.
Underscores can only appear between digits, and consecutive underscores are not allowed. So literals such as 3._14, _2.71 or 1.6__2 are illegal.
Google I/O 2019 is a wrap
If you didn't make it to I/O, or maybe you did, and didn't see all the talks, they're all up on the Chrome Developers YouTube channel, in the Web at Google I/O 2019 playlist.
- Tom and I presented "Unlocking new capabilities for the web" covering some of the amazing new capabilities that are landing in browsers this year.
- Addy and Katie covered some cool performance tips and tricks in "Speed at Scale".
- Elizabeth and Paul dove into some cool devtools in "Demystifying Speed Tooling".
- And in "Build Fast and Smooth Web Apps from Feature Phone to Desktop" Mariko showed us how she and her crew built Proxx to work on any device, from feature phone to smart phone to desktop. If you haven't tried Proxx yet, it's a super fun mine sweeper clone.
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.