uBlock Origin - An efficient blocker for Chromium and Firefox. Fast and lean.
Go to file
gorhill bc6802df13 update of third-party assets 2014-06-29 18:00:46 -04:00
_locales Update messages.json 2014-06-29 18:40:55 +02:00
assets update of third-party assets 2014-06-29 18:00:46 -04:00
css this addresses #7, #11 2014-06-24 21:46:37 -04:00
dist doc work 2014-06-29 17:52:42 -04:00
doc/img remove irrelevant, cluttering entry 2014-06-28 12:45:45 -04:00
img this addresses #7, #11 2014-06-24 21:46:37 -04:00
js this fixes #28 2014-06-29 12:38:18 -04:00
lib no longer needed 2014-06-28 11:26:09 -04:00
1p-filters.html first commit 2014-06-23 18:42:43 -04:00
3p-filters.html fixed "raced condition" between two onLoad listener 2014-06-23 21:09:31 -04:00
LICENSE.txt first commit 2014-06-23 18:42:43 -04:00
README.md unbloat 2014-06-29 17:31:00 -04:00
about.html first commit 2014-06-23 18:42:43 -04:00
background.html this addresses partially #23 2014-06-28 11:25:37 -04:00
dashboard.html this fixes #16: don't mix with window.addEventListener('load') 2014-06-26 09:46:38 -04:00
manifest.json new revision 2014-06-29 13:58:41 -04:00
popup.html ready for translation 2014-06-24 20:04:34 -04:00
settings.html this fixes #7 2014-06-27 17:06:42 -04:00

README.md

µBlock for Chromium

See Change log for latest changes.

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

Chromium on Linux 64-bit

Opera 22 on Windows 7 32-bit

The above screenshots were taken after visiting many reference benchmark links 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.

More: µBlock vs. ABP: efficiency compared

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.

More at the wiki.

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.

License

GPLv3.