Download 42.0.2311.90 from the Chrome Stable for macOS
Download Google Chrome 42.0.2311.90 with the branch, platform, release date, and file size shown clearly on the same page.
What users usually want to know first
Release overview
Google Chrome 42.0.2311.90 is available here as part of the macOS Stable archive. Use this release page when you want the exact version, the current package details, and quick access to the correct installer.
据最新消息，Chrome 42于日前上线，正式将面向大众。新版本的更新将同时适用于Mac、Windows和Linux系统。该版本中包含了大量的问题修复以及功能上的改进，其中包括了：
1、新增海量应用扩展和Web平台API
2、大幅提升软件性能和稳定性
3、“生命、宇宙以及万事终极答案”（根据道格拉斯-亚当斯的小说《银河系漫游指南》，42是“生命、宇宙以及任何事情的终极答案”。因此，42也经常被用来向这一作品致敬。——维基百科）
4、内置Adobe Flash Player已更新至17.0.0.169，另外Chrome 42已正式停止对NPAPI插件的支持，现在默认安装仅支持5款PPAPI插件。临时解决方案可点此查看。
据Chome博客，该版本在新应用、扩展和包括Push API在内的Web Platform APIs都进行了改进。有国外媒体指出，在获得用户许可之后，用户关闭网页后依然可以接收到推送消息。对开发者来说，则能够使用Google Cloud Messaging服务来连接到service worker （在浏览器后台运行的服务脚本，和网页独立区分）来实现推送这些通知。
另外，根据Chrome团队博文中透露的信息本次新版中改善了浏览器的稳定性能，并修复了45项BUG。
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.