> it's missing the element zapper
Support for element zapper was added more than 18 months ago in version 2025.3.23.1241.[1]
---
[1] https://github.com/uBlockOrigin/uBOL-home/releases/tag/uBOLi...
In Apple's new 'Switch to Safari' campaign details why you should ditch ChromeuBlockOrigin
uBOL-home
JavaScript2023–2026
uBlockOrigin / uBOL-home
uBOL-home
uBO Lite home (MV3)
81Distinct people
101Mentions
0Explicit recommenders
4KGitHub stars
What to know before exploring
What it is
uBO Lite home (MV3)
GitHub
Where it is used
No documented product use was verified in the last source check.
What people are saying
No recommendation phrase was found in the indexed comments.
No classified warning is attached to this page. Read the discussions before treating silence as approval.
Also in these discussions
- gorhill/ublock · linked in 4 of the same discussions
Mentioned in the same Hacker News threads. That is not proof they are substitutes.
This week on Hacker News
Nov 7–Nov 14 UTC · Direct repository links and separately labeled related project stories. Indexed through 11/14/2026, 5:04:57 PM UTC.
No direct repository links were found in the indexed HN discussions over the past seven days. Older discussions are available below.
Mentions over time
HN mentions by year101 dated mentions
Observed mentions: 2023-08-21 23:01:33 UTC to 2026-10-13 19:48:25 UTC.
* An incomplete calendar period is marked with an outlined bar. Its count is not directly comparable with a full period.
Counts come from the repository’s dated source evidence. Index cutoff: 2026-11-02 08:16:59 UTC.
View mention counts and date ranges
| Period | Start (UTC) | End (exclusive, UTC) | Mentions | Submissions | Comments |
|---|---|---|---|---|---|
| 2023 | 2023-01-01 00:00:00 UTC | 2024-01-01 00:00:00 UTC | 10 | 1 | 9 |
| 2024 | 2024-01-01 00:00:00 UTC | 2025-01-01 00:00:00 UTC | 25 | 3 | 22 |
| 2025 | 2025-01-01 00:00:00 UTC | 2026-01-01 00:00:00 UTC | 38 | 2 | 36 |
| 2026 (partial) | 2026-01-01 00:00:00 UTC | 2027-01-01 00:00:00 UTC | 28 | 0 | 28 |
From the project README
An excerpt from the repository, fetched Nov 12, 2026.
Read the project’s introduction
uBO Lite
Browser
Install from ...
Browser
Install from ...
Chrome Web Store
Firefox Add-ons
Edge Add-ons
Safari App Store
Description
Frequently asked questions (FAQ)
uBO Lite (uBOL) is an efficient content blocker based on the MV3 API.
uBOL operates entirely declaratively, meaning no permanent process is required for filtering. The browser handles CSS/JS injection for content filtering, ensuring that uBOL does not consume CPU or memory resources while blocking content. The service worker process is only active when interacting with the popup panel or options pages.
The default ruleset includes at least uBlock Origin's default filter set:
uBlock Origin's built-in filter lists
EasyList
EasyPrivacy
Peter Lowe’s Ad and tracking server list
You can enable additional rulesets by visiting the options page — click the Cogs icon in the popup panel.
Changelog
See the Releases section.
Older releases: Wiki/Release notes (salvaged).
Issues
uBO Lite extension issues can be reported here.
Filter/website issues (ads, detection, trackers, breakage, etc.) need to be reported via the 💬 Chat icon in uBOL while on the affected site.
Support questions can be asked here.
Admin Policies
uBOL exposes settings that can be defined by administrators through managed storage. See Managed settings.
Frequently Asked Questions (FAQ)
For more information, check the Wiki.
Read the full README on GitHubWhat Hacker News says
101 sourcesublock origin lite has a safari extension: https://github.com/uBlockOrigin/uBOL-home
it's missing the element zapper and has some other limitations, but it works pretty well for the most part
combined with ublacklist and sponsorblock it's fairly good coverage for safari
In Apple's new 'Switch to Safari' campaign details why you should ditch ChromeIt lacks a lot of features compared to the "real" uBlock Origin: https://github.com/uBlockOrigin/uBOL-home/wiki/Frequently-as...
In uBlock Origin Lite is back on Firefox add-onsI wonder how true this is now. I believe the functionality in MV3 has increased since it was released.
There's still filters that can't be supported, but it seems like most are.
https://github.com/uBlockOrigin/uBOL-home/wiki/Frequently-as...
https://github.com/uBlockOrigin/uBOL-home/blob/main/chromium...
From "ublock-filters" only 1 filter was unsupported and 90 had unsupported domains dropped out of 10436. From "easylist" 18 out of 56109 filters are unsupported, no unsupported domains.
I'm sticking with uBlock-Origin, but not sure how much of a difference it makes these days.
In Hang on to Your FirefoxAgain, we really need to separate "MV3 - the theoretical idea" and "MV3 - the actual implementation which ships with Chrome". It's two confusingly different worlds.
Nobody should be swaying you to prefer DNR over webRequest (or vice versa) when other browsers show both can be available options for the extensions you use as makes sense for what they try to do/what type you'd like to install. Continuing to support MV2 power levels of functionality does not mean uBO Lite type extensions would need to stop working the way they do, it means uBO type extensions would continue to work the way they do. I.e. the biggest failure of MV3 is not in lacking anything new whatsoever, it's in forcing the removal of a lot of API options which were useful in the name of ulterior motives.
> You can definitely do anything that DNR can do with webRequest, nobo
Read the rest
dy can dispute that. The point is that there are things you can do with uBO lite that you can't do with uBO (and vice versa!). It's not a straight downgrade, there are powerful new features.
It's like you sold your house for a mobile home but tell the neighbor it's not a straight downgrade because it's red. Great, but why are we praising that instead of painting the house red?
Funnily enough, this morning I ran across another feature I didn't realize was missing in MV3 https://github.com/uBlockOrigin/uBOL-home/discussions/369. Perhaps keeping the functionality to know what was actually blocked to the extension was too powerful.
https://github.com/uBlockOrigin/uBOL-home/wiki/Frequently-as... has a few of the more practical concrete examples. Namely content can load without the blocker being ready to filter, CNAME cloaking can't be handled properly (in Chrom* at least), and the filter rules aren't as flexible.
Interestingly, the rule count limits themselves do not (currently) seem to be much an issue despite it being one of the more common concerns on the original MV3 announcement.
In Google Has Removed MV2 Extensions from the Chrome Web Store, Including UBOuBOL bug report: https://github.com/uBlockOrigin/uBOL-home/issues/438 , from discussion https://github.com/uBlockOrigin/uBOL-home/discussions/408#di...
uBOL doesn't work in apps, it works only in Safari, it's a pure browser extension, the "app" part of uBOL is an Apple requirement just for the sake of installing the extension.
Copied from #408:
uBOL will stay a webextensions-based browser extension, I do not plan to go further than this, I do not have the time and motivation to take on more work than I already do.
What people may ask though is that Apple maybe supports webextensions in WebApp, if that is possible at all.
I hope this changes, it’s what keeps me on AdGuard :-/
In Firefox for iOS now has a native adblocker> all answers I've found in Google to this question say there is no element picker
Because Google feeds on comments like yours to answer your question about whether there is an element picker, it's bound to be wrong.
You can create your own custom filters using an element picker, and you can manually edit them. See <https://github.com/uBlockOrigin/uBOL-home/wiki/Quick-guide>.
In Firefox is now the last major browser that still supports uBlock OriginAbsolutely not. This is exactly why people have a problem with Chromium, which now has some of the same restrictions on extensions as Safari (Manifest V3).
- uBlock Origin works best on Firefox: https://github.com/gorhill/uBlock/wiki/uBlock-Origin-works-b...
- uBlock Origin Lite FAQ: https://github.com/uBlockOrigin/uBOL-home/wiki/Frequently-as...
In Firefox is now the last major browser that still supports uBlock OriginYour Internet points on the leaderboard do not make you a moderator on the site. But farming points is easy if you selectively reply to or make decisive comments. It's a pattern for most of the leader board if you actually look into what they reply to https://news.ycombinator.com/leaders
https://github.com/uBlockOrigin/uBOL-home/wiki/Frequently-as...
You could have found that link in 30 seconds on Google if you actually wanted to know
In Microsoft Edge is about to lock out older ad blockers, just like Chrome didRules are limited (in syntax and number) and you can only ship updated rules with updated extensions (at least you can skip the queue if you only update rulesets but it's VERY annoying to do). It's also missing a bunch of features: https://github.com/uBlockOrigin/uBOL-home/wiki/Frequently-as... (I see here that replacing response body is possible with Firefox only, is that your use-case?). MV2 was miles better.
In Microsoft Edge is about to lock out older ad blockers, just like Chrome didIt cannot do dynamic filtering [1]. Another big one I forgot about is no CNAME uncloaking. Don't get me wrong, uBOL is still a great add on, it's just not possible to do everything you could with the manifest v2 version.
[1] https://github.com/uBlockOrigin/uBOL-home/wiki/Frequently-as...
In Safari Technology Preview 248 ReleasedThis is HN. The topic has been discussed so many times already. Please read the developer's post about it.
https://github.com/uBlockOrigin/uBOL-home/wiki/Frequently-as...
In Google Chrome update will close the door on ad blockersuBlock Origin Lite's author disagreed.[1]
[1] https://github.com/uBlockOrigin/uBOL-home/wiki/Frequently-as...
In Chrome is looking to permanently drop MV2 extensionShowing the 15 most recent of 101 sources. Enable JavaScript to search and browse every indexed mention.