Have you noticed Chrome’s version numbers climbing past 100 and now reaching the 140s? With such frequent updates, you might wonder how long older versions receive security support. Understanding EOS (End of Support) and EOL (End of Life) schedules is crucial, especially in enterprise environments where maintaining specific versions for stability is common practice.
This guide provides comprehensive information about Google Chrome’s security support policy and detailed EOS/EOL schedules for all versions.
1. Understanding Google Chrome
Google Chrome, first released as a beta on September 2, 2008, has become the world’s most widely used web browser. It’s available across virtually every platform: Windows, macOS, Linux, Android, iOS, and ChromeOS.
Chrome’s defining characteristic is its rapid update cycle. A new major version is released every 4 weeks, with only the latest major release receiving new features, bug fixes, and security updates. This strategy enables Google to quickly patch security vulnerabilities and support the latest web standards.
While most of Chrome’s source code comes from the open-source Chromium project, Chrome itself is distributed as proprietary freeware. This is why many browsers like Edge, Brave, and Opera are built on the Chromium foundation.
2. Chrome Release Channels Explained
To properly manage Chrome, you need to understand release channels. Chrome offers 5 channels: Stable, Extended Stable, Beta, Dev, and Canary.
Stable Channel: The production-ready version used by general users. Major updates arrive every 4 weeks, with minor updates for security patches and critical bug fixes released every 2-3 weeks.
Extended Stable Channel: Designed for enterprise users, this channel provides major updates every 8 weeks while continuing to receive security fixes. Available only on Windows and Mac, it’s ideal for enterprise environments requiring reduced update frequency.
Beta Channel: Provides a 4-6 week preview of upcoming Stable features, allowing users to test new functionality and provide feedback.
Dev Channel: Updated 1-2 times weekly for developers. Less stable but provides earlier access to upcoming features.
Canary Channel: Daily builds with the latest development code. Highly experimental and potentially unstable, but offers the earliest access to new features.
3. Chrome’s Security Support Policy – Only the Latest Version
Chrome’s security support policy is straightforward: only the latest major version receives full support.
Chrome ships a new milestone (major version) to the stable channel every four weeks. Once released, the Stable channel receives weekly updates (refreshes) and the Extended Stable channel receives biweekly updates. These updates primarily contain important security fixes and urgent regression fixes.
For example, when Chrome 141 was released on October 14, 2025, Chrome 140’s security support ended. While this may seem like a brief support period, the automatic update feature ensures most users naturally maintain the latest version.
For the Extended Stable channel, every other milestone branch is maintained for an additional 4 weeks with important security fixes backported. However, complex or risky changes and larger security features like Site Isolation may not be viable to backport, so the stable channel is recommended for security-critical environments.
4. Complete Chrome Version EOS Schedule
Below is a comprehensive table of all Chrome major versions with their release dates and security end-of-support dates. For real-time updates, visit Chrome on endoflife.date.
2025 Latest Versions (Chrome 130-141)
| Version | Release Date | End of Support | Support Duration |
|---|---|---|---|
| Chrome 141 | October 14, 2025 | Currently Supported | – |
| Chrome 140 | September 2, 2025 | October 14, 2025 | ~6 weeks |
| Chrome 139 | August 5, 2025 | September 2, 2025 | ~4 weeks |
| Chrome 138 | June 24, 2025 | August 5, 2025 | ~6 weeks |
| Chrome 137 | May 27, 2025 | June 24, 2025 | ~4 weeks |
| Chrome 136 | April 29, 2025 | May 27, 2025 | ~4 weeks |
| Chrome 135 | April 1, 2025 | April 29, 2025 | ~4 weeks |
| Chrome 134 | March 4, 2025 | April 1, 2025 | ~4 weeks |
| Chrome 133 | February 4, 2025 | March 4, 2025 | ~4 weeks |
| Chrome 132 | January 14, 2025 | February 4, 2025 | ~3 weeks |
| Chrome 131 | November 12, 2024 | January 14, 2025 | ~9 weeks |
| Chrome 130 | October 15, 2024 | November 12, 2024 | ~4 weeks |
2024 Versions (Chrome 120-129)
| Version | Release Date | End of Support | Support Duration |
|---|---|---|---|
| Chrome 129 | September 17, 2024 | October 15, 2024 | ~4 weeks |
| Chrome 128 | August 20, 2024 | September 17, 2024 | ~4 weeks |
| Chrome 127 | July 23, 2024 | August 20, 2024 | ~4 weeks |
| Chrome 126 | June 11, 2024 | July 23, 2024 | ~6 weeks |
| Chrome 125 | May 14, 2024 | June 11, 2024 | ~4 weeks |
| Chrome 124 | April 16, 2024 | May 14, 2024 | ~4 weeks |
| Chrome 123 | March 19, 2024 | April 16, 2024 | ~4 weeks |
| Chrome 122 | February 20, 2024 | March 19, 2024 | ~4 weeks |
| Chrome 121 | January 23, 2024 | February 20, 2024 | ~4 weeks |
| Chrome 120 | December 5, 2023 | January 23, 2024 | ~7 weeks |
2023 Versions (Chrome 110-119)
| Version | Release Date | End of Support |
|---|---|---|
| Chrome 119 | October 31, 2023 | December 5, 2023 |
| Chrome 118 | October 10, 2023 | October 31, 2023 |
| Chrome 117 | September 12, 2023 | October 10, 2023 |
| Chrome 116 | August 15, 2023 | September 12, 2023 |
| Chrome 115 | July 18, 2023 | August 15, 2023 |
| Chrome 114 | May 30, 2023 | July 18, 2023 |
| Chrome 113 | May 2, 2023 | May 30, 2023 |
| Chrome 112 | April 4, 2023 | May 2, 2023 |
| Chrome 111 | March 7, 2023 | April 4, 2023 |
| Chrome 110 | February 7, 2023 | March 7, 2023 |
2022-2023 Versions (Chrome 100-109)
| Version | Release Date | End of Support |
|---|---|---|
| Chrome 109 | January 10, 2023 | February 7, 2023 |
| Chrome 108 | November 29, 2022 | January 10, 2023 |
| Chrome 107 | October 25, 2022 | November 29, 2022 |
| Chrome 106 | September 27, 2022 | October 25, 2022 |
| Chrome 105 | August 30, 2022 | September 27, 2022 |
| Chrome 104 | August 2, 2022 | August 30, 2022 |
| Chrome 103 | June 21, 2022 | August 2, 2022 |
| Chrome 102 | May 24, 2022 | June 21, 2022 |
| Chrome 101 | April 26, 2022 | May 24, 2022 |
| Chrome 100 | March 29, 2022 | April 26, 2022 |
2021-2022 Versions (Chrome 90-99)
| Version | Release Date | End of Support |
|---|---|---|
| Chrome 99 | March 1, 2022 | March 29, 2022 |
| Chrome 98 | February 1, 2022 | March 1, 2022 |
| Chrome 97 | January 4, 2022 | February 1, 2022 |
| Chrome 96 | November 16, 2021 | January 4, 2022 |
| Chrome 95 | October 19, 2021 | November 16, 2021 |
| Chrome 94 | September 21, 2021 | October 19, 2021 |
| Chrome 93 | August 31, 2021 | September 21, 2021 |
| Chrome 92 | July 20, 2021 | August 31, 2021 |
| Chrome 91 | May 25, 2021 | July 20, 2021 |
| Chrome 90 | April 13, 2021 | May 25, 2021 |
2020-2021 Versions (Chrome 80-89)
| Version | Release Date | End of Support | Notes |
|---|---|---|---|
| Chrome 89 | March 2, 2021 | April 13, 2021 | |
| Chrome 88 | January 19, 2021 | March 2, 2021 | |
| Chrome 87 | November 17, 2020 | January 19, 2021 | |
| Chrome 86 | October 6, 2020 | November 17, 2020 | |
| Chrome 85 | August 25, 2020 | October 6, 2020 | |
| Chrome 84 | July 14, 2020 | August 25, 2020 | |
| Chrome 83 | May 19, 2020 | July 14, 2020 | Chrome 82 skipped |
| Chrome 81 | April 7, 2020 | May 19, 2020 | |
| Chrome 80 | February 4, 2020 | April 7, 2020 |
2019-2020 Versions (Chrome 70-79)
| Version | Release Date | End of Support |
|---|---|---|
| Chrome 79 | December 10, 2019 | February 4, 2020 |
| Chrome 78 | October 22, 2019 | December 10, 2019 |
| Chrome 77 | September 10, 2019 | October 22, 2019 |
| Chrome 76 | July 30, 2019 | September 10, 2019 |
| Chrome 75 | June 4, 2019 | July 30, 2019 |
| Chrome 74 | April 23, 2019 | June 4, 2019 |
| Chrome 73 | March 12, 2019 | April 23, 2019 |
| Chrome 72 | January 29, 2019 | March 12, 2019 |
| Chrome 71 | December 4, 2018 | January 29, 2019 |
| Chrome 70 | October 16, 2018 | December 4, 2018 |
2018 Versions (Chrome 60-69)
| Version | Release Date | End of Support |
|---|---|---|
| Chrome 69 | September 4, 2018 | October 16, 2018 |
| Chrome 68 | July 24, 2018 | September 4, 2018 |
| Chrome 67 | May 29, 2018 | July 24, 2018 |
| Chrome 66 | April 17, 2018 | May 29, 2018 |
| Chrome 65 | March 6, 2018 | April 17, 2018 |
| Chrome 64 | January 23, 2018 | March 6, 2018 |
| Chrome 63 | December 5, 2017 | January 23, 2018 |
| Chrome 62 | October 17, 2017 | December 5, 2017 |
| Chrome 61 | September 5, 2017 | October 17, 2017 |
| Chrome 60 | July 25, 2017 | September 5, 2017 |
2017 Versions (Chrome 50-59)
| Version | Release Date | End of Support |
|---|---|---|
| Chrome 59 | May 30, 2017 | July 25, 2017 |
| Chrome 58 | April 18, 2017 | May 30, 2017 |
| Chrome 57 | March 7, 2017 | April 18, 2017 |
| Chrome 56 | January 24, 2017 | March 7, 2017 |
| Chrome 55 | November 29, 2016 | January 24, 2017 |
| Chrome 54 | October 11, 2016 | November 29, 2016 |
| Chrome 53 | August 30, 2016 | October 11, 2016 |
| Chrome 52 | July 19, 2016 | August 30, 2016 |
| Chrome 51 | May 24, 2016 | July 19, 2016 |
| Chrome 50 | April 12, 2016 | May 24, 2016 |
2015-2016 Versions (Chrome 40-49)
| Version | Release Date | End of Support |
|---|---|---|
| Chrome 49 | March 1, 2016 | April 12, 2016 |
| Chrome 48 | January 19, 2016 | March 1, 2016 |
| Chrome 47 | November 17, 2015 | January 19, 2016 |
| Chrome 46 | October 6, 2015 | November 17, 2015 |
| Chrome 45 | August 25, 2015 | October 6, 2015 |
| Chrome 44 | July 14, 2015 | August 25, 2015 |
| Chrome 43 | May 19, 2015 | July 14, 2015 |
| Chrome 42 | April 7, 2015 | May 19, 2015 |
| Chrome 41 | February 24, 2015 | April 7, 2015 |
| Chrome 40 | January 13, 2015 | February 24, 2015 |
2014 Versions (Chrome 30-39)
| Version | Release Date | End of Support |
|---|---|---|
| Chrome 39 | November 11, 2014 | January 13, 2015 |
| Chrome 38 | September 30, 2014 | November 11, 2014 |
| Chrome 37 | August 19, 2014 | September 30, 2014 |
| Chrome 36 | June 24, 2014 | August 19, 2014 |
| Chrome 35 | May 13, 2014 | June 24, 2014 |
| Chrome 34 | April 1, 2014 | May 13, 2014 |
| Chrome 33 | February 18, 2014 | April 1, 2014 |
| Chrome 32 | January 7, 2014 | February 18, 2014 |
| Chrome 31 | November 5, 2013 | January 7, 2014 |
| Chrome 30 | September 24, 2013 | November 5, 2013 |
2013 Versions (Chrome 20-29)
| Version | Release Date | End of Support |
|---|---|---|
| Chrome 29 | August 13, 2013 | September 24, 2013 |
| Chrome 28 | June 25, 2013 | August 13, 2013 |
| Chrome 27 | May 7, 2013 | June 25, 2013 |
| Chrome 26 | March 26, 2013 | May 7, 2013 |
| Chrome 25 | February 12, 2013 | March 26, 2013 |
| Chrome 24 | December 18, 2012 | February 12, 2013 |
| Chrome 23 | October 30, 2012 | December 18, 2012 |
| Chrome 22 | September 18, 2012 | October 30, 2012 |
| Chrome 21 | August 7, 2012 | September 18, 2012 |
| Chrome 20 | June 19, 2012 | August 7, 2012 |
2011-2012 Versions (Chrome 10-19)
| Version | Release Date | End of Support |
|---|---|---|
| Chrome 19 | April 24, 2012 | June 19, 2012 |
| Chrome 18 | March 13, 2012 | April 24, 2012 |
| Chrome 17 | January 31, 2012 | March 13, 2012 |
| Chrome 16 | December 6, 2011 | January 31, 2012 |
| Chrome 15 | October 18, 2011 | December 6, 2011 |
| Chrome 14 | September 6, 2011 | October 18, 2011 |
| Chrome 13 | July 26, 2011 | September 6, 2011 |
| Chrome 12 | May 31, 2011 | July 26, 2011 |
| Chrome 11 | April 19, 2011 | May 31, 2011 |
| Chrome 10 | March 8, 2011 | April 19, 2011 |
Early Versions (Chrome 7-9)
| Version | Release Date | End of Support |
|---|---|---|
| Chrome 9 | January 25, 2011 | March 8, 2011 |
| Chrome 8 | November 30, 2010 | January 25, 2011 |
| Chrome 7 | October 12, 2010 | November 30, 2010 |
Note: Chrome 82 was skipped due to the COVID-19 pandemic, proceeding directly to Chrome 83.
5. Managing Chrome Versions in Enterprise Environments
How should enterprises manage Chrome updates?
Utilizing Extended Stable Channel: For reduced update frequency, use the Extended Stable channel which provides major updates every 8 weeks while continuing to receive security fixes.
You can select the release channel by navigating to Chrome browser > Settings in the Admin Console.
Parallel Beta Channel Testing: Even when using Extended Stable, deploy the Beta channel on some test machines to identify issues proactively. Since there’s no Extended Beta channel, utilize the standard 4-week beta cycle.
Configuring Update Policies: Through the Google Admin console, you can granularly control update timing, rollout speed, and more. Features like Cache Updates and Peer-to-Peer Automatic Updates help manage bandwidth efficiently.
6. Checking and Updating Chrome Version
Checking your current Chrome version is straightforward:
- Open Chrome browser
- Click the three-dot menu in the upper right
- Select “Help” > “About Google Chrome”
- Version information displays and updates are automatically checked
From the command line:
google-chrome --version
With automatic updates enabled, Chrome downloads updates in the background and applies them on the next restart. A colored dot in the browser’s upper right indicates a pending update:
- Green: Updated less than 2 days ago
- Orange: Updated 4 days ago
- Red: Updated 7+ days ago
7. Why Such a Rapid Update Cycle?
Releasing a major version every 4 weeks may seem aggressive, but Google has solid reasons for this strategy.
Rapid Security Response: Web browsers serve as the gateway to the internet. With new security vulnerabilities discovered weekly, a fast update cycle enables quick response to these threats.
Evolving Web Standards: Web technologies like HTML5, CSS3, and WebAssembly continue to advance. A rapid release cycle allows quick support for the latest web standards.
Fast Feedback Integration: New features can be quickly released and improved based on user feedback, enabling agile development.
Maintaining Competitiveness: Competing browsers like Firefox and Edge follow similar rapid release cycles, making this essential for maintaining market competitiveness.
8. ChromeOS Device AUE (Auto Update Expiration) Policy
Separate from Chrome browser, ChromeOS devices like Chromebooks, Chromeboxes, and Chromebases follow a distinct AUE (Auto Update Expiration) policy.
Google provides 6.5 years of automatic update support for each hardware platform, with the 6.5 years calculated from when the first device on that platform is released.
You can check ChromeOS device AUE dates on Google’s official Auto Update policy page. When a device reaches AUE, it no longer receives ChromeOS updates, though the device continues to function.
However, Google is working on the LaCros project to separate the web browser from the operating system. Once completed, the Chrome browser may continue receiving updates even after ChromeOS reaches its AUE date.
9. Essential Security Reminders
Key points to remember for maintaining Chrome security:
Never Disable Auto-Updates: Disabling Chrome’s automatic updates for security reasons is not recommended. Even if you have specific requirements, using the Extended Stable channel is safer.
Regular Restarts: Updates won’t apply until you restart the browser. Make it a habit to restart Chrome regularly or reboot your computer.
Extension Management: Vulnerable extensions can pose security risks. Starting June 2024, Chrome has been gradually disabling Manifest V2 extensions, with the related policy set to be removed in June 2025. Only install trusted extensions and review them regularly.
Caution with Flags: Experimental features in chrome://flags haven’t been verified for stability and security. Avoid using them in production environments.
10. Future Chrome Support Policy Outlook
Chrome’s support policy will continue to evolve.
Chrome Apps support will be phased out starting July 2025 (ChromeOS M138) and completely end in October 2028. This signals a transition to web apps and PWAs (Progressive Web Apps).
From a security perspective, TLS certificates issued after July 31, 2025 by Chunghwa Telecom and Netlock will not be trusted by default starting with Chrome 139, among other certificate policy strengthening measures.
Chrome Enterprise Core services continue to develop with features like inactive profile auto-deletion, enhanced DLP (Data Loss Prevention) capabilities, and more granular policy controls for enterprise environments.
While Chrome’s rapid update cycle may seem complex for version management, it ultimately serves user security and delivers the latest web technology experiences. Simply enabling automatic updates and regularly restarting the browser ensures safe Chrome usage.
In enterprise environments, the Extended Stable channel combined with appropriate update policies can balance stability and security. Regularly checking the Chrome Release blog and Chrome Enterprise release notes helps stay informed about the latest developments.
Official Documentation Links:
- Chrome Release Schedule
- Chrome Enterprise Auto Update Policy
- Chrome Release Channel Selection Guide
- Chrome Version EOS/EOL Details – EndOfLife.date
- Chrome Enterprise Release Notes
- Chrome Official Release Blog