the original version doesn't work on chrome anymore, but ublock origin lite does, and it works EXACTLY the same.
An efficient content blocker. Blocks ads, trackers, miners, and more immediately upon installation.
chromewebstore.google.com
it doesn't work exactly the same.
This is the community-maintained issue tracker for uBlock Origin - uBlockOrigin/uBlock-issues
github.com
uBO Lite (uBOL) is a pared-down version of uBO with a best effort at converting filter lists used by uBO into a Manifest v3-compliant approach, with a focus on reliability and efficiency as has been the case with uBO since first published in June 2014.
However the focus on reliability and efficiency in a Manifest v3 environment meant having to sacrifice many features beyond those not possible within a Manifest v3 framework.
uBO Lite home (MV3). Contribute to uBlockOrigin/uBOL-home development by creating an account on GitHub.
github.com
Filtering capabilities which can't be ported to MV3
Because the
declarativeNetRequest API does not support the ability to enforce rules according to the top context, i.e. the URL in the address bar, the following capabilities can't be supported:
The declarativeNetRequest API does not allow to filter according to the content of response headers, thus not possible:
The following filter options can't be translated into DNR rules:
- strict1p, strict3p: whether a network request is same-origin as its initiator
- Entity-based values for domain= filter option (webextensions #394)
- redirect-rule=: the DNR API does not support redirect-if-blocked concept (webextensions #493)
- Regex-based removeparam= modifier filter options
- Exceptions for all modifier filter options are not possible
- Many very useful regex-based filters used in uBO are not allowed, or are rejected by the DNR API (webextensions #344)
- replace=, can't modify the response body (full support is only possible with Firefox MV2)
- ipaddress=, can't use IP address as a condition to block/unblock (full support is only possible with Firefox MV2)
- urlskip=, this requires programmatic steps to extract a URL from another URL (partial support, for strict-blocked pages only)
CNAME-uncloaking is up to each DNR implementation; no DNR implementation supports this capability at the time of writing.
edit:
generated by Ernie 4.5
Sure! Let’s break this down in even simpler terms and compare
uBlock Origin Lite (uBOL) with the regular
uBlock Origin (uBO) for a non-technical audience.
What is uBlock Origin (uBO) vs. uBlock Origin Lite (uBOL)?
- uBlock Origin (uBO) – The full-featured version, works with older browser standards (MV2). It can block almost anything (ads, trackers, annoying elements) with advanced controls.
- uBlock Origin Lite (uBOL) – A stripped-down version designed for newer browsers (MV3). It’s faster and more privacy-friendly but lacks some advanced features due to browser restrictions.
Why Does uBOL Have Limitations?
Browsers like Chrome and Edge are switching to
Manifest V3 (MV3), a new set of rules for extensions. MV3 is meant to improve security and privacy but
restricts how extensions can block content.
- MV3’s main issue: It uses a simpler, less flexible system (declarativeNetRequest API) for blocking requests.
- uBO (old version) could do almost anything because it used MV2, which gave extensions more control.
- uBOL (new version) must follow MV3 rules, so some features are missing or limited.
Key Features Missing in uBOL (Compared to Regular uBO)
1. Per-Site Controls Are Limited
- What’s missing?
- In regular uBO, you can block fonts, scripts, or large media (videos/images) on a specific website (e.g., block Facebook’s tracker but allow YouTube videos).
- uBOL can’t do this because MV3 doesn’t let it check the main webpage URL (address bar) when filtering.
2. No Dynamic or Advanced Filtering
- What’s missing?
- Regular uBO can dynamically adjust rules (e.g., block a popup only when it appears).
- uBOL uses static rules (always on or off), so it can’t adapt in real-time.
- uBOL also lacks regex-based filters (powerful pattern-matching rules used in regular uBO).
3. Can’t Modify Webpage Content
- What’s missing?
- Regular uBO can edit webpage text or remove annoying elements (e.g., change "Subscribe for $9.99" to "Free!").
- uBOL can’t modify page content because MV3 doesn’t allow it.
4. No IP-Based Blocking
- What’s missing?
- Regular uBO can block requests by IP address (e.g., block a known tracker’s server).
- uBOL can’t do this because MV3 doesn’t support IP-based filtering.
5. No CNAME Uncloaking (Advanced Tracker Blocking)
- What’s missing?
- Some trackers hide behind fake domain names (CNAMEs) to evade blocks.
- Regular uBO can detect and block these, but uBOL can’t because MV3 doesn’t support it yet.
Is uBOL Still Useful? (Rule Limit Explained)
- Good news: uBOL still blocks most ads and trackers effectively.
- Rule limit: MV3 caps extensions at 30,000 rules (guaranteed), but Chrome allows up to 330,000.
- Regular uBO could use millions of rules (MV2 had no strict limit).
- uBOL is optimized to stay under 17,000 rules in normal mode, so it’s fine for most users.
Final Comparison Table
| Feature | Regular uBO (MV2) | uBOL (MV3) |
|---|
| Per-site blocking (fonts, scripts, media) |  Yes |  No |
| Dynamic filtering (real-time adjustments) | Yes | No |
| Modifies webpage content (replace text, remove elements) | Yes | No |
| Blocks by IP address | Yes | No |
| CNAME uncloaking (advanced tracker blocking) | Yes | No |
| Regex-based filters (powerful pattern matching) | Yes | No |
| Works within MV3’s 30K–330K rule limit | No (MV2 had no limit) | Yes |
Should You Use uBOL or Regular uBO?
- Use uBOL if:
- You want a lightweight, privacy-friendly blocker.
- You’re on Chrome, Edge, or another MV3-only browser.
- Use regular uBO if:
- You need advanced controls (per-site blocking, dynamic rules, content editing).
- You’re on Firefox (still supports MV2).
Bottom line: uBOL is a good simpler alternative, but regular uBO is still the
most powerful ad-blocker available.
