Google Has Removed MV2 Extensions from the Chrome Web Store, Including UBO
Source Entity
Hacker News
Google has officially removed Manifest V2 extensions from the Chrome Web Store, impacting popular tools like uBlock Origin. This transition to Manifest V3 marks a significant shift in browser extension architecture and content blocking capabilities.
The Sunset of Manifest V2: A New Era for Chrome
Google has officially completed its transition to Manifest V3 (MV3) by removing all remaining Manifest V2 (MV2) extensions from the Chrome Web Store. This move, which has been in development for several years, represents a fundamental change in how browser extensions interact with the Chrome engine. Among the most notable casualties of this policy enforcement is the popular content blocker uBlock Origin, which relied on the now-deprecated MV2 architecture to function with its high level of efficiency.
The Shift to Manifest V3
The move to Manifest V3 is framed by Google as a necessary step to improve browser performance, security, and privacy. By restricting the ways extensions can intercept and modify network requests, Google aims to minimize the overhead caused by background processes. However, this architectural change fundamentally alters the 'declarativeNetRequest' API, which limits the number of rules extensions can use to block ads and trackers compared to the previous 'webRequest' API.
Impact on Content Blocking
For power users and privacy advocates, the removal of MV2 extensions like uBlock Origin is a point of significant contention. Because MV3 imposes strict limits on the number of filter rules that can be applied, many developers have had to compromise on the efficacy of their ad-blocking algorithms. This creates a tension between Google’s desire for a streamlined, standardized browser environment and the user demand for robust, granular control over web content and tracking scripts.
Broader Implications for Web Ecosystems
This transition reflects a broader trend in the browser industry where platform owners are asserting more control over the extension ecosystem. While the goal is to prevent malicious extensions from hogging system resources or stealing data, the side effect is a reduction in the flexibility that made Chrome a favorite among technical users. Developers are now forced to rebuild their tools within the constraints of MV3, leading to fragmented experiences across different browser platforms that may adopt these standards at varying speeds.
Future Trends and User Adaptation
Looking ahead, we can expect a period of adjustment as developers optimize their extensions for the new API constraints. Users who rely heavily on ad-blocking may look toward alternative browser engines that still support more flexible extension APIs or consider specialized privacy-focused browsers. As Google continues to refine its platform, the balance between security, performance, and user customization will remain a critical metric by which the success of the Chrome ecosystem is measured.