AdGuard: Where Its Blocking Layers Fit in a Real Setup
AdGuard sells a family of blocking products rather than one app: system-wide apps for desktop and mobile, a browser extension, a public DNS resolver, and self-hostable server software. This page reads the published product line plainly — which layer does what, and where each fits in the setup this site recommends elsewhere.
Who AdGuard fits
- Users who want blocking beyond the browser — the system-wide apps filter traffic from native apps and background services, the gap browser extensions cannot cover.
- Households that want one filter everywhere — the DNS product (public resolvers and a paid personal DNS tier) applies to every device pointing at it, including TVs and consoles that install nothing.
- Technical users who want self-hosting — the open-source server product (AdGuard Home) runs the same DNS-level filtering on your own hardware, with no subscription.
What the product line includes
The published structure separates clearly: the consumer apps (paid, one-time or subscription depending on platform) do DNS filtering plus HTTPS-level content blocking inside the browser they integrate with; the browser extension is free and does content blocking only; the public DNS resolvers are free with optional ad-blocking variants; AdGuard Home is free and open-source.
That spread is unusual — most vendors sell one layer. It also means the honest comparison is layer-by-layer: the paid app competes with paid system-wide blockers; the free extension competes with other content blockers; AdGuard Home competes with other self-hosted resolvers.
What stands out
- Full spectrum from free to self-hosted. The free extension and free resolvers let you evaluate the filter lists before any payment — a low-friction entry most paid blockers lack.
- HTTPS-level filtering in the desktop apps. The system apps can filter inside encrypted traffic via local certificate handling, which is the technical mechanism behind their finer granularity — and a trust decision worth reading about in their documentation before enabling.
- Filter-list transparency. Lists, update cadence, and statistics are published and inspectable.
What to watch for
- Certificate trust. HTTPS filtering requires installing the vendor's local root certificate — a genuine trust step the documentation explains. If you are not comfortable with it, use the DNS-layer products, which do not need it.
- Over-blocking is the DNS layer's failure mode. Aggressive lists break logins and apps; start with mainstream lists and tighten only with cause.
- Platform pricing varies. One-time licenses on desktop, subscriptions on mobile tiers — price the exact combination of devices you actually run. [VERIFY current prices on the official site.]
Bottom line
AdGuard's unusual breadth is its actual advantage: one vendor covers the browser layer for free, the system layer for payment, and the household layer for free forever if you self-host. Start with the free products, judge the filter lists in your own daily use, and pay only for the layer you keep.
Check AdGuard's current products →
This assessment is based on AdGuard's published product pages and documentation, current at the date above. Pricing and feature line-ups move often — confirm on the official site before you buy. The link above is a plain link to the vendor's official site; it does not change the assessment on this page.