Adguard Release Notes

AdGuard for Android v4.15 is a small update focused on usability improvements and bug fixes. While this release doesn’t introduce major new functionality, it brings a few long-requested enhancements designed to make everyday use of AdGuard more convenient.

Temporary protection pauses

One of these improvements is the new option to temporarily pause protection. When disabling protection, you can now choose to have it automatically turn back on after 30 seconds, 2 minutes, or 5 minutes.

This feature is particularly useful when you need to check whether a website, app, or network issue is related to filtering. Instead of disabling protection and having to remember to turn it back on later, you can set a timer and allow AdGuard to restore protection automatically. It’s a small quality-of-life improvement, but one that can save time and help ensure you don’t accidentally leave your device unprotected after a quick test or troubleshooting session.

Changelog

Improvements

• Added pause protection for Android
• Added faster navigation in Recent activity
• Improved the update checker to ensure it also detects newer versions of the AdGuard app
• Added HTTPS filtering support for Titanium Browser
• Optimized Samsung Pay service detection to prevent unnecessary background activity on devices where Samsung Pay is not installed

Fixes

• Huawei TileService is not recreated after changing the app’s status
• A grey line is visible when playing a video in fullscreen mode in Private browser
• The proxy enable/disable button notification doesn’t disappear after enabling Integration mode
• The video doesn’t pause when switching from AdGuard player to YouTube
• DNS protection on Android TV could unexpectedly turn itself off after updating to v4.13
• Custom filters and Custom DNS filters appear as updated during every update check
• AdGuard intermittently stops blocking domains included in DNS filters
• A duplicate lastpass.com entry in the default HTTPS allowlist
• Excessive memory usage in certain scenarios
• Changes to plus_cached_state could trigger unnecessary protection or VPN restarts

Corelibs (Filtering engine)

• CoreLibs updated to v1.23.0

DnsLibs (DNS filtering engine)

• DnsLibs updated to v2.10.2

Original source

In AdGuard for Mac v2.20, we’ve renewed the app’s visual style, changed the UX workflow related to system permissions in macOS, added new browsers to the default filtering list, updated our filtering engines, and fixed a number of bugs.

System permissions for AdGuard

AdGuard requires Files and Folders permission to install and verify AdGuard Browser Assistant in Chrome, Edge, and Gecko-based browsers.

In macOS 27, access to third-party browser profile folders has been restricted. Previously, when access was denied, AdGuard displayed a Not supported status, which didn’t make it clear for users that the issue could be resolved by granting additional permissions.

In AdGuard for Mac v2.20, we’ve improved this workflow:

• The Not supported status is replaced with an Allow access button on the Assistant tab. It opens Files and Folders settings, where you can grant the required permission. Once access is granted, you can install the Assistant
• A notice is added to the main window. It appears if your default browser isn’t Safari and AdGuard doesn’t have access to its folder, and takes you to the Assistant tab
• The Enable Browser Assistant notice now appears when the Assistant isn’t installed in your default browser. You can dismiss it by clicking on the > button
• The first-launch wizard now uses the same Allow access button

These changes should make AdGuard for Mac more convenient for users who prefer third-party browsers on macOS.

Other changes

We’ve expanded the list of browsers filtered by default, adding popular names like DuckDuckGo and Naver Whale. Also, AdGuard for Mac now supports LibreWolf. Plus, we’ve set up a Compatibility repository in GitHub, where users can submit their browser support issues, or even open pull requests for us to review and put out the necessary changes in later updates.

We’ve also added Quad9 to the list of DNS providers that support DNS-over-QUIC.

The app’s visual style is being refreshed as well: we renewed the logo and system tray icons, updated the description of the Block WebRTC setting, and removed the Block Java setting. Lastly, we’ve fixed a number of bugs that interfered with the app’s correct functioning and updated CoreLibs and DnsLibs.

Changelog

Improvements

• Introduced compatibility lists specifically for AdGuard for Mac #5
• Removed the Block Java setting #1705
• Updated AdGuard icons and logos, copyright year, and capitalization #1706

Fixes

