Frequently asked questions (FAQ)
uBO Lite (uBOL) is a permission-less 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.
uBOL does not require broad "read/modify data" permissions at install time, limiting its capabilities compared to uBlock Origin or other content blockers that need such permissions upfront.
However, users can explicitly grant extended permissions for specific sites to enhance filtering using declarative cosmetic and scriptlet injections.
To grant permissions on a given site, open the popup panel and select a higher filtering mode like Optimal or Complete.
The browser will alert you to the implications of granting additional permissions, and you must decide whether to accept or decline:
If you accept the request, uBOL can better filter content on the current site:
You can set the default filtering mode from uBOL's options page. If you choose Optimal or Complete as the default, you will need to grant uBOL permission to modify and read data on all websites:
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.
Please note that this is still a work in progress, with the following goals:
- No broad host permissions at install time — extended permissions are granted explicitly by the user on a per-site basis.
- Entirely declarative for reliability and CPU/memory efficiency.
See the Releases section.
Previous releases can be found in the Releases section of the uBlock repo.
All uBO Lite-related issues (including filter-related ones) can be reported here.
uBOL exposes settings that can be defined by administrators through managed storage. See Managed settings.
For more information, check the Wiki.