Microsoft Edge is doubling its update speed, and it's just as good as it sounds

Microsoft is changing how often it pushes updates to the Stable branch of its Edge browser, and the headline number sounds great. Instead of shipping a new version once a month, Edge will start landing fresh builds every two weeks. The shift kicks in on August 27, 2026, according to the announcement on Windows Blogs. Until that date, the current monthly cadence stays in place.

What's actually changing

The practical effect for most people is a faster drumbeat of releases. Where you previously waited about four weeks between feature drops, you'll now see something new roughly every fortnight. Critical security patches were never tied to the regular update train anyway, and that stays true here. Microsoft will continue pushing urgent security fixes as soon as they're ready, independent of the biweekly schedule. That separation matters, because it means a zero-day patch doesn't have to wait for the next scheduled build to reach you.

There's an important asterisk, though. Microsoft isn't doubling the amount of stuff you get. It's splitting each monthly update into two halves and shipping them a couple of weeks apart. So the overall volume of features and fixes over any given month stays about the same. You're getting the same meal, just served as two smaller plates instead of one large one.

Whether that's an improvement depends on how you think about software updates. Smaller, more frequent releases tend to be easier to test and less disruptive when something breaks, since there's less changing at once. If a particular build introduces a regression, the smaller surface area makes it easier to pinpoint what went wrong. On the other hand, anyone hoping this meant twice the features will be disappointed. The pace of genuinely new functionality isn't accelerating, only the rhythm of delivery.

The Extended Stable channel and why it exists

Edge isn't a single update stream. Alongside the regular Stable branch, Microsoft maintains a channel called Extended Stable, which updates every eight weeks rather than monthly. This slower cadence exists for a specific reason. IT administrators in businesses, schools, and other large organizations need time to validate that browser changes won't break internal web apps, custom extensions, or compliance tooling before those changes hit thousands of managed machines. An eight-week window gives those teams breathing room to test and prepare.

That eight-week rhythm isn't changing. What's changing is the contents of each Extended Stable release. Because the Stable branch is now moving twice as fast, an eight-week Extended Stable update will bundle four Stable updates' worth of changes instead of the previous two. For IT teams, the takeaway is that the cadence they plan around stays identical, even if each batch now folds in more incremental Stable work under the hood. Organizations that depend on predictable update windows won't have to redo their deployment planning.

How this fits Edge's broader release model

This move keeps Edge roughly aligned with the upstream Chromium project, which has itself experimented with faster and more granular release schedules over the years. Edge is built on Chromium, so its update philosophy tends to track what Google does with Chrome, adapted for Microsoft's enterprise customer base. Biweekly Stable releases with a separate slow lane for managed environments is a familiar pattern in browser land, balancing the desire to ship quickly against the reality that large IT deployments can't absorb constant change.

For everyday users, none of this requires any action. Edge updates itself in the background, and the channel you're on, almost certainly Stable unless your workplace put you on Extended Stable, determines what you experience. After August 27, you'll simply notice version numbers ticking up more often. The features arrive at a similar overall rate as before, but the steadier stream means you're never waiting a full month to see whatever Microsoft has been working on next.

It's a modest but sensible adjustment. Doubling update frequency sounds dramatic, and the reality is more measured once you account for the split monthly cadence. Still, a faster, more incremental release pipeline generally translates to fewer surprises and quicker turnaround on fixes, which is a reasonable trade for not getting more features overall.