Adblock: Blocking ads in Wavebox
Wavebox is designed to deliver a streamlined and highly productive web working environment. As part of our commitment to performance, security, and user choice, Wavebox does not include a built-in ad blocker.
Instead, we recommend trusted, industry-leading solutions such as uBlock Origin Lite, which is developed and maintained by experts dedicated to providing robust ad-blocking technology. More information about these extensions can be found below.
During installation, you had the option to add an ad blocker. If you did not select one at that time, you can easily install one at any point by following the instructions outlined below.
How to add uBlock Origin (ad blocker) to Wavebox:
- Open the Chrome Web Store
- In Wavebox, open a new tab and go to https://chromewebstore.google.com/detail/ublock-origin-lite/ddkjiahejlhfcafbddmgiahcphecmpfh?hl
- Add to Wavebox
- On the extension page, click the blue [Add to Wavebox] button.
- Confirm Installation
- A pop-up may appear asking for permission. Click Add Extension to proceed.
- Pin to the Toolbar (optional)
- After adding your first extension, a puzzle piece icon appears in the toolbar.
- Click on the puzzle icon.
- Find the extension in the list and click the PIN icon. The extension icon will appear in the toolbar.
More about uBlock Origin Lite
uBlock Origin Lite (uBOL) is an efficient content blocker that blocks ads, trackers, miners, and more immediately upon installation. uBOL is an MV3-based content blocker. The default ruleset corresponds to uBlock Origin's default filterset:
- uBlock Origin's built-in filter lists
- EasyList
- EasyPrivacy
- Peter Lowe’s Ad and tracking server list
You can enable more rulesets by visiting the options page – click the _Cogs_ icon in the popup panel.
uBOL is entirely declarative, meaning there is no need for a permanent uBOL process for the filtering to occur, and CSS/JS injection-based content filtering is performed reliably by the browser itself rather than by the extension. This means that uBOL itself does not consume CPU/memory resources while content blocking is ongoing – uBOL's service worker process is required _only_ when you interact with the popup panel or the option pages.
Susan Davies