Google is developing a method to update the Chrome browser without forcing the user to restart it, a change primarily focused on strengthening the software's security.
Google is developing a method to update the Chrome browser without forcing the user to restart it, a change primarily focused on strengthening the software's security.
The company also plans to release new versions of Chrome every two weeks and is considering making two weekly deliveries of security update packages. This new methodology is already being tested in Chrome version 150 intended for the macOS operating system.
Currently, Chrome performs updates in the background, but the completion of this process depends on restarting the browser. Google seeks to eliminate or reduce this mandatory restart, motivated by security reasons that go beyond mere user convenience.
Like other major technology companies, Google employs artificial intelligence to detect and correct flaws in its products more quickly. This applies to Chrome, an effort that began years ago but gained significant momentum in 2026. That year, Google created a group of agents that used Gemini to locate vulnerabilities throughout the Chrome source code with greater effectiveness and fewer false positives.
However, even with the agility of developers in fixing bugs, the interval between receiving the security update in Chrome and the moment the user restarts the browser to finalize the process can be excessively long. This period represents a risk, as there is a possibility of the vulnerability being exploited. Although unlikely, just as AI helps Google identify flaws, this same technology can be used by third parties to maliciously exploit flaws.
Due to this scenario, Google will implement new versions of Chrome bi-weekly starting in September 2026. The purpose is to ensure that the browser receives security fixes in a shorter timeframe, given that the current browser update cycle typically lasts four weeks. Furthermore, between these main cycles, Google usually releases a smaller security update package that does not change the browser version, only modifies its build number. Now, the company is evaluating the possibility of making two such releases weekly.
In this context, the update without the need for a restart becomes relevant. The crucial point is that the restart will occur, but not while Chrome is actively in use. Google's intention is to determine ideal times to automatically restart the browser, thus ensuring a flawless session restoration.
Generally, Chrome developers want to restart the browser while it is still running, but only when no tabs are open. Although this functionality is not yet active, Google has begun testing it in Chrome version 150 for macOS. If the tests are successful, the proposal should be extended to versions intended for other operating systems.