uBlock Origin - An efficient blocker for Chromium and Firefox. Fast and lean.
Find a file
2014-07-06 19:14:32 -04:00
_locales toward 0.1.4.0 2014-07-06 19:14:32 -04:00
assets allow new lists to be seen and fetched by users 2014-07-05 11:01:17 -04:00
css smaller font size for help text 2014-07-02 14:12:36 -04:00
dist toward 0.1.4.0 2014-07-06 19:14:32 -04:00
doc an illustration of smaller cpu footprint 2014-07-05 16:48:05 -04:00
img this addresses #7, #11 2014-06-24 21:46:37 -04:00
js toward 0.1.4.0 2014-07-06 19:14:32 -04:00
lib this fixes #12, #37 2014-07-02 12:02:29 -04:00
1p-filters.html this fixes #12, #37 2014-07-02 12:02:29 -04:00
3p-filters.html this fixes #12, #37 2014-07-02 12:02:29 -04:00
about.html this fixes #12, #37 2014-07-02 12:02:29 -04:00
background.html this addresses partially #23 2014-06-28 11:25:37 -04:00
dashboard.html toward v0.1.3.0 2014-07-02 12:28:32 -04:00
LICENSE.txt first commit 2014-06-23 18:42:43 -04:00
manifest.json this fixes #46 2014-07-05 12:56:16 -04:00
popup.html highlight part hit by filter 2014-07-02 16:52:57 -04:00
README.md reordered screenshots 2014-07-05 17:00:35 -04:00
settings.html this fixes #12, #37 2014-07-02 12:02:29 -04:00
stats.html toward 0.1.4.0 2014-07-06 19:14:32 -04:00

µBlock for Chromium

See Change log for latest changes. See Wiki for more information.

An efficient blocker for Chromium-based browsers. Fast and lean.

µBlock: page loaded. ABP: page still loading.

Image excerpted from https://www.youtube.com/watch?v=SzJr4hmPlgQ.

Chromium on Linux 64-bit


Opera 22 on Windows 7 32-bit

The screenshots above were taken after visiting links in [reference benchmark](https://github.com/gorhill/uBlock/wiki/Reference-benchmark) plus a bit of random browsing. All blockers were active at the same time, thus they had to deal with exactly the same workload. Before the screenshots were taken, I left the browser idle for many minutes so as to let the browser's garbage collector kicks in. Also, after a while idling, it's good to open the dev console for each extension and force a garbage collection cycle by clicking a couple of times the trashcan icon in the _Timeline_ tab (this caused a ~15MB drop for µBlock and Adguard in Opera) as garbage collectors sometimes work in a very lazy way, so I did this for each extension.

Installation

From the Chrome store, or manually.

To benefit from the higher efficiency, it is of course not advised to use an inefficient blocker at the same time. µBlock will do as well or better than the popular blockers out there.

Documentation

I think it is pretty obvious, except for this I suppose:

Popup

The big power button is to disable/enable µBlock for the specific hostname which can be extracted from the URL address of the current page. (It applies to the current web site only, it is not a global power button.) The state of the power switch for a specific site will be remembered.

About

µBlock is born out of HTTP Switchboard. All the niceties of HTTPSB have been removed, and what is left is a straightforward blocker which support EasyList and the likes, and also support host files. Cosmetic filters ("element hiding") are supported.

There is nothing more to it. But it does what popular blockers out there do, at a fraction of CPU and memory usage for the same blocking power.

Free. Open source. No donations sought. For users by users.

Without the preset lists of filters, this extension is nothing. So if ever you really do want to contribute something, think about the people working hard to maintain the filter lists you are using, which were made available to use by all for free.

You may contribute by helping to translate this project. I created an entry on Crowdin, where you may contribute to the translation work.

License

GPLv3.