• Scrollbar malfunction in the Filtered applications tab #1192
• A bug causing the main app window to automatically pop up during macOS startup #1699
• Inaccurate titles within AdGuard’'s Settings/Preferences screens #1734
• Erroneous User rules filter timestamp is hidden until modified #1737
• Unexpected Noname entries in Filtered Applications menu #1772
• Firefox filtering state not retained in AdGuard for Mac v2.20 beta build #1774
• Excessive disk writes caused by the agflm_standard.db journal mode #1710
• Text and icon colors of the Settings tabs do not match system behavior #1696

CoreLibs (Filtering engine)

• Updated CoreLibs to v.1.22.29 #1754

Improvements

• Prevented domain leaks for Local.adguard.org resolution while protection is turned on #1854
• Added support for filtering of HTTP/3 proxies #1957
• Refined the Do Not Track utility to avoid dispatching DNT/GPC headers to incompatible browsers #1982
• Enabled HTTP/3 filtering out of the box for Beta and Nightly testing channels #2014
• Turned on HTTP/3 filtering by default for all stable release users #2015
• Synchronized verification caching rules to match Chrome’'s implementation standards #2025
• Added full support for filtering HTTP/2 proxy connections #2054
• Changed the evaluation of iframe size for content script injections #2059

Fixes

• Parsing errors occurring within match_context_create routines #124
• Freezing of Firefox with a Host contacted, waiting for reply status due to locked TCP socket connections #2058
• Latency issues in QUIC/HTTP/3 processing leading to automatic fallbacks to HTTP/2 #2062
• OCSP validation routines failing to properly block connections targeting compromised or revoked SSL certificates #2069

Scriptlets (JavaScript enhancement for filtering rules)

• Updated Scriptlets to v2.4.2

Improvements

• Added the google-ima3-dai redirect rule #239
• Introduced the trusted-json-set scriptlet #308
• Expanded JSON-focused scriptlets to support advanced JSON path queries #522
• Enhanced log-addEventListener with a parameter to manage overriding addEventListener #551

Fixes

• cancelBubble causes unexpected errors in trusted-click-element #555

ContentScript

• Updated ContentScript to v3.2.0

DnsLibs (DNS filtering engine)

• Updated DnsLibs to v2.10.1 #1742

Improvements

• Added ability to update upstreams list without reloading filters #248

Fixes

• Crash caused by segmentation error during DNS proxy setup on MIPS routers #136
• Missing TCP filtering within Apple Network Extensions #264
• Intermittent failures during DNS-over-TLS upstream availability checks #263
• Missing AdGuard certificate issues on hitomi.la

Original source

In this release we’ve added AdGuard’s Manifest V3 (MV3) Browser Extension to Microsoft Edge.

As of now, Manifest V2 (MV2) ad blockers no longer appear in Edge Add-ons search results. This is part of Microsoft’s policy on moving away from MV2 extensions, which the company announced in August.

But this doesn’t mean AdGuard is leaving the store. This is where our MV3 version comes in.

What changes with MV3

With MV2, the extension sees each network request in real time and decides what to block. This changes with MV3: the browser receives a prebuilt ruleset and applies it itself.

This means the number of active rules is limited in MV3, some traditional filtering rules cannot be converted exactly, and most filter updates now ship with the extension itself, so updates can take longer.

For most people, everyday filtering stays close to MV2. Still, the browser now handles more of the decision-making, and keeping behavior close to our MV2 version takes more work. But we’re up for it.

Setting up

To use custom filters and user rules, turn on Allow user scripts for the AdGuard Browser Extension in Edge. Here’s how to do that:

Open edge://extensions, or click Extensions → Manage extensions Find AdGuard and click Details Turn on Allow User Scripts

This will allow the MV3 extension to work as intended.

Changelog

Improvements

• Added AdGuard MV3 Extension to Microsoft Edge

Original source

AdGuard for Android v4.14 is focused on improving compatibility and making ad blocking work seamlessly with the privacy tools you rely on every day.

A smarter Recent activity screen

Recent activity is becoming more flexible and customizable. With the upcoming filtering options, you’ll be able to refine which network requests are displayed based on criteria such as applications, companies, event types, and statuses. This makes it easier to focus on the information that matters most and navigate large activity logs more efficiently, giving you greater control over how network activity is presented.

