AIToday
Large Language ModelsAI Business & IndustryTechCrunch AIPublished: Sep 9, 2026, 04:00 JST2 min read

Chrome moves to two-week release schedule with Chrome 153

Chrome moves to two-week release schedule with Chrome 153

3 Key Points

  1. What happened

    Google launched Chrome 153 on desktop, iOS, and Android, officially switching Chrome from a four-week to a two-week release schedule.

  2. Why it matters

    The shorter cycle shrinks the window between landing a fix and getting it to users, keeping the "N-day" patch gap as small as possible.

  3. What to watch

    The faster schedule is tied to Chrome's AI-era security strategy, as automated tools and bug reports have increased the volume of patches.

WHO IT HITSSecurity teams and IT administrators who manage Chrome deployments will need to handle updates twice as often, reducing the time they have to test patches before they reach end users.

Ask the AI about this article →

Summaries like this, in your inbox every morning.

Context & Analysis

Google's shift to a two-week release schedule marks the second time the company has accelerated Chrome's update cadence. Chrome first moved to a four-week release cycle in 2021, down from six weeks, after establishing its principles of "release early, release often" over a decade prior. The new schedule is a direct response to the changing security landscape, where automated AI tools and community bug reports have increased the volume of patches needing deployment.

The faster cadence is also a competitive move. AI-assisted software development has enabled new browser competitors to emerge, including Brave, Dia, Opera Neon, Perplexity's Comet, and DuckDuckGo's browser, even as OpenAI's web browser ChatGPT Atlas was shut down. By shipping features faster, Google can iterate more rapidly on AI additions to Chrome and maintain its position as the most-used browser globally.

The success of this strategy hinges on whether the two-week cycle actually keeps the "N-day" patch gap small without overwhelming Chrome's development and quality assurance teams. The test will be whether the faster schedule can consistently deliver stable updates while addressing the growing volume of AI-related threats.

FAQ
What is the "N-day" patch gap?
The "N-day" patch gap is the gap between when a security vulnerability is known and when it gets patched. A shorter release schedule helps keep this gap as small as possible.
Why is Google speeding up Chrome releases?
Automated AI tools and community bug reports have pushed up the volume of patches and updates. Faster releases also help Chrome ship features faster as AI-assisted development enables new browser competitors to emerge.
Which other browsers have adopted a two-week schedule?
Mozilla, Microsoft, and Brave have already begun adopting a faster two-week schedule, following Chrome's lead.

Get the latest Large Language Models news every morning

For example, today's edition would include:

  • Google's TimesFM-3 tops forecasting benchmarks, adds multivariate supportTHE DECODER · 51m ago
  • Rosetta Stone's Todd Hughes: AI can't replace talking to peopleFortune AI · 51m ago
  • DeepSeek V4.1-Flash: 763B model beats V4 Pro on AA Index 40Latent Space · 3h ago

AI-summarized, only the topics you pick — one digest a day via Email, Slack, or Discord.

Free · 30 seconds with Google · unsubscribe anytimeWhat is AIToday? →

Ask AI

Ask AI anything about this article. Q&As are published on this page for other readers too.

Related Articles

Next articleOpenAI AI resolves Navier–Stokes Millennium Problem