Edge Joins Chrome in Phasing Out Legacy Extension Framework

The Second Wave

Microsoft has set a timeline for retiring Manifest V2 extensions in Edge, following the path Google cleared with Chrome earlier in 2026. The decision affects popular content-blocking tools, most notably uBlock Origin, which built its reputation on the capabilities that the older extension architecture provided.

The scale of disruption appears limited, at least according to Microsoft's internal metrics. The company reports that only 58 extensions in its add-on marketplace still rely on Manifest V2 and maintain any significant user base. Of those, all but three have already migrated to the newer Manifest V3 standard or offer alternative versions that comply with the updated framework.

For developers who follow browser politics, this announcement completes a transition that began when Google first outlined its Manifest V3 roadmap in 2019. What started as a proposal to improve security and performance quickly became a flashpoint in debates about browser control, user agency, and the economics of ad-supported content.

What Changed Under the Hood

Manifest V2 and V3 represent fundamentally different philosophies about what browser extensions should be allowed to do. The older framework gave extensions broad latitude to intercept, inspect, and modify network requests in real time. That power enabled sophisticated ad blockers to evaluate every resource a page tried to load and decide on the fly whether to allow it through.

Manifest V3 shifts that model toward a declarative approach. Instead of executing arbitrary code to make blocking decisions, extensions now provide the browser with a set of rules that the engine itself interprets. The change limits flexibility but gives browser vendors tighter control over performance and, critics argue, over what kinds of filtering remain viable.

uBlock Origin, one of the most widely deployed extensions for both Chrome and Edge, has declined to port its full feature set to Manifest V3. Its developer instead released uBlock Origin Lite, a stripped-down version that works within the new constraints. The naming alone signals what was lost in translation.

A Smaller Crater Than Expected

Microsoft's claim that only 58 extensions face obsolescence suggests either that the Edge user base skews toward users who don't rely heavily on extensions, or that developers have already completed the migration work. Both explanations likely hold some truth.

Edge's extension ecosystem has always been smaller than Chrome's. The browser shares Chromium's rendering engine and much of its codebase, but Microsoft has struggled to attract the same density of third-party development. That relative scarcity may have made the transition easier to manage; fewer extensions means fewer edge cases and less public outcry.

The three holdouts that have not migrated remain unnamed in Microsoft's announcement. Whether they represent niche tools with dedicated followings or abandoned projects is unclear. Either way, their users will need to find alternatives or accept reduced functionality.

The Opera Exception

Opera has positioned itself as a refuge for users who want to keep running Manifest V2 extensions. The browser, which also uses the Chromium engine, has committed to maintaining support for the older framework "for as long as it's technically feasible." That qualifier leaves room for retreat if maintaining compatibility becomes too costly or if security concerns mount, but for now Opera offers a workaround for users unwilling to compromise.

The viability of that strategy depends on how much the Chromium codebase itself evolves. If Google removes the underlying plumbing that makes Manifest V2 possible, Opera will face a choice between maintaining an increasingly divergent fork or falling in line. The company's statement suggests it understands that calculus but believes it can buy time.

What This Means for Content Filtering

The shift to Manifest V3 reshapes the economics and capabilities of content blocking in ways that go beyond simple compatibility. Extensions operating under the new rules can define up to 30,000 static filtering rules and a smaller number of dynamic rules. For many users, that will prove sufficient. But advanced filter lists, especially those that combine anti-tracking measures with cosmetic filtering and script blocking, can exceed those limits.

The result is a fragmentation of the ad-blocking landscape. Users who care deeply about privacy and control are migrating to browsers that preserve the old extension model, while mainstream users are adopting the Lite versions of their preferred blockers or switching to alternatives that fit within Manifest V3's boundaries. Publishers and advertisers, meanwhile, are watching to see whether the new constraints make their content harder to filter.

At DailyTechWire, we've tracked similar platform transitions before. The pattern is familiar: a vendor announces a change in the name of security or performance, developers protest the loss of capability, and users eventually adapt or fragment. What makes this transition notable is the coordination. When both Chrome and Edge move in lockstep, the pressure on holdouts intensifies. Opera's stance may prove temporary, or it may carve out a niche for users who prioritize extension freedom.

The Longer Game

Microsoft's announcement is less a surprise than a confirmation. Once Chrome committed to deprecating Manifest V2, Edge's position became untenable. Maintaining support for an obsolete framework while the underlying Chromium project moves on would require engineering resources that Microsoft has shown little interest in allocating.

The broader question is whether this transition represents a one-time adjustment or the beginning of a pattern. If browser vendors can successfully narrow the scope of what extensions are allowed to do, other capabilities may come under similar scrutiny. The justifications will vary, but the dynamic remains: platforms that host third-party code always face tension between openness and control.

For now, Edge users who rely on uBlock Origin or similar tools have a clear path forward. They can switch to the Lite version, try a different extension that works within Manifest V3, or move to a browser that still supports the older framework. None of those options perfectly replicate what they had, but that's the nature of platform transitions. The infrastructure moves, and users adjust.