Download 72.0.3626.81 from the Chrome Stable for macOS
Download Google Chrome 72.0.3626.81 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 72.0.3626.81 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.
时隔一个半月，距离上个稳定版本71.0.3578.98，Google终于于2019年1月30日向公众发布了Chrome 72稳定版，最新版本号为72.0.3626.81。新版本的Chrome修补了58个大大小小的安全漏洞，并引入了其他一些更改或修复。
大多数Chrome用户都应自动获取更新，因为默认情况下配置浏览器以便在可用时下载并安装新更新。您可以在浏览器的地址栏中输入chrome://settings/help，对Google Chrome中的更新进行手动检查。
Chrome官方网站上也提供下载内容，但是建议您下载Chrome离线安装程序以避免.Net安装程序问题。
官方release说明仅强调安全修复程序，并未提及其他更改。此次更新修正了一个严重的安全问题，并提高了若干问题的评级。
Chrome修复了密码管理器逻辑，用于确定密码管理器是否可用。
默认情况下启用AV1解码器支持。
chrome://flags/#omnibox-ui-one-click-unelide，如果启用，则在通过键盘，鼠标或手势点击聚焦多功能框时执行unelision。
Removed option to set the default polling rate using the GamepadPollingRate flag. Google set it to 250 Hz and states that the flag is no longer necessary because of that.
桌面平台删除了“站点进程”标志，因为它默认情况下已启用且不再需要。
添加了画中画模式的重放按钮。
Android：chrome://flags上的gesture-nav标志，用于启用手势导航前后移动。
几个崩溃修复。
你已经更新到Chrome72了吗？你发现了什么重大变化吗？
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.