Better filtering

Filtering for browser proxy and VPN extensions has also been significantly improved. Previously, traffic from these extensions had to be downgraded to HTTP/1 for filtering. AdGuard now supports full filtering over HTTP/2 and HTTP/3, providing better compatibility, more reliable protection, and a smoother browsing experience without sacrificing performance.

Changelog

Improvements

• Added a new button to export filtering log
• Added a new version available notification as a red dot above the AdGuard icon
• Added status indicators for apps in the App Management section
• Added AdGuard to the list of Device administration apps in system settings
• Allowed encrypted fallback and bootstrap DNS servers
• Added the Search field on the Websites exclusions screen
• Added a filter to Recent activity to hide duplicate entries
• Implemented smart search for the Recent activity screen

Fixes

• Several issues in Recent activity (TLS details), including inconsistent wording and missing ClientHello and TLS version information
• The Add blocking rule button is incorrectly displayed for QUIC connections blocked by the Filter HTTP/3 option
• The router’s web interface is inaccessible after a reboot when the Wi-Fi gateway route is unexpectedly included in the VPN
• Screen rotation glitches in landscape mode when using video players in the private browser
• Holding down backspace in the Add blocking rule field does not trigger continuous character deletion
• AdGuard protection is not automatically enabled after reboot when using Always-on VPN
• Background playback doesn’t work in AdGuard’s YouTube Player
• AdGuard protection gets stuck in a restart loop

CoreLibs (Filtering engine)

• CoreLibs updated to v1.22.28

DnsLibs (DNS filtering engine)

• DnsLibs updated to v2.10.1

Original source

A brand-new version, a new major number, a fresh design — and, most importantly, truly system-wide protection. AdGuard for Windows v8.0 doesn’t just look different: it gives you clearer control over the traffic on your computer and makes the most important settings easier to reach.

Truly system-wide protection

Alongside the DNS filtering you already had, AdGuard offers full-fledged network-level filtering. This means stronger protection and more control: you can filter all Internet traffic on your device, so your protection is system-wide.

AdGuard uses a special network driver that handles the actual sending and receiving of data, allowing us to filter traffic from every app on your device.

While DNS filtering is still there, it is less flexible, and some tracking requests can still get through. This is where HTTPS filtering becomes essential. With it enabled, AdGuard can inspect traffic within Windows apps. This allows us to distinguish between legitimate content and tracking requests, even when they come from the same domain. By decrypting the traffic, AdGuard can identify the full URL and block only the tracking requests while leaving the rest of the app working just fine.

While HTTPS filtering is enabled for browsers by default, it is disabled for most other apps to ensure better compatibility. You can always enable it for extra protection: just select the application you want to filter in

App management

and toggle on

Filter HTTPS traffic

.

See what your apps are doing and take control

To make managing traffic easier and give you a clear picture of what’s happening on your device, we’ve added two new sections:

App management

and

Statistics

.

App management

App management

lets you control how each app accesses the Internet. By default, AdGuard filters everything. As soon as an app goes online, it appears in

App management

, and its traffic is routed through AdGuard. From there, you can configure what to do with the app and how to filter it:

• Decide which apps have their traffic routed through AdGuard
• Choose to block ads and trackers in specific apps
• Enable HTTPS filtering in apps of your choice

We’ve also introduced

Filter unknown apps

, a new setting for handling apps that are not yet in the compatibility or exclusion lists. It’s on by default — new apps get regular filtering, while HTTPS interception stays off to avoid affecting app behavior.

Statistics

Statistics

show detailed network activity. The

Companies

section provides a perspective on all the companies that your device has sent requests to, while in

Apps

and

Domains

you see the stats specific traffic data for every app routed through AdGuard. You can quickly identify and block anything suspicious.

Not only inside updates: A complete redesign

AdGuard for Windows has been completely redesigned. Our focus was on simplicity and ease of use. The most important tools are now front and center, while advanced settings are still available — just tucked away so they don’t overwhelm new users.

Key settings in plain sight

The app is designed to let you enable everything you need straight from the first screen. Just click the symbols you see — they stand for blocking ads and trackers, handling cookie notices and similar annoyances, and DNS protection.

