Download 49.0.2623.75 from the Chrome Stable for Windows 32-bit
Download Google Chrome 49.0.2623.75 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 49.0.2623.75
Google Chrome 49.0.2623.75 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.
Chrome 49.0.2623.75 is part of the Chrome 49 release line. Check the official update below for the published security, stability, and platform details.
- With user consent, sites can record audio and video without relying on plugins by using the new MediaRecorder API.
- Developers can now control how fonts load using CSS font-display, improving page load speed.
- Sites can now detect which service worker client initiated a fetch request and return a specialized response using the FetchEvent.clientID attribute.
- Chrome now animates scrolling for discrete scrolling devices like mouse wheels, allowing for a smoother user experience.
- Chrome now more strictly protects secure cookies and allows developers to identify secure cookies using cookie prefixes.
- Sites can now prevent media from playing remotely using the disableRemotePlayback attribute as part of the Remote Playback API.
- Event.timeStamp is now a DOMHighResTimeStamp instead of a DOMTimeStamp, allowing for high-precision scroll latency and pointer velocity measurements.
- Promise rejection handling can now be tracked using the UnhandledRejection and RejectionHandled events.
- Developers can now interact with the GET parameters of a URL more easily using URLSearchParams.
- The WebAudio API now supports IIR Filters, OfflineAudioContext.suspend() and resume(), and promises in DecodeAudioData.
- WindowClient.navigate() allows service workers to navigate controlled windows to a new URL.
- Sites can detect if a user has requested reduced data usage and respond with a lighter experience by checking the Save-Data header field.
- Chrome’s content security policy now matches ‘script-src http:’ to both HTTP and HTTPS, preventing developers from accidentally rejecting secure resources.
- The Request.mode enum of the Fetch API now supports a navigate mode, improving spec compliance.
- Developers now have the option to ignore case when matching attribute selectors.
- Developers can now create pop-ups that don’t expose which page opened them using 'rel=noopener'.
- addEventListener() and removeEventListener() now require their first two arguments and can have the "capture" option specified using dictionary syntax, improving spec compliance and flexibility.
- Chromium now supports the standardized version of ChaCha-Poly1305 cipher suites in TLS.
- Navigator.getStorageUpdates() has been removed as it is no longer in the Navigator spec.
- MouseEvent.webkitMovementX/Y has been removed in favor of the unprefixed version.
- initTouchEvent has been deprecated in favor of the TouchEvent constructor to improve spec compliance and will be removed altogether in Chrome 53.
- Object.observe() has been deprecated as it is no longer on the standardization track and will be removed in a future release.
- The getComputedStyle(e).cssX behaviour has been deprecated since it was not a part of the formal spec.
- Some non-standard uses of RTCPeerConnection legacy methods have been deprecated to enable promise-based implementation of the WebRTC spec.
- Document.defaultCharset has been deprecated to improve spec compliance.
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.