v151 · Browser · Migration Guide
Migration Guide
Hardware compatibility, macOS upgrade paths, and enterprise fleet management guidance for the Chrome 151 removal of macOS 12 Monterey support.
Users who remain on macOS 12 after Chrome 151 ships will not receive further Chrome security updates. Staying current on Chrome requires upgrading to macOS 13 (Ventura) or later.
hardware compatibility
Hardware rows are loaded from hardware-compatibility.json so the data can be refreshed without editing the table markup.
| Mac model | Runs macOS 13 Ventura? | Action required |
|---|---|---|
| Loading hardware compatibility data… | ||
Chrome version support matrix
| macOS version | Last supported Chrome | Status |
|---|---|---|
| macOS 10.13 High Sierra | Chrome 116 | Dropped Chrome 117 |
| macOS 10.14 Mojave | Chrome 116 | Dropped Chrome 117 |
| macOS 10.15 Catalina | Chrome 130 | Dropped Chrome 131 |
| macOS 11 Big Sur | Chrome 139 | Dropped Chrome 140 |
| macOS 12 Monterey | Chrome 150 | Dropped Chrome 151 |
| macOS 13 Ventura | — | Supported |
| macOS 14 Sonoma | — | Supported |
| macOS 15 Sequoia | — | Supported |
enterprise fleet management
# Option 1: Detect via UA-CH in your web app and warn users
# Server-side: read Sec-CH-UA-Platform and Sec-CH-UA-Platform-Version headers
# (requires Accept-CH: Sec-CH-UA-Platform, Sec-CH-UA-Platform-Version response header)
# Option 2: Use Chrome Browser Cloud Management
# Policy: BrowserLabsSettings → manage minimum OS requirements
# Report on devices that cannot upgrade
# Option 3: Chromium enterprise policy
# ChromiumPolicy.json:
# "SuppressUnsupportedOSWarning": true ← temporarily suppresses warning
# Note: suppressing the warning does not restore security updates
# Option 4: Google Admin console → Devices → Chrome → Reports
# Filter by OS version to identify macOS 12 machines in your fleet
# Export to CSV and triage by hardware model for upgrade eligibilitysee also
scenario focus
Select a scenario to focus its rendered example and summary.
implementation reference
Need the exact API surface, compatibility boundaries, errors, lifecycle, and source links? Read the matching gendn reference ↗