Why Microsoft Edge is Changing the Extension Game
The world of web browsers is on the verge of significant changes that will directly affect how millions of users interact with the internet. Microsoft has officially confirmed its intention to follow Google’s lead and begin the process of phasing out support for extensions built on the outdated Manifest V2 platform in its Edge browser. This decision is not surprising, considering that both browsers are based on the common Chromium engine, but it is causing a significant stir, especially among fans of ad-blocking and privacy protection extensions.
The transition to the new architecture, known as Manifest V3, is positioned by the engine’s developers as a necessary step to enhance user security, performance, and privacy. However, this transition is accompanied by serious technical limitations that significantly complicate the operation of many popular tools. The greatest concern is the fate of classic ad blockers, such as uBlock Origin, which rely on the capabilities of Manifest V2 for effective content filtering at the network request level.
Technical Standoff: Manifest V2 vs. Manifest V3
To understand the core of the problem, it’s necessary to delve into the technical details of how extensions interact with the browser. In Manifest V2, the key tool for ad blockers was the webRequest API. This interface allowed extensions to intercept every network request created by the browser, analyze it, and, if necessary, block or modify it before it was executed. This gave ad blocker developers immense flexibility and allowed them to create complex, dynamic filtering rules.
On the other hand, Manifest V3 replaces the webRequest API with the declarativeNetRequest API. The main difference is that now it’s not the extension making the decision to block a request in real-time, but the browser itself. The extension only provides the browser with a list of predefined (declarative) rules. This approach, according to Google and Microsoft, significantly improves performance, as the browser doesn’t need to wait for a response from the extension for every request, and also enhances security, as extensions no longer have access to the user’s full network data stream.
Limitations of the New Standard and Their Consequences
The main problem for ad blocker developers is not the API change itself, but the strict limitations imposed by declarativeNetRequest. In Manifest V3, there is a limit on the number of static rules a single extension can use, as well as an overall limit for all installed extensions. Furthermore, it is much more difficult to implement dynamic updates to filtering lists, which is crucial for quickly responding to new types of ads and trackers.
For example, the popular uBlock Origin uses a combination of massive rule lists and its own scripts to block not just ads, but various UI elements, tracking scripts, and other undesirable content. Porting all this functionality to Manifest V3 within the current limitations is an incredibly difficult task. The developer of uBlock Origin, Raymond Hill, has repeatedly expressed skepticism about the possibility of creating a fully featured version of the extension for the new platform.
Official Microsoft Timeline and Transition Stages
Microsoft hasn’t just announced its intentions but has published a clear timeline for phasing out Manifest V2 in Edge. This process will be gradual to give developers and users time to adapt. According to the official statement dated August 7, 2026, users of test builds of the browser will be the first to feel the changes.
Microsoft Edge (Canary, Dev, Beta channels) will begin displaying warnings that Manifest V2 extensions will soon no longer be supported. Also, V2 extensions will no longer be accepted to the Microsoft Edge Add-ons store.
Full removal of support for Manifest V2 extensions in stable versions of Microsoft Edge for regular users.
Cessation of Manifest V2 support for enterprise customers using appropriate group policies to manage extensions.
What This Means for Edge Users
Once Manifest V2 support is completely ended, all installed extensions of this type, including classic versions of uBlock Origin, Adblock Plus, and others, will be automatically disabled by the browser. Users will not be able to re-enable them. This will lead to ads reappearing on sites, and the level of privacy protection will decrease unless users find alternatives.
This decision by Microsoft highlights Edge’s deep dependence on the Chromium ecosystem and the decisions made by Google. Despite Microsoft’s attempts to add unique features to Edge, fundamental changes to the browser engine are dictated by Google, and Microsoft is forced to follow this course to maintain compatibility and security at the appropriate level.
Alternatives and the Future of Ad Blocking in Edge
The situation is not hopeless for those who want to continue using the internet without ads. There are several possible scenarios. First, developers of popular ad blockers are already working on versions of their products adapted to Manifest V3. For example, uBlock Origin Lite already exists, which is a simplified version of the classic extension and works within the limitations of the new platform. While it is less flexible, it is still capable of blocking most common types of ads.
Second, some browsers, such as Brave or Vivaldi, which are also based on Chromium, have stated their intention to support their own ad-blocking mechanisms at the browser code level, regardless of changes to the extension system. This could make them attractive alternatives for users for whom effective ad blocking is a priority. Microsoft Edge also has a built-in tracking prevention feature, which, while not a full-fledged ad blocker, can significantly reduce the amount of undesirable content.
Ultimately, the transition to Manifest V3 is an inevitable stage in the development of the Chromium ecosystem. It will bring security and performance improvements, but at the same time change the landscape of extensions, forcing users and developers to adapt to new realities. The future of ad blocking in Edge will depend on developers’ ability to create effective tools within the new limitations and on how aggressively Microsoft develops its own built-in protection features.
0 Comments