Download 45.0.2454.85 from the Chrome Stable for Linux
Download Google Chrome 45.0.2454.85 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 45.0.2454.85
Google Chrome 45.0.2454.85 is available here as part of the Linux Stable archive. Use this release page when you want the exact version, the current package details, and quick access to the correct installer.
Chrome 45.0.2454.85 is part of the Chrome 45 release line. Check the official update below for the published security, stability, and platform details.
New ES2015 features
Service worker improvements
- Developers are now able to measure their service worker’s performance using the User Timing and Resource Timing APIs.
- Service workers used exclusively to send push notifications are now kept up-to-date correctly and developers can also use the new update method to manually trigger an update check.
- Sites can now use getRegistrations() to access all the service workers whose scope matches the current page.
Media controls in Android notifications
Other updates in this release
- Sites can now customize the vibration triggered when showing a notification on Android.
- Chrome’s implementation of the Push API has undergone several minor breaking changes to keep up to date with the evolving specification.
- Sites using promoted add to home screen can now programmatically control the timing of the banner.
- The rotationAngle attribute of Touch objects is no longer prefixed, making it easier for sites to understand the geometry of the user's touch with cross-browser code.
- To improve scroll performance on pages with heavy mouse handlers or :hover styles, Chrome no longer sends mouse position updates when the user is scrolling with a trackpad or scrollwheel.
- Chrome now immediately prefetches all HTML imports referenced by a page instead of waiting for scripts included higher in the document to finish executing, improving performance.
- Sites can now include 3rd-party resources on their site with reduced security risk by using a hash to ensure the integrity of 3rd-parties resources.
- To reduce the risk of certain types of attack, the 'self' source defined by Content Security Policy now excludes blob and filesystem URLs.
- The logjam attack is fixed in this release by deprecating the use of keys smaller than 1024 bits in Diffie-Hellman key exchanges, which may require developers to update their server’s TLS configuration.
- To improve cross-browser compatibility and specification compliance, CSSUnknownRule and CSSKeyframesRule.insertRule() are now deprecated with the latter now replaced by CSSKeyframesRule.appendRule().
- Sites using SMIL will now trigger deprecation warnings in the console, encouraging them to migrate to CSS Animations and Web Animations.
- This release deprecates both multiple shadow roots and shadow-piercing deep selectors following a unanimous decision by browser vendors at the Web Components April 2015 meeting.
- The MediaStream attributes label and ended are now deprecated in favor of id and active, while the stop() method is deprecated in favor of MediaStreamTrack.stop().
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.