Microsoft Edge is moving to a two-week Stable release cycle starting with Edge 152, scheduled to reach the Stable channel on August 27, 2026. The change was confirmed in a Microsoft Edge blog post on June 11, 2026, cutting the browser’s current four-week interval exactly in half and bringing Edge onto roughly the same release rhythm Google has set for Chrome 153 in September.
The headline reads as a simple tempo change. The structural reason runs deeper. Microsoft announced in December 2018 that it would rebuild Edge on Google’s open-source Chromium project to create better web compatibility. That earlier decision is the reason the 2026 schedule looks the way it does. Security fixes, rendering changes, and JavaScript engine updates flow from Chromium on a rhythm Microsoft does not set.
Why Edge Is Switching to Two-Week Releases
Microsoft framed the new cadence as a net benefit. In a post titled “Faster updates, enterprise-friendly schedule”, the company said Edge users would get “a steady, continuous stream of new capabilities.” The blog post adds that, for customers on Stable, the new cycle delivers “smaller, steadier change,” with each release carrying “about half as much new content as before, delivered twice as often.” Both the Stable and Extended Stable channels continue to receive critical security patches between major releases.
The old cycle was four weeks. The new one is two. That is the calendar math. The competitive and structural math is the more consequential piece. Google has confirmed that Chrome 153 will ship September 8, 2026 as Chrome’s own first two-week Stable release. By aligning, Edge keeps its security patch delivery on the same clock as the Chromium engine underneath it.
The Edge release schedule page already reflects the change. Microsoft published version 149 to Stable on June 4, 2026 as 149.0.4022.52, and lists Edge 152 as the first Stable build on the new two-week cadence. Each subsequent Stable version steps up by two.
What Changes on August 27 with Edge 152
Edge 152 is the line of demarcation. It reaches the Beta channel the week of August 6, 2026. It lands on Stable the week of August 27, 2026. It is the first Stable version to ship on the two-week cadence.
After that, the version numbers step in twos. Edge 152 is the demarcation; subsequent Stable builds land every two weeks on the new rhythm. Beta continues to lead Stable, giving Microsoft its validation window before each release reaches the broader user base.
Home users on the default Stable channel need to do nothing. Updates begin arriving automatically every two weeks once Edge 152 ships. Organizations running managed deployments need to think about the new rhythm well before then. The change is not a feature addition; it is a structural shift in how often new code reaches the browser. The trade-off Microsoft is selling is smaller change sets, more often, with a narrower blast radius if something breaks. The trade-off IT teams inherit is a tighter validation window between each release and broad organizational deployment.
The current latest Stable version at time of writing is Edge 149, released June 4, 2026. Microsoft is publishing on the old four-week cycle until Edge 152. Two more four-week releases, Edge 150 and Edge 151, sit between the present and the cadence change.
| Version | Beta channel week | Stable channel week | Extended Stable channel week |
|---|---|---|---|
| 152 | Week of 06-August-2026 | Week of 27-August-2026 | Week of 27-August-2026 |
| 153 | Week of 25-August-2026 | Week of 10-September-2026 | Not applicable |
| 154 | Week of 08-September-2026 | Week of 24-September-2026 | Not applicable |
The Chromium Pipeline That Sets the Clock
Edge is built on Chromium, the open-source browser engine Google develops with contributions from Microsoft, Intel, Samsung, and others. The release schedule page makes the dependency explicit: “The trigger for Beta and Stable major releases is an equivalent Chromium release.” Microsoft does not set the upstream tempo.
That matters most for security. When a Chromium vulnerability is disclosed, the fix lands in Chrome’s stable channel first. Under a four-week Edge cycle, that fix could sit in Edge for up to four weeks before reaching the same users. The new two-week cadence cuts the maximum gap to 14 days. Chromium security fixes flow through a cherry-pick process into the active stable branch, and the closer Edge’s cycle sits to Chrome’s, the smaller the window attackers have to reverse-engineer a public fix and exploit the lag. Google’s framing of its own move captures the same logic: smaller, more frequent releases minimize disruption and simplify post-release debugging.
Extended Stable Stays the Enterprise Escape Hatch
Microsoft left one door open for organizations that need longer validation windows. The Extended Stable channel, introduced in 2021 for IT teams that need time to test and validate browser updates before broad deployment, is unchanged in its eight-week interval.
What changes is the version mapping. Under the old cadence, Extended Stable aligned to every other Stable release. Under the new two-week Stable cycle, Extended Stable aligns to every fourth Stable release: 152, 156, 160, 164. The time between Extended Stable updates stays the same. Security patches continue to flow to Extended Stable on the same Chromium security patching model, independent of the major feature cadence.
The Edge channel overview page documents this. Extended Stable “provides a longer 8-week major release cycle, compared to the two-week major release cycle for Stable.” Organizations on Extended Stable do not need to change any configurations.
- Stable: Broad Deployment, ~two weeks, supported
- Extended Stable: Enterprise release option, ~eight weeks, supported
- Beta: Representative validation, ~two weeks, supported
- Dev: Planning and developing, weekly, not supported
- Canary: Bleeding edge content, daily, not supported
What IT Teams Should Do Before the Cadence Hits
Microsoft’s primary recommendation for enterprise administrators is to add a pilot group to the Beta channel now, through the supported Enterprise Preview path. The post announcing the change frames it directly: “Whichever channel you run: add a pilot group to Beta and start testing from day one to maximize your validation time.” The Enterprise Preview setup guide shows admins how to set the Target Channel policy to Beta or Dev to flight prerelease builds inside the Edge Stable application.
For organizations with 10,000 to 100,000 devices, Microsoft recommends a 5% flighting population. The minimum suggested prerelease audience is 20 devices. Smaller organizations (under 10,000) are recommended at 10%, and larger ones scale down. The reason this matters is structural: with a two-week Stable cadence, the validation window between Beta and broad deployment is shorter, not longer.
- Stable assisted support window: ~12 weeks
- Extended Stable assisted support window: ~16 weeks
- Current latest Stable version: Edge 149.0.4022.52 (June 4, 2026)
- Recommended flighting for 10,000 to 100,000 devices: 5%
- Minimum prerelease audience: 20 devices
What Microsoft Hasn’t Confirmed Yet
Whether the two-week cadence extends to Edge for Business or Edge for Linux has not been confirmed. Both currently follow the main Stable channel schedule, but Microsoft has not explicitly committed to including them in the August 27 transition. Organizations running either variant should monitor the Microsoft Edge Blog for further announcements before that date. The browser war on Windows is heating up on multiple fronts, and the new Edge cadence is one front; see how Chrome is pushing back against Edge on the same Windows default settings.
The Microsoft blog post and the official documentation cover the four standard channels and the Edge Stable application. Edge for Business and Edge for Linux are listed in the channel overview table only as supported channels, without a separate release cadence noted.
The same gap exists on the Chromium side. Google’s Chrome Extended Stable stays on its existing eight-week cycle. Chrome’s Standard stable moves to two weeks starting September 8 with Chrome 153. The enterprise protection is intact on both browsers; the open question is whether Microsoft’s two non-default distributions will follow the August 27 transition or hold for a later update. New entrants are also reshaping the picture. OpenAI’s Atlas browser entered the Chrome-versus-Edge race in late 2025 and now competes for the same two-week tempo.
The published material indicates Microsoft is rolling the new cadence into the Stable channel first, with Extended Stable’s version mapping adjusted to match, and the other variants left for a later announcement. The Microsoft 365 Message Center is where Microsoft has said it will continue to share updates.
Frequently Asked Questions
Does the two-week cycle mean Edge gets twice as many new features?
No. Microsoft has been explicit that each release under the two-week schedule will carry about half the new content of a four-week release, delivered twice as often. The total monthly volume of features and changes stays similar. They arrive in smaller, more frequent batches rather than larger monthly bundles.
Why is Microsoft speeding up Edge’s release cycle now?
The immediate trigger is Google Chrome’s own shift. Google has confirmed that Chrome 153 will ship September 8, 2026 as Chrome’s first two-week Stable release. Because Edge is built on Chromium, the underlying security fixes and platform changes arrive on a schedule Google sets, not Microsoft. A four-week Edge cycle could mean Edge users waited up to four weeks longer than Chrome users for the same patch. The two-week cycle closes that gap.
What should enterprise IT administrators do before August 27?
Add a pilot group to the Beta channel through the Enterprise Preview path. Under a two-week Stable cadence, the window to validate each update before broad deployment is tighter. Microsoft recommends flighting 5% of devices for organizations with 10,000 to 100,000 devices, with a 20-device minimum. Organizations already on Extended Stable do not need to change anything.
Does the change affect the Extended Stable channel?
The timing and interval of Extended Stable updates are unchanged. It still receives major feature updates every eight weeks. What changes is the version number mapping: Extended Stable will now align to every fourth Stable release, such as 156, 160, 164, rather than every other one, since Stable is shipping twice as often. Security patches continue to flow as needed, independent of the feature cadence.
When does the two-week cycle start?
The new cadence begins with Edge 152 on the Stable channel, scheduled for the week of August 27, 2026. Edge 150 reaches Stable the week of July 2, 2026, and Edge 151 the week of July 30, 2026, both on the old four-week cycle. Edge 152 is the first Stable version on the new rhythm.
