
uBlock Origin, Manifest V3, and what to actually do
The problem
If you browse the web using Chrome or a Chromium-based browser, your ad blocker is about to change. Google has started disabling the classic version of uBlock Origin, the web’s most popular adblocking extension.
You are probably seeing a warning in your browser extension console telling you that uBlock Origin is no longer supported and will be disabled soon. This is the result of Google’s long-delayed rollout of Manifest V3, a new extension architecture that alters how extensions interact with web page traffic.
What is Manifest V3?
Manifest V3 is Google’s new system framework for Chrome extensions. Under the old framework (Manifest V2), ad blockers used the webRequest API. This API allowed extensions to intercept every network request made by the browser, analyze it in real time, and block it before the page loaded.
Manifest V3 replaces this with the declarativeNetRequest API. Instead of letting extensions inspect traffic in real time, extensions must now submit a static list of blocking rules to Chrome, and Chrome performs the blocking itself. Google claims this change improves security and performance, but it places strict limits on the number of rules an adblocker can use and stops extensions from fetching dynamic updates without a full store review.
uBlock Origin Lite vs. Classic
To comply with Google’s new constraints, the creator of uBlock Origin developed uBlock Origin Lite. Because of Manifest V3 rules, Lite operates with significant functional differences:
- No dynamic rule updates: The extension cannot fetch fresh filter lists from remote servers. To update its filters, you must wait for the developer to release a new version of the extension through the Chrome Web Store.
- No cosmetic scriptlet injection: Advanced features (such as visual element block selectors or custom scripts to bypass anti-adblock walls) are disabled or severely limited.
- Natively processed rules: Because Chrome handles the blocking rules natively, Lite uses slightly less CPU and memory, making pages load quickly on a normal laptop, but it lets more tracking scripts through.
What you can actually do
You have three main paths forward to deal with the adblocker change:
- Switch to uBlock Origin Lite in Chrome: If you are committed to using Google Chrome, installing uBlock Origin Lite is the least-bad path. It handles basic ads, but you will notice more tracker cookies and complex ad layouts slipping through.
- Switch to Firefox or Zen Browser: Firefox and its forks (such as Zen Browser) are keeping support for the Manifest V2 APIs. This means classic uBlock Origin works perfectly, giving you full dynamic adblocking and cosmetic element filtering.
- Deploy a network-level DNS blocker: Set up a local DNS blocker (such as Pi-hole or AdGuard Home) on your home network. While DNS blocking cannot stop YouTube ads or complex scriptlets, it provides a secondary buffer by blocking tracking domains before they hit your machine.
Real-world lessons for the rest of us
- Browser engine diversity matters. When one company controls the browser engine (Blink/Chromium), they control the API capabilities of all third-party extensions. Keeping a non-Chromium browser installed stops you from being locked into their updates.
- Declarative blocking is the new Chromium baseline. If you choose to stay in Chrome, accept that your extensions are shifting from dynamic, real-time inspectors to static rules lists.
- Keep an alternative browser configured. If you wait until Google fully disables Manifest V2 extensions before testing alternatives, you will be scrambling to export your bookmarks and extension profiles mid-work. Set up a backup browser now.
Bottom line
Google’s rollout of Manifest V3 means your adblocker is getting weaker on Chrome. If you want to keep using Chromium, switch to uBlock Origin Lite and accept the static rule limits. If you want full, dynamic adblocking and element cosmetic filtering, migrate your tabs to Firefox or Zen Browser today.


