Download 48.0.2564.82 from the Chrome Stable for Windows 64-bit
Download Google Chrome 48.0.2564.82 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 48.0.2564.82
Google Chrome 48.0.2564.82 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.
Chrome 48.0.2564.82 is part of the Chrome 48 release line. Check the official update below for the published security, stability, and platform details.
- The new DevTools security panel enables developers to understand the security state of a page to help them migrate their websites to HTTPS.
- Sites can now use FontFaceSet more flexibly with several new iteration methods.
- WebRTC now supports the VP9 video codec, and can serve HD video at almost half the bandwidth of VP8 or H264.
- Web Audio JavaScript syntax can now be shortened and simplified with method chaining for AudioNode.connect() and AudioParam.connect() automation methods.
- The MediaStreamTrack.remote attribute allows sites to detect if a media stream is from a remote source.
- Sites can now detect key presses from a user without worrying about browser type or operating system using the KeyboardEvent.code attribute.
- Developers can now leverage JavaScript language behaviors not previously exposed in ES5 or below using the well-known symbols @@isConcatSpreadable, @@toPrimitive.
- min-width:auto and min-height:auto now work for flex items without flex-basis:auto.
- Several getAll() methods have been added to IndexedDB to simplify bulk interactions.
- ServiceWorkerRegistration.update() no longer bypasses the cache for update checks within 24 hours, improving spec compliance.
- The error attribute on IDBRequest and IDBTransaction will now return DOMException instead of DOMError to improve Chrome's spec compliance.
- The RC4 cipher is no longer supported over HTTPS connections due to several vulnerabilities.
- The MediaStreamTrack.getSources() method has been deprecated in favor of MediaDevices.enumerateDevices().
- SVGGraphicsElement.getTransformToElement has been removed to match the SVG spec.
- getSVGDocument() has been removed from HTMLFrameElement.prototype to match the spec.
- SVG glyph-orientation-horizontal and glyph-orientation-vertical properties have been removed in favor of the CSS text-orientation property.
- SVGElement.offset* properties and SVGPathSeg interfaces have been removed to improve spec compliance.
- The CSS plus-darker composite operator has been removed to increase spec compliance.
- The item() method has been removed from TextTrackList and TextTrackCueList to improve spec compliance.
- Developers can now build robust RTL text experiences using CSS Writing Modes Level 3 without prefixes.
- CSS font-feature-settings are no longer prefixed.
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.