Match patterns

Match patterns are a way to specify groups of URLs: a match pattern matches a specific set of URLs. They are used by WebExtensions in a few places, most notably to specify which documents to load content scripts into, and to specify which URLs to add webRequest listeners to.

APIs that use match patterns usually accept a list of match patterns, and will perform the appropriate action if the URL matches any of the patterns. See, for example, the content_scripts key in manifest.json.

Match pattern structure

All match patterns are specified as strings. Apart from the special "<all_urls>" pattern, match patterns consist of three parts: scheme, host, and path. The scheme and host are separated by "://".



The scheme component may take one of two forms:

Form Matches
"*" Only "http" and "https".
One of "http", "https", "file", "ftp", "app". Only the given scheme.


The host component may take one of three forms:

Form Matches
"*" Any host.
"*." followed by part of the hostname. The given host and any of its subdomains.
A complete hostname, without wildcards. Only the given host.

host is optional only if the scheme is "file".

Note that the wildcard may only appear at the start.


The path component must begin with a "/".

After that, it may subsequently contain any combination of the "*" wildcard and any of the characters that are allowed in URL paths. Unlike host, the path component may contain the "*" wildcard in the middle or at the end, and the "*" wildcard may appear more than once.


The special value "<all_urls>" matches all URLs under any of the supported schemes: that is, "http", "https", "file", "ftp", "app".


Pattern Example matches Example non-matches


Match all URLs.

(unsupported scheme)


Match all HTTP and HTTPS URLs that are hosted at "" or one of its subdomains.
(unmatched scheme)
(unmatched host)
(unmatched host)


Match all HTTP and HTTPS URLs that are hosted at exactly "".
(unmatched scheme)
(unmatched host)
(unmatched path)

Match only "".
(unmatched scheme)
(unmatched host)
(unmatched path)


Match HTTPS URLs on any host, whose path is "path".
(unmatched scheme)
(unmatched path)
(unmatched path)
(unmatched path)


Match HTTPS URLs on any host, whose path is "path/".
(unmatched scheme)
(unmatched path)
(unmatched path)
(unmatched path)*

Match HTTPS URLs only at "", with any path.
(unmatched scheme)
(unmatched host)

Match only this URL. Anything else.*/b/*/

Match HTTPS URLs hosted on "", whose path contains a component "b" somewhere in the middle.*/
(unmatched path)
(unmatched path)


Match any FILE URL whose path begins with "blah".



(unmatched path)

Invalid match patterns

Invalid pattern Reason
resource://path/ Unsupported scheme. No path.
https://mozilla.*.org/ "*" in host must be at the start.
https://* "*" in host must by the only character or be followed by ".".
http*:// "*" in scheme must be the only character.

Testing match patterns

When writing WebExtensions you don't generally work with match patterns directly: usually you pass a match pattern string into an API, and the API constructs a match pattern and uses it to test URLs. However, if you're trying to work out which match pattern to use, or debugging a problem with one, it can be useful to be able to create and test match patterns directly. This section explains how to do this.

First, open the developer tool settings and check the setting marked "Enable browser chrome and add-on debugging toolboxes":

Next, open the "Browser Console":

This gives you a command line that you can use to execute privileged JavaScript in Firefox.

Because code running in the Browser Console has system privileges, any time you use it to run code, you need to understand exactly what the code is doing. That includes the code samples in this article.

Now paste this code into the command line and press enter:


This does two things:

  • imports "MatchPattern.jsm": this is the system module that implements match patterns. Specifically, the module contains a constructor for MatchPattern objects. MatchPattern objects define a function called matches(), that takes a URI and returns true or false.
  • imports "BrowserUtils.jsm": this includes a function makeURI(), that converts a string into an nsIURI object. nsIURI is the type that matches() expects to receive.

Now you can construct MatchPattern objects, construct URIs, and check whether the URIs match:

var match = new MatchPattern("*://");

var uri = BrowserUtils.makeURI("");
match.matches(uri); //        < true

uri = BrowserUtils.makeURI("");
match.matches(uri); //        < false


Document Tags and Contributors

 Contributors to this page: wbamberg
 Last updated by: wbamberg,