Adguard Release Notes

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
.

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])

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
• Text clipping, header overlap, and content being covered by the keyboard in Rule editor
• The YouTube button in the AdGuard player restarts video
• On the Quick actions screen firewall notifications are displayed for both blocked and allowed apps when the Show blocked only filter is selected
• Scrolling User rules overlaps another view
• Scroll focus moves out of viewport during rapid scrolling of App management on TV
• Sharing from YouTube Music to AdGuard player doesn’t work
• AdGuard’s notification brings the device’s screen out of sleep mode
• Private browser does not open other apps from webpages
• Filter rule editor accepts any non-empty string as valid rule without syntax validation
• Dynamic theme does not apply to the AdGuard app after closing Private browser
• With Kazakh or Kyrgyz as system language, AdGuard erroneously displays it as Russian
• The number of blocked requests is displayed incorrectly in notifications in languages ​​that use hieroglyphs

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

We are presenting our latest release — AdGuard for Mac v2.19! This version offers an assortment of updates and reworkings, aimed in two main directions: security and usability.

We’ve implemented a new protection mechanism: AdGuard for Mac now uses cryptography to protect UserDefaults settings and userscripts. UserDefaults are encrypted with AES-GCM. Other types of data, including userscripts and filters, are protected by SHA256 checksums cryptography, with keys stored in the macOS Keychain. If a third-party app attempts to modify the configuration, AdGuard will detect it and alert you immediately.

Another security-focused feature is that AdGuard can now detect when a userscript compromises a website’s security. If that is the case, you will get a specific warning while trying to install it. This became possible after an important update to CoreLibs.

Concerning usability: we reworked the onboarding process for new users. We added new screens and details to create a smoother flow, making the app easier to understand and navigate.

We updated Scriptlets, DnsLibs, and UserscriptsWrapper as well, and fixed bugs for an overall better app performance.

This update improves filtering reliability, makes settings easier to share, and adds helpful popups to keep things clear and predictable.

Filtering: Faster, stronger, better

Custom filters in MV3 can now update independently from extension updates again, so ad blocking stays accurate and responds to changes more quickly.

We also fixed an issue where the extension would mistakenly accept HTML pages as filter lists when you added a custom filter by URL, causing the filter to fail silently. The extension now validates sources properly, preventing situations where a filter appears to be added but doesn’t actually work.

Beyond filter improvements, we’ve refined the Allowlist — the list of sites where blocking is disabled. Previously, if you added a full page URL (for example, copied straight from your browser’s address bar), the Allowlist might ignore it and keep blocking ads on that site. That’s no longer an issue — the extension now extracts the domain automatically, so your exclusions work as expected.

Settings import: Show, don’t tell

You can now generate a URL containing your full extension configuration. This makes it easy to set up AdGuard on a new device or after reinstalling your browser. Share the link with a friend, colleague, or support team, and they’ll see your exact setup instantly.

If you’re an active GitHub user, you can now import settings directly from Issues — especially useful for filter developers and those helping test fixes.

Interface: Better prompted than puzzled

We've added a few small improvements to prevent confusion and make the extension behave more predictably.

Warning for Opera users. Opera doesn’t grant extensions access to search engine pages by default, which prevents AdGuard from blocking ads in search results. The extension popup now displays a notice explaining that you need to allow access to search pages in your browser settings.

Confirmation for Invert Allowlist. The Invert Allowlist feature reverses how the extension works: blocking is disabled everywhere except sites on the list. To prevent accidental activation, we’ve added a confirmation dialog that explains what will happen when you enable it.

Changelog

Improvements

• Added beta suffix to the version in issue reports
• Implemented handling of speculative prerender requests
• Added confirmation modal for inverting allowlist
• Enabled independent updates of custom filters in MV3 without waiting for extension updates
• Added warning notification in Opera when Allow access to search page results permission is not granted
• Added support for importing settings via adguard:import_user_configuration links on reports.adguard.com
• HTTP Last-Modified header is now used as fallback when TimeUpdated metadata is missing
• Improved allowlist editor: now normalizes entries by extracting domains from URLs
• Updated issue report URL format to v4
• Cookie self-destruct stealth parameters are now MV2-only in issue reports (not supported on MV3)
• Added ROList support to Filters in MV3
• Added Share settings button to the main screen
• Updated @adguard/filters-downloader to v2.4.4
• Updated @adguard/dnr-rulesets to v4.2.1

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

AGTree (A tool for working with adblock filter lists)

• Updated @adguard/agtree to v4.1.1

TSUrlFilter (AdGuard Browser Extension filtering engine)

• Updated @adguard/tsurlfilter to v5.0.1

TSWebExtension (Library wrapper for Browser API and TSUrlFilter)

• Updated @adguard/tswebextension to v4.1.1

Scriptlets (JavaScript enhancement for filtering rules)

• Updated Scriptlets to v2.4.2