Fine-tune your protection

: Head to the

Protection

section, where settings are clearly categorized, explained in simple terms, and enabled by one toggle.

Tracking protection

: Choose a level of protection — from a simple, comfortable experience to a more advanced one, which includes deleting cookies for enhanced privacy. There is also a custom level where you can freely fine-tune everything to suit your preferences: like blocking notifications from websites or enabling anti-DPI protection.

Advanced approach to filtering

: You can find low-level and network settings in

Settings → App settings
.

For more details on new features,

check the Knowledge Base
.

It’s been a huge overhaul, and we can’t wait to hear what you think. Share your thoughts and send improvement ideas via

GitHub Issues
.

Original source

Improved user rule editing

This release brings a streamlined user rule editor, the new Mail Tracking Protection filter, and a few quality-of-life upgrades for Chrome MV3.

The User rules section now uses RulesEditor instead of Ace. The new editor has two modes: List view, which displays your rules as a searchable list with checkboxes to quickly enable or disable individual rules, and Editor view for direct manual editing. An overflow menu in the top-right corner gives you quick access to Rule syntax help, Import, Export, and Delete all options.

Here’s what the old rule editor looked like:

And here are the two modes — Editor view on the left and List view on the right — of our new editor.

The Allowlist section now also runs on RulesEditor and has an improved overflow menu.

New Mail Tracking Protection filter

We’ve added a new Mail Tracking Protection filter that removes tracking pixels — invisible 1x1 images that are used to tell senders when an email has been opened. These trackers can’t be blocked by domain alone, since most email services proxy images through their own servers. Instead, this filter uses other signals to catch them without breaking legitimate images.

More accurate filter update dates

Previously, the Filters tab in MV3 settings showed the extension’s update date for all filters, no matter when the filter itself was last updated. We updated the filter metadata handling so the Last updated field now shows the filter’s real update date.

$urltransform modifier for advanced users

For advanced filter makers, v5.5 adds support for the $urltransform modifier. It lets a rule rewrite parts of a URL — like its path or query string — before the request goes out, including redirects handled through Chrome’s MV3 declarativeNetRequest API. This makes it possible to strip tracking parameters and other unwanted bits from URLs without blocking the request entirely.

Changelog

Improvements

• Added filter rule conversion error logging in MV2
• Added a new rule editor with dedicated list and editor views
• Aligned internal RuleSet / ruleSet identifiers to Ruleset / ruleset to match the renamed linked libraries (@adguard/dnr-converter, @adguard/tswebextension)
• Filtering log now accumulates declarativeRuleInfo.sourceRules across multiple DNR matches for the same event instead of overwriting the previous value
• Aligned RuleActionType enum casing to PascalCase (BLOCK → Block, etc.) to match the @adguard/dnr-converter API
• User rules error reporting in MV3 now logs dynamic rule conversion errors
• Improved visibility of UI controls in OS high-contrast mode (forced-colors: active): switches, action buttons, editor, dropdowns, and modal-like cards on Options/Popup pages
• Updated [@adguard/dnr-converter] to v1.1.0
• Updated [@adguard/rules-editor] to v2.0.0

Fixes

