Quick Links
Google is officially transitioning to Manifest V3, the new Chrome extension specification. The latest version brings new features and, unfortunately, some limitations that will kill some of your favorite browser extensions when it starts rolling out in 2025.
Why Google Is Set to Kill Your Favorite Extensions
In Manifest V2, extensions relied on anAPIfeature dubbed Web Request to monitor traffic while visiting websites, allowing them to block or modify select requests in flight. Using the Web Request API, extensions could, for example, block websites from making requests to certain domains, like those belonging to advertisers, ultimately blocking ads and trackers.
However, malicious actors could also abuse the Web Request to createshady Chrome extensions. Google has long had concerns about malicious actors abusing the Web Request API. That’s why, in Manifest V3, Google moved the blocking functionality to a new API called Declarative Net Request and restricted some previous functionality.
For instance, Google has removed support for remotely hosted code, meaning extensions can only execute scripts included within the package. This gives the company all the power to decide what extensions can and can’t do as they manually review packages before publishing them on the Chrome Web Store. Manifest V3 also limits the number of filtering rules an extension can have, which could hinder the effectiveness of blocking extensions.
According to Google, Manifest V3 will help to bolster the “security, privacy, performance and trustworthiness of the extension ecosystem as a whole.” However, if some of your favorite extensions relied on the removed or limited functionality, they could no longer be effective or, at worst, be gone for good once Manifest V3 is released to everyone.
How to Check Which Chrome Extensions Are Affected
you may check if your extensions are affected by navigating tochrome://extensions. On this page, you’ll see a list of extensions Chrome will no longer support once Manifest V3 goes live.
If one of your extensions is affected, you can hope the developer updates the extension as soon as possible before Google’s deadline. However, you can also seek alternative extensions with the same functionality.
Google has a handyFind Alternativebutton available on the chrome://extensions page for any extension that will be defunct if the developer doesn’t provide an update before the deadline.
Alternatively, switch to another browser like Firefox, which still supports the Web Request API. Most Chrome extensions are also available on Firefox, so you might not miss out on much if you switch. If you’re worried about losing your data, you don’t have to. You can easilyswitch from Chrome to any other browser while retaining your bookmarks and settings.
