AdGuard is a fast and lightweight ad blocking browser extension
that effectively blocks all types of ads and trackers.
AdGuard.com |
Reddit |
Twitter |
Telegram
AdGuard is a fast and lightweight ad blocking browser extension that effectively blocks all types of ads and trackers on all web pages. We focus on advanced privacy protection features to not just block known trackers, but prevent web sites from building your shadow profile. Unlike its standalone counterparts (AG for Windows, Mac), the browser extension is completely free and open source. You can learn more about the difference here.
AdGuard does not collect any information about you, and does not participate in any acceptable ads program. The only source of income we have is selling premium versions of our software, and we intend to keep it that way.
You can get the latest available AdGuard Extension version from the Chrome Web Store.
You can get the latest version of AdGuard Extension from the Mozilla Add-ons website.
Opera is basically a Chromium browser, but it maintains its own add-ons store. You can get AdGuard Extension from there.
The latest stable version of AdGuard browser extension is available in Microsoft Store.
We are blessed to have a community that does not only love AdGuard, but also gives back. A lot of people volunteer in various ways to make other users' experience with AdGuard better, and you can join them!
We, on our part, can only be happy to reward the most active members of the community. So, what can you do?
If you want to help with AdGuard translations, please learn more about translating our products here: https://kb.adguard.com/en/general/adguard-translations
You can get a beta version of AdGuard Browser Extension for any browser. All necessary information on this topic can be found on a dedicated page on our website.
GitHub can be used to report a bug or to submit a feature request. To do so, go to this page and click the New issue button.
Note
For the filter-related issues (missed ads, false positives etc.) use the dedicated repository.
Here is a dedicated page for those who are willing to contribute.
- node.js LTS
- NPM v8
- yarn v1.22
Install local dependencies by running:
yarn install
Running tests:
yarn test
Run the following command to build the dev version:
yarn dev
This will create a build directory with unpacked extensions for all browsers:
build/dev/chrome
build/dev/edge
build/dev/firefox-amo
build/dev/firefox-standalone
build/dev/opera
To make a dev build for a specific browser, run:
yarn dev <browser>
Where <browser>
is one of the following: chrome
, edge
, opera
, firefox
,
firefox-standalone
, like this:
yarn dev chrome
To run dev build in watch mode, run:
yarn dev --watch
Or for a specific browser:
yarn dev <browser> --watch
Since version v4.0, AdGuard browser extension uses an open source library tsurlfilter that implements the filtering engine.
While developing the browser extension it may be required to test the changes
to tsurlfilter
. Here's what you need to do to link your local dev build
to the local dev build of tsurlfilter
.
-
Clone and build tsurlfilter libraries.
-
Go to the
tsurlfilter/packages/tsurlfilter
andtsurlfilter/packages/tswebextension
directories and runyarn link
. -
Now you can link these packages to the browser extension. To do that run
yarn link
commands in the root directory of the browser extension root directory:
yarn link @adguard/tsurlfilter
yarn link @adguard/tswebextension
- Build the browser extension in the watch mode:
yarn dev <browser> --watch
Before building the release version, you should manually download the necessary resources that will be included into the build: filters and public suffix list.
yarn resources
This command also checks if there are dangerous rules in the filters. See dangerous rules
yarn beta
yarn release
You will need to put certificate.pem file to the ./private
directory. This
build will create unpacked extensions and then pack them (crx for Chrome).
- Ensure you have installed Node.js and Yarn.
- To build the BETA version, run:
yarn beta firefox-standalone
- Navigate to the build directory:
cd ./build/beta
- Compare the generated
firefox.zip
file with the uploaded one.
If you want to analyze the bundle size, run build with the ANALYZE
environment:
yarn cross-env ANALYZE=true yarn <build command>
So, for example, if you want to analyze the beta build for Chrome, run:
yarn cross-env ANALYZE=true yarn beta chrome
Or if you want to analyze all beta builds, run:
yarn cross-env ANALYZE=true yarn beta
Analyzer will generate reports to the ./build/analyze-reports
directory in the following format:
build/analyze-reports
├── <browser-name>-<build-type>.html
Despite our code may not currently comply with new style configuration,
please, setup eslint
in your editor to follow up with it .eslintrc
To download and append localizations run:
yarn locales download
To upload new phrases to crowdin you need the file with phrases
./Extension/_locales/en/messages.json
. Then run:
yarn locales upload
To remove old messages from locale messages run:
yarn locales renew
To validate translations run:
yarn locales validate
To show locales info run:
yarn locales info
Browser | Version |
---|---|
Chromium Based Browsers | 80 |
Firefox | 78 |
Firefox Mobile | 113 |
Opera | 67 |
Edge | 80 |