Is uBlock Origin dead? What actually breaks on August 31
Two uBlock Origin stories broke in August 2026, and most coverage has merged them into one. They are separate failures with separate fixes. On August 10, 2026, the people who maintain the extension gave up on Facebook feed ads. That call hits every browser. On August 31, 2026, Google pulls the last Manifest V2 extensions from the Chrome Web Store, and that hits Chrome and Edge.
The split matters, because only one of them is fixed by a new browser. A move to Firefox brings the extension back. It does not bring Facebook ad blocking back, since the filters that stopped being updated are the same on every browser.
What is uBlock Origin, and what changed twice this month?
uBlock Origin is a free, open-source ad blocker for desktop browsers, built by a tiny volunteer team and handed out through browser extension stores. Filter lists are the rule files it reads, and they are the same on every browser it runs on. That shared design is why the two August events play out so differently.
| Event | Date | Who is affected | Does switching browser fix it? |
|---|---|---|---|
| Facebook ad filters no longer maintained | August 10, 2026 | Every uBlock Origin user, on every browser | No |
| Manifest V2 extensions removed from Chrome Web Store | August 31, 2026 | Chrome and Edge users | Yes |
The Facebook call came first, posted by the dev team on Reddit and reported by PiunikaWeb the day it surfaced. The team called Facebook a "disgusting anti-user site" whose coders "randomize the order and used to add fake letters" to beat filters. The problem was time, not principle. The project is two people, and Facebook can read any public filter and route around it in days.
The old Facebook rules were not deleted. They just stop being refreshed each time Meta shuffles its page code, so they fade out slowly instead of failing at once.
What happens to Chrome extensions on August 31, 2026?
Manifest V2 is the older Chrome add-on platform that allowed the deep request filtering uBlock Origin needs. Google has been winding it down for two years. The dates below come from a timeline kept by AllAboutCookies.
| Milestone | Date | Effect |
|---|---|---|
| Chrome 138 | July 24, 2025 | Settings toggle permanently disabled |
| Chrome 149 | June 2, 2026 | Last release where command-line workarounds functioned |
| Chrome 150 | June 30, 2026 | Primary enterprise flag removed |
| Chrome 151 | July 28, 2026 | Remaining Manifest V2 flags stripped |
| Web Store purge | August 31, 2026 | All remaining Manifest V2 extensions delisted |
The real effect is narrower than "uBlock Origin stops working" implies. Copies installed on Chrome 138 or earlier stay installed after the purge. They cannot update, and they cannot be installed again, so a new laptop or a fresh Chrome profile has no way back to the full extension. Edge and Opera land in the same place, since both are built on Chromium and follow Google on add-on rules.
Chrome users are not left with nothing. uBlock Origin Lite is the Manifest V3 rewrite, and it stays in the store. Quetta's write-up calls its dynamic filtering "more limited by design" than the original, which is the honest read. It blocks the easy cases and misses the awkward ones.
Which browser should you actually use now?
The answer turns on which of the two failures bugs you more. This blog set out the background in Chrome Security Update AI: 1,072 Bugs, Then 1,442, which covers why Google keeps locking down the add-on platform. Safety and blocking power pull against each other here, and that tug of war is the whole story.
| Browser | Full uBlock Origin after August 31 | Facebook feed ads | Notes |
|---|---|---|---|
| Chrome | No | Not blocked | Existing installs frozen, Lite available |
| Edge | No | Not blocked | Follows Chromium policy |
| Opera | No | Not blocked | Follows Chromium policy |
| Firefox | Yes | Not blocked | Full extension via Mozilla Add-ons |
| Brave | Yes | Not blocked | Shields block advertising without an extension |
Note that the Facebook column reads the same on every row. That is the point most of this month's coverage missed. No browser brings Facebook feed blocking back, because what is missing is filter upkeep, not extension power.
Should you switch, install Lite, or ignore this?
Consider the five common situations below, then pick the one that matches your setup.
- You run Chrome with uBlock Origin and it works today. Nothing breaks on August 31. Your copy keeps going until some future Chrome build trips it up, so treat the date as a planning cue, not a panic.
- You are setting up a new machine or a new Chrome profile. Pick the browser you want first. After August 31 the full extension cannot go back on Chrome, so a fresh profile loses that option for good.
- You want the most blocking for the least effort. Brave needs no add-on at all, since the filtering is built in. That is the short path for a household that does not want to fiddle.
- You want the original extension and its full control. Firefox still backs Manifest V2 and hosts the full extension on Mozilla Add-ons. It is the one mainstream desktop route that keeps what you had.
- You mainly wanted Facebook clean. Nothing fixes that in 2026. Use Facebook in a browser tab rather than the app to cut what it can track, or live with the ads.
Phones are a separate question, and Android's rules keep shifting, as covered in Google Play Age Verification: How It Works on Android. Add-on support on mobile browsers is patchy, so do not assume a desktop fix carries over to a phone.
Sources: PiunikaWeb on the Facebook filter decision, AllAboutCookies on the Chrome Manifest V2 timeline, Quetta on Lite versus the original, Neowin on Facebook's filter evasion.
Originally published on www.nihardaily.com. For more articles like this one, visit www.nihardaily.com.
Top comments (0)