Google’s Manifest V3 (MV3) is not killing extensions, but it has fundamentally changed how they work, forcing thousands of developers to rewrite their code. The most significant impact is on ad blockers and privacy tools, which now face technical limitations that didn’t exist under the previous Manifest V2 (MV2). This article explains what MV3 actually changes, why Google made the shift, and what it means for the extensions you use daily.
Background: What Is Manifest V3?
Manifest V3 is the latest version of the specification that defines how Chrome extensions are built. Every extension has a manifest.json file that tells Chrome what permissions it needs and what files it uses. The previous version, Manifest V2, had been in place since 2013 and allowed extensions to run powerful background scripts that could execute arbitrary code. MV3 replaces those with service workers, which are event-driven and shut down when idle, and introduces a new permission system that restricts certain network requests.
Google announced MV3 in 2019 and began phasing out MV2 in 2023. As of early 2024, Chrome automatically disabled MV2 extensions for most users, and by June 2024, the Chrome Web Store removed all remaining MV2 extensions. Other Chromium-based browsers like Microsoft Edge and Brave have followed similar timelines, though some offer temporary opt-in flags.
How MV3 Changes Extension Architecture
The core technical change is the replacement of background pages with service workers. In MV2, an extension could keep a persistent background page running in memory, which allowed it to monitor network traffic continuously. In MV3, service workers are ephemeral—they start when an event triggers them and stop after a few seconds of inactivity. This saves memory and improves browser performance, but it also means extensions can’t maintain long-running state without storing it.
The second major change is the declarativeNetRequest API, which replaces the webRequest API for blocking or modifying network requests. Instead of letting an extension intercept and modify each request in real-time, the new API requires extensions to declare a static set of rules in advance. Chrome then applies those rules natively, which is faster and more private, but it limits how many rules an extension can have and prevents dynamic, on-the-fly modifications.
Impact on Ad Blockers and Privacy Tools
The most visible casualty of MV3 is the ad blocker. Popular extensions like uBlock Origin rely on the ability to filter requests based on complex, frequently updated lists. Under MV3, the default limit for static rules is 30,000 per extension, which is far less than the hundreds of thousands of rules that comprehensive filter lists like EasyList contain. While extensions can use multiple rule sets and dynamic rules (up to 5,000), they still face a hard ceiling. uBlock Origin’s developer has stated that the MV3 version is a “lite” version with reduced functionality, and many users have switched to alternative browsers like Firefox, which still supports MV2.
Privacy tools that block trackers or fingerprinting also suffer because they often need to modify responses or inject scripts, which MV3 restricts. For example, an extension that removes tracking parameters from URLs can still work, but one that rewrites page content on the fly may not. The net effect is that MV3 reduces the power of extensions that protect user privacy, while making it harder for malicious extensions to abuse the same APIs.
Why Google Made the Change
Google’s stated reasons for MV3 are improved security, privacy, and performance. The webRequest API allowed extensions to see and modify all network traffic, which was a security risk if an extension was compromised. By moving to declarative rules, Chrome can vet the rules and apply them without giving the extension full access to request data. Service workers also reduce memory usage, which is especially beneficial on low-end devices.
Critics argue that the change is also a business decision, as it weakens ad blockers, which directly threaten Google’s advertising revenue. While Google denies this, the timing and the specific limitations on ad-blocking tools have fueled skepticism. Regardless of motive, the technical reality is that MV3 makes extensions safer but less capable.
How to Choose Extensions Under MV3
When picking an extension now, check whether it has been updated to MV3 and what features were lost. For ad blocking, look for extensions that explicitly state they use declarativeNetRequest and offer a “full” or “advanced” mode, but be aware that they may still be less effective than MV2 versions. For privacy tools, verify that the extension doesn’t rely on blocked APIs; if it does, consider using the browser’s built-in protections instead.
- Read the extension’s description for “Manifest V3” or “MV3” mentions.
- Check the developer’s website or GitHub for known limitations.
- Test the extension on a few sites you visit regularly to see if it works as expected.
- Consider switching to Firefox if you rely heavily on MV2 features, as it still supports them.
Common Problems and Workarounds
One common issue is that extensions may stop working after Chrome updates, especially if they haven’t been updated to MV3. If an extension is disabled, you’ll see a message in your extensions page. You can try re-enabling it, but if it’s still MV2, it won’t work. Another problem is that some extensions lose functionality, like the ability to block elements on a page manually. Workarounds include using the browser’s built-in content settings or finding alternative extensions that use different methods.
Another issue is that service workers can cause extensions to lose state, such as a password manager that forgets your session. Developers have adapted by using storage APIs, but some extensions may still feel less responsive. If you notice this, try updating the extension or clearing its cache.
Comparison: MV3 vs. MV2 for Users
For the average user, the differences are subtle. MV3 extensions generally use less memory and are more secure, but they may have fewer features. Ad blockers are the most affected, with some users reporting more ads slipping through. Other extensions, like password managers or grammar checkers, work similarly because they don’t rely on network interception. The table below summarizes the key differences:
- Background processing: MV2 persistent background pages vs. MV3 ephemeral service workers.
- Network filtering: MV2 full request modification vs. MV3 declarative rules with limits.
- Permissions: MV2 broad permissions vs. MV3 more granular, with host permissions becoming optional.
- Security: MV3 reduces the risk of malicious extensions accessing sensitive data.
Frequently Asked Questions
Will my old extensions stop working?
Yes, if they haven’t been updated to MV3. Chrome disabled all MV2 extensions in 2024, so any extension still on MV2 will be automatically disabled. You can check your extensions page to see which ones are affected and look for updates or alternatives.
Can I still use uBlock Origin?
Yes, but only the “uBlock Origin Lite” version, which is MV3-compliant and has fewer features. The original uBlock Origin is not available on Chrome anymore, but it still works on Firefox, which supports MV2. If you want the full version, you’ll need to use a different browser.
Does MV3 affect other browsers?
Yes, any Chromium-based browser (Edge, Brave, Opera, Vivaldi) will follow Chrome’s lead because they share the same extension ecosystem. Firefox is the main exception, as it uses its own extension system and continues to support MV2. Safari also has its own system, so it’s not affected.
Is MV3 more secure?
Generally, yes. By limiting what extensions can do, MV3 reduces the attack surface. For example, extensions can no longer read all your browsing history without permission, and they can’t execute arbitrary code in background pages. However, no system is perfect, and malicious extensions can still exist.
Can I force Chrome to use MV2?
No, as of 2024, Chrome has removed all MV2 support. There is no official way to enable it, and using unofficial builds or flags is not recommended for security reasons. If you must use MV2 extensions, consider switching to Firefox.
Will MV3 kill all extensions?
No, most extensions will survive, but they may have to change how they work. Developers are adapting, and many popular extensions have already released MV3 versions. The biggest impact is on extensions that rely on deep network access, like ad blockers and some privacy tools.
Related
Method: the standard formula for this calculation, rounded as each result states. See how the calculators work or report an error.
More cards in this drawer
- Luxury V6 Sports Sedan: Can It Easily Top 100k Miles?
- Puppets in TV Shows: Classic Proof They’re Better
- Best Streaming Remote: Top Picks for Every Setup
- Claude Pro Hidden Features Power Users Try
- Tesla Rental Prices: Why They’re So Low255.00 USD
- Best Family Western Movies to Stream Right Now