Skip to content
Open
Show file tree
Hide file tree
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
Original file line number Diff line number Diff line change
Expand Up @@ -13,39 +13,58 @@ Due to policy updates in macOS 27, AdGuard may be unable to communicate with its

## Recommended solutions

Since this issue can affect any Chromium-based browser, this section covers how to grant AdGuard the required permissions regardless of which browser is used.
This section covers how to grant AdGuard the required permissions across Chromium- and Gecko-based browsers.

### Step 1: Grant access via Files & Folders

:::note

AdGuard checks folder access **only for your system default browser**. Consequently, the in-app prompts and the _Allow Access…_ button will not appear if the browser is not set as default. In this case, you will need to grant permission manually via macOS _System Settings_.

:::

1. Open _Files & Folders_
- via AdGuard settings: click the gear icon on the app’s main window → _Preferences…_ → the _Assistant_ tab → _Open Files & Folders_
![AdGuard settings](https://cdn.adtidy.org/content/kb/ad_blocker/mac/adguard-settings.png)
- via AdGuard Setup Assistant: on the Browser Assistant installation screen, click _Open Files & Folders_ — this button appears if AdGuard doesn’t have access to the browser’s folder
![AdGuard Setup Assistant](https://cdn.adtidy.org/content/kb/ad_blocker/mac/setup-assistant.png)

- via AdGuard Setup Assistant upon first launch: on the Browser Assistant installation screen, click _Allow Access…_. You’ll be taken directly to the _Files & Folders_ section
![AdGuard Setup Assistant](https://cdn.adtidy.org/content/kb/ad_blocker/mac/setup-assistant-new.png)
- via the AdGuard main window:
- click _Allow access to your browser folder for the Assistant_ at the bottom → _Assistant_ → _Allow Access…_. This prompt only appears if the Assistant was installed at least once and access is currently denied for your default browser. It permanently disappears after the first click. If you don’t see it, use the Preferences option below.
- or click the gear icon in the top-right corner → _Preferences…_ → _Assistant_ → _Allow Access…_

| | |
| :----------------------------------------------------------------------------------: | :--------------------------------------------------------------------------------------------: |
| ![AdGuard popup](https://cdn.adtidy.org/content/kb/ad_blocker/mac/adguard-popup.png) | ![AdGuard settings](https://cdn.adtidy.org/content/kb/ad_blocker/mac/adguard-settings-new.png) |

- via _System Settings_ → _Privacy & Security_ → _Files & Folders_
![System Settings](https://cdn.adtidy.org/content/kb/ad_blocker/mac/system-settings-new.png)
2. Find _AdGuard_ in the list and click it to expand the dropdown
3. Locate the browser (for example, Chrome or Brave) and turn on the toggle next to it

:::note

A toggle for a specific browser will only appear in this list if the browser is already installed. If your browser or Google Chrome is not listed, proceed to Step 2.
A toggle for a specific browser will only appear in this list if the browser is already installed. If your browser, Google Chrome, or Mozilla Firefox is not listed, proceed to Step 2.

:::

### Step 2: If the browser isn't listed
### Step 2: If the browser isn’t listed

**Option A: Install Google Chrome**
**Option A: Install Google Chrome or Mozilla Firefox**

Some browsers, like Opera, rely on the Native Messaging folder that belongs to Google Chrome instead of using a folder of their own. On earlier macOS versions, AdGuard could simply create this folder itself. Starting with macOS 27, however, macOS does not allow AdGuard to request access to Chrome's folder unless Chrome is actually installed. Installing Chrome allows AdGuard to request the required permission.
Some browsers built on Chromium or Gecko do not create their own dedicated Native Messaging directory. Instead, they share the directory used by Chrome or Firefox. On earlier macOS versions, AdGuard could simply create these folders itself. Starting with macOS 27, macOS does not allow AdGuard to request access to these folders unless the corresponding browser — Google Chrome or Mozilla Firefox — is actually installed on the system.

1. Install Google Chrome and open it at least once — the required Native Messaging folder will become available on the system
2. Open _Files & Folders_ (via the AdGuard settings, AdGuard Setup Assistant, or Mac System Settings, as described in Step 1)
1. Install Google Chrome or Mozilla Firefox (depending on whether your browser is Chromium- or Gecko-based) and open it at least once — the required Native Messaging folder will become available on the system
2. Open _Files & Folders_ (via the AdGuard main window, AdGuard Setup Assistant, or Mac System Settings, as described in Step 1)
3. Find _AdGuard_ in the list and click it to expand the dropdown
4. Locate Google Chrome and turn on the toggle next to it. As a result, Browser Assistant will start working in the browser that relies on Chrome's folder (such as Opera).
4. Locate Google Chrome or Mozilla Firefox and turn on the toggle next to it. As a result, Browser Assistant will start working in the browser that relies on Chrome’s or Mozilla Firefox’s folder (such as Opera or Zen).

**Option B: Grant Full Disk Access**

:::caution

Granting _Full Disk Access_ is a last-resort measure: we strongly recommend trying the options above first. _Full Disk Access_ is not required for AdGuard in general. Use it only as a workaround for Browser Assistant if the options above did not work and you fully understand what you are doing.

:::

1. Open _System Settings_ → _Privacy & Security_ → _Full Disk Access_
2. Find _AdGuard_ in the list and turn on the toggle
![Full Disk Access](https://cdn.adtidy.org/content/kb/ad_blocker/mac/full-disk-access-new.png)
Original file line number Diff line number Diff line change
@@ -0,0 +1,46 @@
---
title: How to switch back to v7 after updating to v8.0
sidebar_position: 14
---

:::info

This article covers AdGuard for Windows, a multifunctional ad blocker that protects your device at the system level. To see how it works, [download the AdGuard app](https://agrd.io/download-kb-adblock)

:::

## How to switch back to v7 after updating to v8.0

AdGuard for Windows v8.0 introduces significant changes. If you find the new interface uncomfortable or encounter issues, you can switch back to version 7.

:::note

If you wish to preserve your settings, it’s recommended that you export them before changing versions. You can then import your saved settings after updating the app. The steps needed to do so are listed below.

:::

1. After upgrading to v8, open the folder `C:\ProgramData\Adguard\Backups` and find a ZIP file with a name similar to `adguard_settings_7.22.5008.0-08-04-2025-13_42_15.276.zip`.

2. Copy this ZIP file somewhere outside `C:\ProgramData\Adguard`, for example, to your Desktop. This is important because the folder will be cleaned during the next step.

3. Uninstall v8.0 via _Settings_ → _Apps_ → _Installed apps_. In the uninstaller dialog, check the box to remove all user settings and data so that no v8 leftovers remain.

![Uninstall \*border](https://cdn.adtidy.org/content/kb/ad_blocker/windows/version_8/solving_problems/uninstall.png)

:::note

For step-by-step instructions, see [How to uninstall AdGuard for Windows](/adguard-for-windows/installation#uninstall).

:::

4. Install the previous version. You can find the download link in the _Assets_ section of the latest stable v7 release on [GitHub](https://github.com/AdguardTeam/AdguardForWindows/releases/tag/v7.22.9).

5. Exit version 7 from the system tray to stop filtering.

6. Extract the contents of the ZIP file from step 2 and replace the following files:

- `adguard.db` → `C:\ProgramData\Adguard` — main settings database, including filters and custom rules
- `agflm_dns.db` → `C:\ProgramData\Adguard\FLM` — DNS filter database
- `agflm_standard.db` → `C:\ProgramData\Adguard\FLM` — standard filter database

7. Launch AdGuard. Version 7 will start with your previous settings restored.
Original file line number Diff line number Diff line change
Expand Up @@ -31,6 +31,10 @@ sidebar_position: 1

A handy menu in the Safari toolbar

- [System-wide protection](/adguard-mini-for-mac/features/system-wide-protection.md)

A feature that blocks ads and trackers not just in Safari, but across other apps on your Mac.

- [Full version](/adguard-mini-for-mac/features/full-version.md)

Advanced features that enhance filtering speed and power
Original file line number Diff line number Diff line change
@@ -1,6 +1,6 @@
---
title: Full version
sidebar_position: 9
sidebar_position: 10
---

AdGuard Mini for Mac’s full version unlocks advanced features that provide extra filtering speed and power.
Expand Down
Original file line number Diff line number Diff line change
@@ -0,0 +1,94 @@
---
title: System-wide protection
sidebar_position: 9
---

Starting with version 3.0, AdGuard Mini for Mac introduces _System-wide protection_, a feature that blocks ads and trackers not just in Safari, but across other apps on your Mac.

The feature is available for users with an AdGuard license. You can [purchase the license right away](https://adguard.com/license.html) or click _Try for free_ in _Advanced protection_ to start a 14-day free trial.

## How it works

_System-wide protection_ is built on Apple’s [**URL filter**](https://developer.apple.com/documentation/networkextension/filtering-traffic-by-url), a system filtering API used for system-wide traffic filtering. Here’s how it works.

First, macOS checks a URL against a bloom filter — a prefilter stored on your Mac that updates in the background. Most addresses are cleared locally, with no network request for the check itself.

If the prefilter finds a possible match, macOS asks AdGuard’s server for a verdict using Private Information Retrieval (PIR). This method lets your Mac request data from the server without revealing which exact address it asked about. The request can’t be linked to your account or device. If the server doesn’t respond, the page loads normally.

You can read [a detailed analysis of Apple’s approach to system-wide filtering](https://adguard.com/en/blog/apple-url-filter-system-wide-filtering-api.html) in our blog.

## How to turn on System-wide protection

You’ll find _System-wide protection_ under _Advanced protection_ in the AdGuard Mini app. To enable it, toggle the switch on.

![System-wide protection](https://cdn.adtidy.org/content/release_notes/ad_blocker/mini_for_mac/v3.0/system-wide-protection.png)

When you first enable _System-wide protection_, you’ll get a request to install the URL filter on your computer. Click _Install_, after which a system message will appear requesting to add filter configurations. This is standard macOS behavior. AdGuard does not see or store any of this data.

![System-wide protection requires a URL filter](https://cdn.adtidy.org/content/release_notes/ad_blocker/mini_for_mac/v3.0/install-screen.png)

After you install the URL filter, _System-wide protection_ will remain on by default. If you want it off, toggle off the _System-wide protection_ switch in _Advanced protection_.

You can also click the context menu in the top right corner (⋮) and select _Remove URL Filter_. If you want to reset the filter without deleting it to troubleshoot connection issues, choose _Reset Cache_.

It’s also possible to disable the URL filter in your Mac’s _System Settings_ → _Network_ → _VPN & Filters_ → _Filters & Proxies_. Change _Enabled_ to _Disabled_ in the _Status menu_. AdGuard Mini will then switch off _System-wide protection_ automatically.

## Protection levels

There are three levels of protection you can choose from. _Essential_ is selected by default.

- _Essential_ — blocks ads and trackers
- _Safe_ — blocks ads, trackers, phishing, and malware
- _Family_ — blocks ads, trackers, phishing, malware, and adult content

![Three levels of protection](https://cdn.adtidy.org/content/release_notes/ad_blocker/mini_for_mac/v3.0/levels-of-protection.png)

## Troubleshooting

### System-wide protection doesn’t work with every app or browser

Coverage depends on how each app handles network requests, so some apps may not be filtered. This is a limitation on Apple’s side.

Chromium-based browsers, such as Chrome, Edge, Opera, and Brave, use their own networking code instead of Apple’s frameworks, so the URL filter can’t check their requests.

### System-wide protection doesn’t turn on

- **Your Mac runs an older version of macOS.** Apple’s URL filter needs macOS 26 Tahoe or later. On earlier versions, the setting is disabled and the app asks you to _Update to macOS Tahoe 26 or later_.
- **Your account isn’t supported.** _System-wide protection_ only works with the first user account created on a Mac. If your account was added later, the setting is disabled and shows _Not supported on this Mac account_. See [Can I change my Mac account’s user ID?](/adguard-mini-for-mac/features/system-wide-protection/#can-i-change-my-mac-accounts-user-id) below.
- **You’re on the free version.** To use _System-wide protection_, [purchase an AdGuard license](https://adguard.com/license.html) or click _Try for free_ in _Advanced protection_ to start a 14-day free trial.

### Can I change my Mac account’s user ID?

Yes. _System-wide protection_ only works with the first user account created on a Mac with the user ID (UID) of 501. If your Mac has more than one account, or if you migrated your account from an older Mac, your UID might be different. Follow the steps below to check your UID and, if needed, free up 501 and assign it to your account.

:::warning

This is an advanced, risky operation. Only do this if you have no other option. Freeing up UID 501 means deleting an existing account and creating a new one from Terminal. If something goes wrong, this can cause permanent data loss. Back up all the data on your Mac before proceeding.

:::

1. **Check your current UID.** Open Terminal, type `id -u`, and press Return. If the result is 501, your account already has the right UID. You don’t need to do anything else.

2. **Find out who has UID 501.** If your UID is not 501, run this command:

```bash
dscacheutil -q user -a uid 501 | grep -E '^(name|uid|gecos):'
```

This shows the username, UID, and full name of that account. Make sure you don’t need any files from it, or back them up before continuing.

3. **Delete the account with UID 501.** While logged in to your own admin account, open _System Settings_ → _Users & Groups_, select the account from step 2, and delete it. When macOS asks what to do with its home folder, choose _Save the home folder in a disk image_ — this keeps the account’s files in case you need them later.

4. **Create a new account with UID 501.** Run the following command, replacing `username` and `Name Surname` with the details you want:

```bash
sudo sysadminctl -addUser username \
-fullName "Name Surname" \
-password - \
-admin \
-UID 501
```

`-password -` makes Terminal prompt you for the password interactively; `-admin` gives the new account administrator rights.

5. **Verify the change.** Log in to the new account, then check the UID again: open Terminal, type `id -u`, and press Return. The result should now be 501.
Original file line number Diff line number Diff line change
Expand Up @@ -127,7 +127,8 @@ Some rules can be used only in trusted filters. This category includes:

- filter lists [created by the AdGuard team](../adguard-filters),
- custom filter lists installed as `trusted`,
- user rules.
- user rules,
- pre-approved third-party filter lists available in the *Filters* tab.

### AdGuard Content Blocker

Expand Down
Loading
Loading