If you've noticed Chrome extensions behaving differently lately,
you're not imagining it. Google's Manifest V3 transition is
forcing every extension to rewrite how it intercepts network
requests — and not all of them made it.
What Actually Changed
Manifest V2 allowed extensions to use webRequest API to
dynamically block or modify network requests. This is how
uBlock Origin, Privacy Badger, and most ad blockers worked.
MV3 replaced this with declarativeNetRequest — a static
rule-based system. You define rules in advance; the browser
enforces them. No dynamic interception.
The practical difference:
- Ad blockers: Reduced effectiveness for complex filters
- uBlock Origin: The original version stops working. uBlock Origin Lite (MV3 version) has fewer capabilities
- Privacy extensions: Most have migrated, some haven't
- Developer tools: Generally fine — most already updated
What's Happening August 31
Chrome will disable MV2 extensions that haven't migrated.
Users will see a warning banner, then the extension gets
turned off. You can temporarily re-enable in developer mode
but that's not a permanent fix.
Extensions That Won't Survive
- uBlock Origin (non-Lite) — the big one
- Some niche privacy tools built on dynamic request blocking
- Extensions that inject remote code (banned outright in MV3)
What You Can Do
Switch to uBlock Origin Lite — it's the official MV3
version. Less powerful but functional.
Try Firefox — Mozilla has committed to keeping MV2 support.
If you rely heavily on legacy extensions, this is the cleanest
escape route.
Check your extensions — Go to chrome://extensions,
enable Developer Mode, and look for any flagged as MV2.
I put together a full breakdown of every affected extension
category and what the alternatives look like here:
Chrome Manifest V2 Migration: Complete Guide
The August 31 deadline is real. If you manage extensions for
a team or organization, now is the time to audit.
Top comments (0)