Starting next month, every major browser on your computer will update twice as often. Chrome, Firefox and Edge are all moving to a two-week release cycle within weeks of each other — a convergence that will change how quickly you get new features and security fixes, and how often you see that “restart to update” nudge.
Chrome starts biweekly releases on September 8
Google announced in March 2026 that Chrome would shift from four-week to two-week stable releases across desktop, Android and iOS. Chrome 152, expected on August 25, will be the last version on the old monthly schedule. Chrome 153 lands September 8 as the first biweekly release, followed by Chrome 154 on September 22 and Chrome 155 on October 6.
Google says a beta still ships three weeks before each stable release, so developers keep the same testing window. Weekly security patches — a practice Chrome started in 2023 — continue alongside the new cadence. Enterprise users on Extended Stable stay on their existing eight-week cycle.
Edge follows on August 27
Microsoft announced in June that Edge 152, due August 27, would be the first Edge release on a two-week schedule. Since Edge shares Chromium’s engine, aligning with Chrome’s faster cadence is a natural fit. Edge’s Extended Stable channel keeps its eight-week rhythm as well — updates land every fourth version (156, 160, 164 and so on), so IT teams managing large deployments are not forced into the faster lane.
Firefox joins from September 1
Mozilla confirmed in July that Firefox Desktop and Android will move to biweekly major releases starting with Firefox 155 on September 1. Firefox 154, expected August 18, will be the last monthly release. The new schedule runs at least through Firefox 160: version 156 on September 15, 157 on September 29, and 158 on October 13.
Mozilla is explicitly calling this an experiment. If stability or quality metrics slip, the company says it will adjust course. Firefox on iOS stays on its current schedule.
The ESR (Extended Support Release) channel keeps its annual feature cadence but will get security point updates on biweekly opportunities — expect version numbers like ESR 153.2, 153.3 and so on, instead of the current monthly security dots.
What this means for you
Under a four-week cycle, a feature or fix finished early in the cycle sat idle for nearly a month. Two-week releases cut that waiting time roughly in half, which means security patches and bug fixes reach you faster. That is the genuine upside.
The practical cost is more frequent update prompts. Chrome, Edge and Firefox all use background updates that download silently, but each still needs a browser restart to apply. If you tend to keep dozens of tabs open for days, expect to see that restart nudge more often. On slower connections — common in many parts of India — more frequent downloads could also be noticeable, though each individual update should be smaller since it carries fewer changes.
For extension developers, the faster treadmill means less time to catch and fix compatibility issues before a new stable version ships. Google and Mozilla both say they will not rush unfinished features and that the development timeline for any given feature stays the same — only the release opportunities increase. Whether that holds under competitive pressure remains to be seen.
The full timeline
- August 18 — Firefox 154 (last monthly Firefox release)
- August 25 — Chrome 152 (last monthly Chrome release)
- August 27 — Edge 152 (first biweekly Edge release)
- September 1 — Firefox 155 (first biweekly Firefox release)
- September 8 — Chrome 153 (first biweekly Chrome release)
If you use any of these browsers — and statistically, you almost certainly use at least one — no action is required on your part. Updates will keep arriving automatically, just more often. The browsers you already have will simply start ticking over faster, beginning in the last week of August.
Sources: Chrome for Developers, XenoSpectrum (Firefox details), Microsoft Edge Blog
