Skip to main content

Advanced Features


You can edit rules to block sites in the options page, as well as in the "Block this site" dialog.

rule editor

You can write rules by match patterns or regular expressions.

Match patterns

Match patterns are URLs including wildcards. You can see the details in MDN web docs.

Here are examples of valid match patterns.

PatternExample matches

(URLs hosted at

(URLs hosted at or its subdomain)

(URLs hosted at and whose path starts with /hoge/)

Here are examples of invalid match patterns.

Invalid patternReason
*://www.qinterest.*/* is not at the start. Use regular expressions instead.
<all_urls>Not supported.

Regular expressions

You can write more flexible rules by regular expressions.

Note that regular expression rules shall be regular expression literals in JavaScript, surrounded by / (e.g. /example\.(net|org)/).

Here are examples of valid regular expressions.

Regular expressionExample matches

(URLs starting with https://www.qinterest.)

(URLs including internationalized domain names)

Here are examples of invalid regular expressions.

Invalid regular expressionsReason
^https?:\/\/example\.com\/Not surrounded by /.
/^https?://example\.com//Inner / are not escaped.

Regular expressions for page titles

To block sites with specific titles, use regular expressions preceded by title.

For example, title/example domain/i blocks sites which titles include "example domain" in a case-insensitive manner.

Unblock rules

Match patterns or regular expressions preceded by @ mean that the specified sites are not blocked.

They can be used to unblock sites that are blocked by subscriptions. For example, if is blocked by a subscription, you can unblock it by @*://*.

Highlighting rules

Match patterns or regular expressions preceded by @N (N=1,2,3,...) mean that the specified sites are highlighted.

For example, you can highlight GitHub by @1*://*.

highlight GitHub

By default, only @1 (blue) is available. To change or add highlighting colors, see the "Appearance" section in the options page.


Comments begin with #. Although any line that cannot be interpreted as a rule is effectively a comment, a # comment is better in two ways.

  1. # comments are guaranteed to be comments even if new syntax is introduced in the future.
  2. # comments can be placed after rules.
# Block pages which URLs are hosted at or its subdomain

/example\.(net|org)/ # Block pages which URLs contain or

Other search engines

This extension supports Bing, Brave (partially), DuckDuckGo, Ecosia (partially), Qwant, SearX (partially),, Yahoo! JAPAN (partially) and Yandex (partially). This feature is disabled by default and can be enabled in the options page.

other search engines

You can also enable it by clicking the toolbar icon when a search result page is open.










"Videos" search will only work if you disable qwant custom links by clicking on "Always read on".

With the lite version of Qwant, the extension only work with "Web" search.




Yahoo! JAPAN





You can synchronize rulesets among devices using Google Drive or Dropbox.

To turn on sync, click the "Turn on sync" button in the options page and select a cloud.

turn on sync

Follow the instructions on the dialog to authenticate.


Once authentication succeeds, your ruleset will be regularly synchronized with the selected cloud.

Google Drive

If you use Firefox or its derivative, you will be required to permit access to

The ruleset is saved in the application data folder on your Google Drive. It is hidden from you, although you can delete it in the settings page of Google Drive.


The ruleset is saved in the /Apps/uBlacklist/ folder on your Dropbox. The folder name may be different depending on your language.


You can subscribe to public rulesets.

To add a subscription, click the "Add subscription" button and enter the name and URL. You will be required to permit access to the origin of the URL.

add subscription

You can show, update or remove a subscription.

manage subscription

Publish a subscription

To publish a ruleset as a subscription, place a ruleset file encoded in UTF-8 on a suitable HTTP(S) server, and publish the URL.

It is a good idea to host your subscription on GitHub. Make sure that you publish the raw URL (e.g.

raw url