Skip to main content

Guide · SuperchargePerformance

Does uBlock Origin Still Work on Chrome? No (2026 Status)

uBlock Origin's Chrome listing was removed in August 2026, and the extension has not run on stable Chrome since July 2025. What died, when, and what works now.

7 min read Verified Chrome 152

No. Full uBlock Origin has not run on stable Chrome since Chrome 138 shipped on July 24, 2025, when Google disabled every Manifest V2 extension with no way to turn them back on. The Chrome Web Store listing was removed on August 31, 2026, in the MV2 purge, leaving an empty-title placeholder where the install page was. It doesn’t.

Key takeaways

  • Full uBlock Origin has been dead on stable Chrome since Chrome 138 (July 24, 2025). Chrome 151 shipped July 28, 2026 and deleted the last MV2 code paths from the browser.
  • The store listing was removed on August 31, 2026, when Google executed the purge of all remaining MV2 extensions from the Chrome Web Store. There is no page left to install from.
  • On Chrome, your options are MV3 blockers: uBlock Origin Lite, AdGuard, Ghostery. Full uBlock Origin lives on in Firefox.

The uBlock Origin Listing Is Removed. The Extension Is Still Dead.

This is the confusion that keeps the “does it still work” question alive a full year after the answer became no. It looked healthy until August 31, now a placeholder:

FieldStatus (verified September 4, 2026)
CWS listingRemoved August 31, 2026 (now an empty-title placeholder)
Version1.72.2, updated July 8, 2026
Users12,000,000
ManifestStill MV2 (manifest_version: 2 in the listing)
Runs on stable Chrome?No — disabled since Chrome 138, July 2025
Listing removalExecuted August 31, 2026 (per the MV2 timeline)

The confusion is understandable. For most of a year, the listing looked healthy on the store, so readers assumed the extension was still running. It wasn’t. Chrome has refused every MV2 extension since Chrome 138, and the listing itself was removed on August 31, 2026, leaving only an empty placeholder where it used to be.

A previous version of this article said uBlock Origin was back and a reinstall would fix a disabled copy. That was wrong on the point that matters. Removed August 31. Not coming back. Stable support ended at Chrome 138.

When Chrome Actually Killed uBlock Origin

Dates from Google’s MV2 timeline and release tracking. 150/151 from secondary reporting. Checked September 2026:

DateWhat happened
January 2022Chrome Web Store stops accepting new MV2 extensions
June 2024Warning banners appear on pre-stable Chrome channels
October 9, 2024Gradual disabling begins on stable; users can re-enable
March 31, 2025MV2 disabled by default for all users; re-enable toggle still works
July 24, 2025 (Chrome 138)MV2 disabled for everyone, re-enable toggle removed
Chrome 139Enterprise escape hatch (ExtensionManifestV2Availability) removed
June 30, 2026 (Chrome 150)First of two leftover developer flags deleted
July 28, 2026 (Chrome 151)All remaining MV2 code paths deleted from Chromium
August 31, 2026All MV2 extensions removed from the Chrome Web Store

The functional death was July 24, 2025 — 13 months before this update. Everything since has been cleanup. gorhill’s own README says it plainly: end of support on Chrome 139.

Why the Flag Workarounds Died in Chrome 150 and 151

After Chrome 138, two undocumented chrome://flags entries let determined users postpone the shutdown: #extension-manifest-v2-deprecation-disabled and #extension-manifest-v2-deprecation-unsupported. Tech press covered these as the “last resort,” often with garbled names.

Chrome 150 (stable June 30, 2026) removed the first flag and its underlying feature entirely. Chrome 151 (July 28, 2026) deleted the second flag, the exception-list machinery, and every remaining MV2 feature from the Chromium source. This was based on release reporting for 150 and 151, not the source tree. Current stable is Chrome 152, shipped August 25, 2026.

What Still Blocks Ads on Chrome

The MV3 field is more capable than the 2024 doom posts suggested, though the table below is a July snapshot:

uBO LiteAdGuard MV3GhosterySuperchargePerformance
Version (Sep 2026 snapshot)Current, MV35.4.310.5.51 (July 10, 2026)1.4.7
Cosmetic filteringYes (generic off until Complete mode)YesYesBasic
Custom filtersNoYes (5,000 dynamic rules)NoNo
YouTube ad blockingPartial (bundled scriptlets)YesLimitedYes (dedicated layers)
Filter update pathExtension updates only (CWS review)Extension updates for static rulesExtension updatesExtension updates
Beyond ad blockingNoNoAnti-tracking focusTab suspension (session RAM-saved counter), cookie banners

AdGuard made the cleanest migration. Its MV3 build replaced the main listing back in September 2024, and its knowledge base is unusually candid about the costs: filter auto-update is gone, regex rules cap at 1,000, and the filtering log shows assumed rather than exact rule matches. Still the closest thing to full uBO’s flexibility on Chrome, since dynamic rules allow real custom filtering.

Ghostery runs MV3 with declarativeNetRequest and stays actively maintained. Its strength is tracker blocking and its Never-Consent cookie handling rather than maximum ad coverage.

