Chrome, Edge, and Firefox Converge on Two-Week Release Cycles in August and September
Microsoft Edge, Mozilla Firefox, and Google Chrome are each cutting their release interval from four weeks to two, starting in late August and September 2026.
Overview
Microsoft, Mozilla, and Google are each cutting their browser release interval in half this year, moving from a four-week update cadence to a two-week one. Microsoft Edge switches first, followed by Firefox and then Chrome, according to official posts from all three vendors.
What We Know
Starting with Microsoft Edge 152, due on the Stable channel on August 27, Edge will move to a 2-week release cycle, according to the Microsoft Edge Blog. The post, published June 11, states that “each release brings about half as much new content as before, delivered twice as often.” Extended Stable, the slower channel Microsoft introduced in 2021 for enterprise administrators, is not changing: it will now receive updates “every fourth release (for example, 156, 160, 164),” keeping the same eight-week gap between updates, per the Edge Blog. Both channels continue to receive critical security updates on their respective schedules.
Mozilla is next. In a post to the [email protected] mailing list, Sylvestre Ledru, Mozilla’s director of engineering, wrote that Mozilla is “planning to move Firefox Desktop and Android from a 4-week release cadence to a 2-week release cadence starting in September 2026,” with a target of shipping Firefox 155 on September 1, 2026, moved up from the originally scheduled September 15. Ledru framed the change as an experiment: “This will be an experiment. The goal is to give work that is ready to ship more frequent opportunities to reach users, while making the release process more predictable and reducing pressure on uplifts.” He added a caveat: “This does not mean that all work needs to ship twice as fast. Work that is not ready should not be rushed, and features can still take the time they need to bake,” and said Mozilla “will closely monitor how this change works in practice and adjust if needed.” According to The Register, Firefox 153 and 154 will keep the current four-week schedule before the switch, and Firefox 153 is set to become the next Extended Support Release, receiving security updates for at least 15 months through late 2027.
Google announced its own move first chronologically but its cutover lands last. In a Chrome for Developers post published March 3, 2026 by Ben Mason and Deepak Ravichandran, Google said “starting September 2026, Chrome will move to a two-week release cycle, from the current four-week cycle,” with the switch taking effect at the stable release of Chrome 153 on September 8th. Chrome has shipped a new milestone every four weeks since 2021, the post notes, and in 2023 Google “initiated a weekly security update to further improve our patch gap and introduced an early stable release to improve release quality.” The new cadence applies to “Desktop, Android, and iOS,” with “no changes to the Dev and the Canary channels,” and Chrome Beta will continue to ship three weeks ahead of each stable release. As with Edge, Chrome’s Extended Stable channel — also introduced in 2021 for enterprise administrators and Chromium embedders — keeps its existing eight-week cycle unchanged.
All three companies frame the shift the same way: smaller, more frequent releases rather than larger periodic ones. Google says the smaller scope of each release “minimizes disruption and simplifies post-release debugging,” while Microsoft says smaller change sets can “make validation more manageable” for IT teams testing updates before wide deployment, per the Edge Blog.
What We Don’t Know
Mozilla has explicitly labeled its move an experiment rather than a permanent change, and has not said what metrics would lead it to revert to a four-week cadence. Neither Google nor Microsoft has published a specific reconsideration point either, and none of the three companies has said whether extension developers or enterprise IT teams that are not on the Extended Stable channels will need new testing infrastructure to keep pace with twice-as-frequent updates.
Analysis
The near-simultaneous timing is notable given that Edge and Chrome share the Chromium engine, while Firefox runs on Mozilla’s independently developed Gecko engine — meaning three separately governed release processes arrived at the same two-week interval within a few months of each other. Edge’s transition on August 27 arrives first, Firefox’s target of September 1 follows within days, and Chrome’s September 8 switch closes out the sequence, compressing a decade-old browser-release rhythm into a single six-week window across the industry’s three most-used desktop browsers.