Google Updates Chrome Extension Policies Amid Security Concerns and Developer Backlash

Google has been updating its Chrome extension policies, a move that has been motivated by a number of factors, including security concerns and developer pushback. Among the most significant changes is the transition from Manifest V2 to Manifest V3, which is designed to enhance security and privacy by limiting the authority of extensions. But this development has been trouble for the manufacturers of ad blockers and privacy applications, who hold that the new model prevents them from offering content filtering effectively.
Manifest V3 introduces several major changes, including to the webRequest API, which numerous content blockers use to block and modify network requests. This change has affected popular extensions like uBlock Origin, which has had to release a more limited version, uBlock Origin Lite, in an effort to comply with the new requirements. The classic uBlock Origin is being disabled on Chrome browsers since it does not support Manifest V3.
The transition process has been complained about by developers, stating that it was difficult for them to adapt to the new framework. AdGuard, for instance, complained about its Quick Fixes and Custom filters not functioning due to the remote code execution policy in Manifest V3. Developers claim that Google has promised content blockers will be supported in Manifest V3 but is not keeping its word as claimed.
Google’s phase-out of Manifest V2 extensions on a gradual basis has also created user fear, with some eyeing alternatives like Firefox or Brave, which remain compatible with legacy extensions. Brave has promised support for Manifest V2 extensions “for now,” though customers must go out of their way to do so.
The transition to Manifest V3 is one of the broader efforts by Google to make Chrome extensions more secure and stable. The company has postponed the deadline for businesses to migrate their extensions until June 2025, providing enterprises with more time to adapt. However, this deadline does not extend to end-users, who will have to update or get their extensions disabled.
The impact of Manifest V3 extends beyond ad blockers. Many other extensions are being affected, and some have been completely disabled as they were unable to accommodate the new framework. This shift reflects Google’s attempt to enhance browser security but also highlights the inconvenience experienced by developers and users in accommodating such shifts.
In addition to the technical problems, Google’s approach has been criticized on how it interacts with developers. It has been said that the company has not adequately met the needs of extension developers, which has resulted in frustration and abandonment feelings. All these problems aside, Google remains adamant on its dedication to supporting content blockers and other types of extensions in Manifest V3, even though the actual implementation is contentious.
With the deadline for Manifest V2 extensions fast approaching, users are advised to check what extensions of theirs will be affected and find alternatives if necessary. The transition to Manifest V3 is a broad overhaul of the extension ecosystem for Chrome, and both have advantages and disadvantages for developers and users.