SuperchargePerformance takes a different angle: it was designed for MV3 from the first commit, so no capability was lost in a porting exercise. 195K+ declarativeNetRequest rules compiled from curated commercial-safe sources cover ads, trackers, malware, and phishing, with dedicated blocking layers for YouTube and Twitch video ads. On top of the blocking it does what no ad blocker attempts: tab suspension with an estimate of the memory it has freed, cookie banner auto-dismissal, and popup blocking. Zero telemetry, no account, free core. If the MV2 sunset taught one lesson, it is to prefer tools built for the current platform over ports grieving the old one.

uBlock Origin Lite Is Better Than Its Reputation

uBO Lite absorbed a lot of secondhand scorn during the MV2 wars, some of it repeated by an earlier version of this article. Corrections, from gorhill’s own uBO Lite FAQ:

  • It does have cosmetic filtering. Generic cosmetic filtering is off by default and activates when you raise a site’s blocking mode to Complete. The claim that uBO Lite has none is false.
  • It does inject scriptlets. Rulesets ship with bundled scripts, which is how it attempts YouTube ad blocking. “Structurally impossible under MV3” was never accurate.
  • The genuine losses: no custom filters or list imports (a deliberate design choice), no dynamic filtering, no per-site remote-font or scripting switches, and no response-header filtering, because declarativeNetRequest cannot express those.
  • The genuine bottleneck: filter lists update only when the extension itself updates through Chrome Web Store review. During a YouTube counter-measure wave, that turns same-day filter fixes into a wait measured in weeks.

Its default ruleset hovers around 17K rules against the static-rule pool Chromium shares across extensions, so it is deliberately lean. As a set-and-forget blocker for someone who never touched uBO’s dashboard, it is a fine default. Power users will feel the walls.

Where Full uBlock Origin Still Works

Firefox. gorhill ships stable and development builds for Firefox, Chromium MV2, and Thunderbird, and Mozilla has no MV2 shutdown. On Firefox you keep everything: dynamic filtering, custom lists, the element picker, and filter updates that land the same day a YouTube wave hits.

The Chromium MV2 builds on GitHub serve forks and older builds that still load MV2, not stable Chrome. And the enterprise route closed when Chrome 139 removed the policy key. If full uBlock Origin is non-negotiable for you, the browser is the variable now, not the extension.

What to Do Now

  • Still have uBlock Origin installed and grayed out → uninstall it. Nothing revives it on stable Chrome, and the listing was removed August 31, 2026
  • Want the nearest uBO experience on Chrome → AdGuard MV3 for custom filtering depth, or uBO Lite for a lean zero-config blocker
  • Want blocking, tab suspension, a session RAM-saved counter, and cookie banner handling in one MV3 extension → SuperchargePerformance
  • Refuse to give up full uBlock Origin → move to Firefox; that is the only place it still runs with everything intact

Frequently Asked Questions

Does uBlock Origin still work on Chrome in 2026?
No. As of September 2026, full uBlock Origin cannot run on stable Chrome. Google disabled all Manifest V2 extensions with Chrome 138 on July 24, 2025, with no option to turn them back on. The Chrome Web Store listing was removed in the August 31, 2026 purge of all MV2 extensions, so there is no page to install from. Full uBlock Origin still works on Firefox.
Is uBlock Origin still on the Chrome Web Store in 2026?
No. As of September 2026, the listing was removed on August 31, 2026, in the Chrome Web Store purge of all remaining Manifest V2 extensions. The page now shows an empty placeholder. The extension also has not run on stable Chrome since Chrome 138 disabled every MV2 extension on July 24, 2025, with no re-enable path.
Can I re-enable uBlock Origin with a Chrome flag in 2026?
Effectively no. As of September 2026, Google's official timeline states MV2 extensions have been disabled for all users since Chrome 138 (July 2025), with no re-enable. Two undocumented chrome://flags escape hatches lingered afterward: Chrome 150 (stable June 30, 2026) removed one, and Chrome 151 (July 28, 2026) deleted the other along with every remaining MV2 code path. There is no supported way back.
Does uBlock Origin Lite block YouTube ads?
Partially. As of July 2026, uBO Lite ships scriptlets bundled with its rulesets, so it does attempt YouTube ad blocking — the old claim that this is structurally impossible under MV3 is wrong. The real limits are different: filter updates only arrive when the extension itself updates through Chrome Web Store review, so uBO Lite responds to YouTube's counter-measures in weeks rather than the days full uBO managed on Firefox.
Where does full uBlock Origin still work in 2026?
Firefox. As of July 2026, gorhill still ships stable and development builds for Firefox, Chromium MV2, and Thunderbird. Firefox has no MV2 shutdown, so full uBlock Origin runs there with everything intact: dynamic filtering, custom filter lists, and same-day filter updates. On desktop Chrome, Edge, and other browsers tracking upstream Chromium's extension changes, the MV2 build cannot run.
Is SuperchargePerformance a full ad blocker replacement for uBlock Origin?
No. It blocks ads, trackers, malware domains, and YouTube video ads through 195K+ declarativeNetRequest rules, but full uBlock Origin's cosmetic filtering depth and custom filter support are not its focus. It adds what no ad blocker does: tab suspension, a session RAM-saved counter (no per-tab readout), and cookie banner auto-dismissal. It was built MV3-native, so nothing in it is scheduled for removal.

Don't miss the next release

Be first to know when we ship something new.

Related Articles