• Element hiding rules not being applied on fast page reload in MV3
• Filtering log loses events during window.open() tab redirects
• Filtering log events for tabs closed by $popup modifier rules are now displayed as linked to the background page
• The Send ad filters usage option with CSS rules containing ::before or ::after causes visible content on the page
• WebRTC IP handling policy changed from disable_non_proxied_udp to default_public_interface_only to reduce VoIP breakage while still preventing IP leaks
• Firefox freezes when playing Douyin videos, triggered by custom filter rule all.txt
• Sites loading-slowly in Firefox 118 when AdGuard extension is enabled
• Scroll bar missing in the filtering log
• Allowlist editor now accepts bare compound public suffixes (e.g. gov.br, co.uk, com.au) while still rejecting single-label TLDs
• The request for additional permissions is not asked when importing extension settings
• monkeytype.com fails to load — requests stuck pending with AdGuard MV2 enabled
• Cosmetic rules with a regex in the $domain modifier containing multiple escaped separators (e.g. [$domain=/example\d*.(live|com|icu|org)$/]##body) not being applied
• Expanded wildcard TLD domains in DNR conversion for $domain and $to modifiers
• Scriptlet exception rules with comma-containing arguments now work correctly
• Generic scriptlet rules (scriptlets without a domain restriction) now appear in the filtering log

TSUrlFilter (AdGuard Browser Extension filtering engine)

• Updated [@adguard/tsurlfilter] to v6.0.2

Improvements

• Added $urltransform modifier support
• Added $removeparam support for SPA navigations
• Default registered script is always added to local script rules
• Migrated declarative network rule conversion from @adguard/tsurlfilter/es/declarative-converter to the dedicated @adguard/dnr-converter package

AGTree (A tool for working with adblock filter lists)

• Updated [@adguard/agtree] to v4.2.0

Scriptlets (JavaScript enhancement for filtering rules)

• Updated [@adguard/scriptlets] to v2.5.0

TSWebExtension (Library wrapper for Browser API and TSUrlFilter)

• Updated [@adguard/tswebextension] to v5.0.0
• Updated [@adguard/extended-css] to v2.2.0 (sub-dependency of [@adguard/tswebextension])

Original source

Please welcome the much anticipated AdGuard for Android v4.13! We set ambitious goals for this release, and did our best to deliver: a lot of work was done both in terms of big features as well as the usual behind the scenes routine of fixing bugs and oiling gears for a better performance. Let’s see the details below.

With this release, we introduced differential filter updates to AdGuard for Android! To achieve this, we integrated the FiltersListManager library into the app. Now, your filters will load automatically without consuming tons of traffic and overloading servers.

We also added post-quantum cryptography support to DnsLibs. Now AdGuard for Android, like our other full ad-blocking products, keeps your DNS requests protected against future threats.

Another significant change is our adoption of CRLite by Mozilla to verify revoked certificates. Using this instead of the more outdated OCSP (Online Certificate Status Protocol) or letting the app check each certificate against the CRL (Certificate Revocation List) not only speeds up website loading, but also increases your privacy and safety while browsing.

To improve security in Integration mode with AdGuard VPN, we changed the connection protocol, introducing the use of credentials. With the release of AdGuard for Android v4.13, our ad blocker and VPN cooperate seamlessly and securely, with no additional action required on the user’s part for them to synchronize. No third-party apps will be able to spy on your activities, as an added bonus.

In previous versions, in-app instructions for installing HTTPS certificates were added, as the process could differ in regards to your device’s make and model. In AdGuard for Android 4.13, we added support for ColorOS (Oppo) to those instructions.

And last, but not least, we have done a lot of work on our filtering engines and fixed bugs that had accumulated over time. Scriptlets and CoreLibs were updated for better app performance.

You can consult the changelog below to see all the fixes and improvements.

Changelog

Improvements

• Added possibility to copy an applied rule in request details in the filtering log
• Added support for Google Backup
• Excluded 2ndLine application from filtering by default
• Displayed information about updated DNS filters in the DNS list
• Added possibility to copy package_name in request details in the filtering log
• Improved the Check for updates button’s behavior on the update check screen
• Eliminated the possibility to add an empty user rule through the recent activity tab
• Added color distinction for updated content on the Updates screen
• Improved voicing of TalkBack voice assistant elements for Private browser
• Restructured the inputs/dialogs in Tracking protection
• Updated crash reports and app usage data names and dialogs
• Added the option to find requests by applied rules in recent activity
• Added validation to Mask your IP address screen
• Added auto-refreshing of the webpage after toggling the Website protection switch for it in Private browser
• Added authentication for the local proxy
• Added possibility to clear .hprof when it’s not needed
• Added an app update error screen for TV
• Improved video playback in the YouTube player in the background and picture-in-picture (PiP) mode

Fixes

• A blocking rule for the $network type is added via the Add allowing rule button in request details
• The Disable all? popup appears on the User rules screen even if the rules list is empty
• CA certificate installation instructions are not relevant for ColorOS
• DNS filters shows null instead of the time of the last update
• Firewall is activated automatically after granting the Usage access system permission
• High battery consumption starting from v4.12
• Impossible to block a domain, unblocked in DNS filter, using the filtering log only
• Incorrect subdomains appear in statistics
• Many apps stop working when AdGuard is active
• Recent activity log lags heavily after updating to v4.12.1
• Problems while editing extensions in language modes other than English
• Recent activity log fails to be cleared instantly in AdGuard v4.14 nightly 4
• Subdomains duplicate in Statistics
• The custom DNS server disappears after importing settings that were just exported
• The title of videos doesn’t minimize when clicking the share button while in horizontal mode
• Turning on AdGuard using tile closes the notification panel
• Filters update without authorization
• User regex in Ad blocking and DNS filtering rules breaks after AdGuard v4.14 nightly 5
• When attempting to update a beta version (e.g. RC), the update proceeds to the latest release version
• Configuration can’t be imported via link, even if the versions are consistent
• Rules duplicate themselves in the Applied rules section
• Failed to move the AdGuard Personal CA to the system store via the Move button in the app
• Custom content filter lists disappear after time
• Protection resumes every few seconds with HTTPS filtering and FakeDNS enabled
• An error snack appears after editing a userscript
• The switch on the Extensions setting does not respond when tapping the setting name
• After rebooting the phone, blocked URLs no longer show the reason why they were blocked in the log
• The Protection may not work properly while the hotspot is active notification is displayed for Android 10+
• Impossible to add a blocking rule with additional modifiers from Recent activity
• Impossible to select a custom DNS server by tapping Save and select
• Actual DNS protocol doesn’t match with what is shown on the DNS server details screen after settings import
• Empty space below the navigation bar after opening extensions editor
• AdGuard does not start after reboot
• Incorrect display of onboarding for certificate installation when importing settings via a link
• Integration mode dialogue doesn’t open consistently at app’s first launch
• Search query is not displayed on the Recent activity screen if the header was not collapsed after returning from request details
• The Open button for DNS providers opens the browser but not the website on Xiaomi TV Box
• The Can’t update license info snack is not displayed on the TV license screen after license check timeout
• Focus reset to default after pressing the Refresh status button on the License screen on TV
• The Certificate wasn’t installed dialog is shown after certificate installation via settings sharing
• Custom filter version is not updated after the filter update

DnsLibs (DNS filtering engine)

• Updated DnsLibs to v2.8.45

Improvements

• Added Post-Quantum cryptography support to DnsLibs
• Added an option to remove h3 from the alpn parameter of HTTPS RR
• Improved reliability of testing DoT upstream availability
• Improved DNS upstream list updates without reloading filters

Fixes

• DNS unblocking rule does not work
• At times system:// upstream replies failed to be accepted on Android
• Missing AdGuard certificate on some websites such as hitomi.la

CoreLibs (Filtering engine)

• Updated CoreLibs to v1.21.38

Improvements

• Added support for decoding URLs in $urltransform
• Enabled HTTP/3 filtering by default in beta/nightly builds
• Added support for example.org/path cosmetic rules
• Added support for the new $reason modifier
• Improved Do Not Track behavior
• Prevented local.adguard.org DNS leakage after enabling protection
• Enabled HTTP/3 filtering by default in stable builds

Fixes

• Incorrect certificate serial number marshalling leads to false positive CRLite matches
• There is no AdGuard certificate if the advanced option Check websites’ certificate transparency is enabled
• Connection resets on CoreLibs v1.19
• Localhost is unreachable in manual proxy mode in v1.19
• Incorrect destination address is shown in Request details when integration with AdGuard VPN is enabled
• Userscript import failure caused by BOM
• Broken injections when FakeDNS is used in proxy settings
• Broken handling of closing script tags with spaces
• Incorrect $generichide behavior for domain-scoped rules
• High latency in QUIC/HTTP/3 filtering causes protocol fallback to HTTP/2

Scriptlets (JavaScript enhancement for filtering rules)

• Updated Scriptlets to v2.2.16

Improvements

• Added new scriptlet — prevent-innerHTML
• Improved fingerprintjs2 — support window
• Added a parameter to increase duration of the trusted-click-element scriptlet’s execution duration

Original source