Google is updating Chrome every two weeks now—as of version 153—for desktop, Android, and iOS. The move marks a shift from the previous four-week rhythm and reflects growing pressure from security challenges in the age of AI. Google says the new schedule lets it respond faster to threats and get fixes into user hands more rapidly.
Why two weeks? Faster risk reduction and competitive urgency
The shorter cycle targets the so-called “N-day” gap: the time between when a vulnerability is discovered and when a patch reaches users. AI tools have increased both the speed and volume of vulnerabilities being surfaced, whether through automated scanning or by community reporting. By halving the interval between official releases, Chrome can curtail windows for attackers.
Beyond security, the update pace supports faster innovation. Google is pushing more AI-powered features into Chrome and needs a fast turnaround for feature fixes and improvements. It also comes as new browsers with AI capabilities—browsers like Brave, Comet, Opera Neon, Dia, and DuckDuckGo—are waiting in the wings, making speed a competitive advantage.
Industry ripple effects and Chrome’s history of release cadences
Chrome’s move isn’t in isolation. Mozilla, Microsoft, and Brave are all following suit, adjusting their release schedules to adopt similar two-week cycles. Given Chrome’s dominant market share, Google’s approach may become a de facto industry standard.
This isn’t Chrome’s first revamp of release timing. In 2021, Google reduced its cycle from six to four weeks to speed up roll-outs and reduce security lag. Its guiding principle—”release early, release often”—has shaped these changes for over a decade.
Version 153, now rolling out, is the first under the new two-week plan. This shift has been in the works since earlier this year.
Why this matters:As AI tools grow more capable—both for building features and enabling cyberattacks—vulnerabilities multiply and evolve quickly. Google’s two-week release interval strengthens Chrome’s defenses and sets a higher bar for browser security.
Expectations for the near future include more automated vulnerability detection, swifter patch delivery, and continuous competitions around security in browsers. Users will have to update more often, but the trade-off is tighter risk control as threats accelerate.
What to watch:Does the faster cadence lead to more accidental bugs slipping through? How will AI-based threats adapt to even shorter exposure windows? The answers will shape security norms across browsers for years to come.
