Adguard Release Notes

April 3, 2025

We’ve added a major feature in AdGuard v4.9 for Android: native support for userstyles. This feature has been available in AdGuard for Windows and AdGuard for Mac for a while, and now we are bringing it to AdGuard for Android!

Userstyles are similar to userscripts in a way, but they only focus on changing the appearance of websites using CSS, without getting into their code. Now customizing websites — like adding a dark theme — becomes an easy task. You can create your own userstyles in the app itself, or install ready-made styles from trusted online sources.

To add a userstyle, go to Settings → Filtering → Extensions→ Add extension → Import from file or URL. To create your own style, tap Add extension → Create userstyle.

Also, some users might have recently faced a bug that was increasing statistics to ridiculously huge values. We fixed the issue, and once you install AdGuard v4.9 for Android, you will see normal numbers in the Statistics tab.

Please note that statistics accumulated earlier than the last 24 hours will be heavily pruned.

Aside from this serious issue, we have also worked on fixing smaller bugs. As always, we’ve updated CoreLibs and Scriptlets for better functionality of the app.

Changelog

Improvements …

March 5, 2025

With this release, we're bringing our MV2 and MV3 extensions on the same page. We’re upgrading the MV2 extension to version 5.1, and from this point on, both extensions will be in perfect sync, with their versions updated at the same time.

What’s in it for you? First off, you’ll notice a visual upgrade: the MV2 extension now features the MV3 design. But that’s not all — from now on, bug fixes and features will be implemented more efficiently in both extensions.

We’ve also made some other minor improvements and bug fixes, which you can explore in the full changelog below. One of them deserves to be highlighted: internal optimizations will give the extension the possibility to take part in the Fast Track Review process in the Chrome Web Store. This means that in the future, if our approach works, we will be able to release extension updates with new filters more often, without having to wait for a review according to Chrome Policy. You will get extension updates in your hands – or rather, in your browser – faster than ever!

February 28, 2025

This hotfix, as well as the release before it, focuses on filters. Many users have reported a big issue: filters and extensions were gone after updating from the previous version. Rest assured, they are not gone permanently — we always create backups. If you’ve been affected by this issue, please follow the steps below to restore your settings:

Open File Explorer and navigate to the path “%programdata%/adguard/backups”.

Find the backup zip file associated with the 7.19 version. It will be named something like adguard_settings_7.19.... Save this file somewhere.

Uninstall AdGuard, but make sure to keep your settings (don’t check the box Delete settings).

Go back to File Explorer and navigate to “%programdata%/adguard”. Delete the FLM folder and the adguard.db file.

From the zip file you saved in step 2, extract the adguard.db file and copy it to the “%programdata%/adguard” folder.

Finally, install version 7.20.1. Your settings should be restored.

February 26, 2025

Unfortunately, the build with the returned Quick fixes filter failed to pass the Chrome Web Store review and we had to remove not only this filter, but also the entire Custom filters group. We're very unhappy about this, but it's a forced measure.

Stay tuned to our blog for our reflections on this matter and a full timeline of events, as well as how the userScripts API and fast-track review can potentially help us.

February 17, 2025

We continue to unify the code base of our products, and AdGuard for Android is no exception. Updates will now be more stable and new features will be added faster. Also, in the new version we have accelerated the loading of large amounts of data in Statistics, as well as updated CoreLibs and DnsLibs.

From this version, AdGuard for Android only supports Android 9 or higher.

Changelog

Fixes

Beeline Wi-Fi calls do not work #5583

The CPU background value increases drastically after a few series of quitting/starting the app #5504

Custom DNS does not work after importing settings #5618

CoreLibs (Filtering engine)

CoreLibs updated to v1.17.88 #5620

DnsLibs (DNS filtering engine)

DnsLibs updated to v2.5.63 #5607

Improvements

Added matter._tcp.default.service.arpa to the list of default exclusions #230

Block RFC9462 (_dns.resolver.arpa) queries #228

Use pretty_str() in errors reported in DnsRequestProcessedEvent #223

Fixes …

December 30, 2024

This update is just a chill guy that makes the app up to 30x faster. We did some work on Safari Converter, so now AdGuard filtering rules are converted to Safari rules in just 0.5–2 seconds instead of 10–30. You will notice the difference especially when updating, enabling, or disabling filters and turning protection on.

Let's give a bit of explanation.

Updating and/or applying filters involves three steps: downloading new versions to the AdGuard app (a seamless process), converting AdGuard rules into Safari-compatible rules (now 30x faster thanks to optimization), and loading the rules into Safari. In the case of the last step, however, on iOS and iPadOS, the process takes 6–15 seconds per small content blocker to compile rules compared to fractions of a second on macOS. This delay affects user experience and slows filter updates, which are critical for ad blockers' performance. AdGuard has reported the issue to Apple (ticket ID: FB16130983) and hopes for a fix in 2025. You can read the blog post for more details.

December 30, 2024

This update is just a chill guy that makes the app up to 30x faster. We did some work on Safari Converter, so now AdGuard filtering rules are converted to Safari rules in just 0.5–2 seconds instead of 10–30. You will notice the difference especially when updating, enabling, or disabling filters and turning protection on.

Let's give a bit of explanation.

Updating and/or applying filters involves three steps: downloading new versions to the AdGuard app (a seamless process), converting AdGuard rules into Safari-compatible rules (now 30x faster thanks to optimization), and loading the rules into Safari. In the case of the last step, however, on iOS and iPadOS, the process takes 6–15 seconds per small content blocker to compile rules compared to fractions of a second on macOS. This delay affects user experience and slows filter updates, which are critical for ad blockers' performance. AdGuard has reported the issue to Apple (ticket ID: FB16130983) and hopes for a fix in 2025. You can read the blog post for more details.