Open-source project
TG-Twilight/AWAvenue-Ads-Rule avatar
TG-Twilight/AWAvenue-Ads-Rule

AWAvenue Ads Rule: a network-layer list split into four subscriptions

An upstream source for many excellent ad-blocking rules, and one of the best ad filters in the open-source community. Compatible with AdGuard/Home/DNS, AdAway, hosts, Mosdns, ClashMeta, QuantumultX and other mainstream ad-blocking/proxy tools.

6,824 stars177 forksAdblock Filter ListGPL-3.0

At a glance

What is it?
AWAvenue Ads Rule is a GPL-3.0 filter list that blocks advertising SDK traffic at the network layer and ships four subscriptions covering ads, privacy and unwelcome traffic. It works well on routers and DNS resolvers, and it explicitly does not work with accessibility click tools.
Who is it for?
Adopt it when your blocking happens at DNS, hosts or proxy level, on a router, an OpenWrt box or an AdGuard resolver, and pick the subscription that matches which app features you are willing to lose. Skip it if you depend on an accessibility click tool or the AdGuard browser extension, since neither path is supported.
Can I use it commercially?
Yes, with conditions. GPL-3.0 is a copyleft licence: if you distribute software that includes it, you must release that software's source code under the same licence. Running it internally without distributing it does not trigger that obligation.
Is it still maintained?
Yes. The repository last received commits 1 day ago.
What is it written in?
Mainly Adblock Filter List, according to GitHub's language statistics.

Answers come from the project's GitHub data, last synced on November 15, 2026, and from our analysis. They are not legal advice.

From daily snapshots

Star history

  • TG-Twilight/AWAvenue-Ads-Rule6,824 ★ · +298
Star history
Repository2026-09-232026-11-15
TG-Twilight/AWAvenue-Ads-Rule6.5k6.8k

298 Stars in the last 53 days, measured from the daily GitHub snapshot. Compare with other projects

Editorial analysis

The list stops SDK traffic at the network layer, so accessibility clickers are out of scope

The mechanism is network-layer interception. The rules block the traffic between an app's advertising SDKs and the servers they call, so the ad payload never arrives. That single design choice explains both what the list does well and where it stops working. It is a different approach from accessibility services that simulate taps on an ad view, and the project states plainly that this kind of tool is not supported and cannot import these rules. Nothing in the repository changes that: the top level holds AWAvenue-Ads-Rule.txt, Filters/, assets/, LICENSE, README.md, .gitattributes and .github/, all of them text and documentation, nothing that hooks into an app or clicks anything. Any ad that renders without a network request, or that pulls from a domain the list does not carry, stays on screen. After subscribing, the project asks for a report if ads still appear or if something legitimate gets blocked.

Since 1.7.6-release the rules split into ads, privacy and unwelcome, and that is what drives the four plans

The four subscriptions are not four quality tiers. They are four trade-offs against specific app features, and the split exists because of what each category costs you. Full protection bundles ads, privacy and unwelcome rules into the default experience. The ads-only variant drops both other categories and is the one to pick when compatibility and minimum intervention come first. A third plan keeps ads and unwelcome rules but leaves privacy out, for readers who want statistics and telemetry to keep flowing. The fourth keeps ads and privacy but leaves unwelcome rules out, for readers who want forced updates, push delivery and related connections to keep working. The unwelcome category is defined in the project as forced updates, P2P and PCDN distribution, push, and cloud-controlled delivery. Blocking those does not reduce ad filtering, which is exactly why they were split off instead of folded into the default.

Four mirrors of the same raw file, so one unreachable CDN is not the end of it

The default plan is published at the same path on the main branch and served through four different routes, which is the cheapest insurance a subscription list can offer. If one host is slow or blocked from your network, the other three return identical content:

text
https://raw.githubusercontent.com/TG-Twilight/AWAvenue-Ads-Rule/main/AWAvenue-Ads-Rule.txt
https://github.boki.moe/https://raw.githubusercontent.com/TG-Twilight/AWAvenue-Ads-Rule/main/AWAvenue-Ads-Rule.txt
https://gcore.jsdelivr.net/gh/TG-Twilight/AWAvenue-Ads-Rule@main/AWAvenue-Ads-Rule.txt
https://ghfast.top/https://raw.githubusercontent.com/TG-Twilight/AWAvenue-Ads-Rule/main/AWAvenue-Ads-Rule.txt

All four point at AWAvenue-Ads-Rule.txt, which is the full protection file. The other three plans live under Filters/ and are addressed by their own paths, so swapping plans means replacing the URL rather than editing a list inside your client. The three narrower plans are published at paths such as Filters/AWAvenue-Ads-Rule-Adguard-Only.Ads.txt for the ads-only variant, with matching files carrying a No.Privacy or No.Unwelcome suffix for the two partial plans. Pinning the URL matters for another reason: clients cache a subscribed list on a schedule, so a plan change that only edits content in place is harder to notice than one that changes what you subscribe to.

Filters/ encodes tool and variant in the filename, which is why the site offers a generator

The project publishes an explicit naming rule for the Filters/ directory: AWAvenue-Ads-Rule-<tool>-<variant>.<suffix>. That convention is what makes the same rules reachable from Adblock syntax, hosts files, Clash rules, Quantumult X lists and Mosdns configurations without maintaining separate repositories. The subscription table in the project documentation only spells out the AdGuard variants, and the project says so, then points readers at the subscription generator on the official site instead of asking anyone to memorise filenames. That is the sane call once you count the cross product of tools and variants. It does mean the repository listing alone is not a usable index for a new user, and that the canonical list of current URLs lives on a site outside the repository.

RouterOS entries in 240.0.0.1 and 0.0.0.0 form, plus one explicit browser exception

The supported surface is grouped by syntax rather than by vendor. Adblock syntax covers AdGuard on iOS, Android, Home and DNS, and the project states it does not include the AdGuard browser extension for Chrome. Hosts syntax covers AdAway and other hosts-based blockers such as 大圣净化. The OpenWrt group covers Mosdns, plus Dnsmasq in .conf form and other DNS-level blockers. Proxy clients include Clash Meta, Quantumult X, Shadowrocket, Surge and Surfboard. Routing systems are supported too, with RouterOS handling both 240.0.0.1 and 0.0.0.0 style addresses. The project calls AdGuard Home on a router the more ideal filtering position and notes the rules are already in the official AdGuard list, so subscribing from the client's own list is possible without pasting a URL.

Size control is the trade the project advertises, and it is what keeps routers comfortable

The project's own comparison is against lists that run to many thousands of rules, and it claims four properties instead: controllable size for faster loading, a hit rate tuned for common ad SDKs, enough efficiency for routers and low-end devices, and one subscription serving every device. The README does not print a rule count or a file size, so those two numbers are not checkable from the repository alone, and the hardware friendliness claim is the one to test first on an actual router. The effects the project expects you to notice are the shake-to-open ads disappearing, in-feed and end-of-article ad slots failing to load, autoplaying ad video ending, TV box and smart TV boot ads going away, and a little reclaimed space on a phone because the ad assets never download. The argument for the network layer over per-app configuration is cost and reach: one subscription on a router covers devices you cannot configure individually. The project also states that as of September 2026 the list can block more than ninety percent of existing ad SDK content "in Teyvat", which is its own claim rather than an audited figure.

Hosts format drops the syntax features that only Adblock clients understand

The same rule set has to survive being reduced to a hosts file, and that is where a lot of generic filter lists stop being useful. A hosts variant can only express domain to address mappings, and the project serves hosts targets such as AdAway and 大圣净化 with their own hosts-format files. The Mosdns route adds a third constraint, because it wants its own format. Dnsmasq is listed separately again in .conf form. That is four serialisations of the same policy, and it explains why the project recommends generating the right URL per tool instead of picking one file and hoping a client copes.

Casual maintenance, three recent releases, and a feedback loop that starts with the FAQ

The project describes itself as a personal project maintained on a free spirit basis, and the release feed matches that: 1.6.9-release on 2025-11-13, 1.7.6-release on 2026-07-26 and 1.7.8-release on 2026-09-21, with the last push on 2026-10-26. About eight months separate the first and second of those, the third came about two months after the second, and the repository is not archived, so the cadence is uneven rather than dormant. Licence is GPL-3.0. The support path is deliberately narrow: the documentation asks that you read the FAQ page before submitting an issue or asking in the chat group, on the grounds that many questions are already answered there, and issues and pull requests are both welcome. The feedback it asks for runs in both directions, ads that still get through and false positives that should not have been blocked, which is the only way a list this size stays honest about its own coverage. Whether that loop keeps up depends on how quickly a newly observed domain reaches the right category and the right tool variant, and the repository sets no service level for it.

Editorial conclusion

Adopt it when your blocking happens at DNS, hosts or proxy level, on a router, an OpenWrt box or an AdGuard resolver, and pick the subscription that matches which app features you are willing to lose. Skip it if you depend on an accessibility click tool or the AdGuard browser extension, since neither path is supported. Before switching, subscribe to one variant, watch for a week of false positives, and read the FAQ page the project links before opening an issue.

Frequently asked questions

Can I block ads using DNS on my router with AWAvenue Ads Rule?

The project treats this as the preferred setup. It points to AdGuard Home running on a router as a more ideal filtering position, and notes the rules are already in the official AdGuard list so they can be subscribed from within the client without pasting a URL.

Which AWAvenue Ads Rule subscription should I pick?

Full protection bundles ads, privacy and unwelcome rules. The ads-only variant is for minimum intervention, ads plus unwelcome keeps statistics and telemetry flowing, and ads plus privacy keeps forced updates, push and related connections working.

Does AWAvenue Ads Rule work with accessibility click tools?

No. The project states that accessibility click tools use a completely different principle and are not supported, and that its rules cannot be imported into them. Its own filtering happens at the network layer.

Which tools can consume the AWAvenue Ads Rule filters?

Adblock syntax tools including AdGuard on iOS, Android, Home and DNS but not the Chrome extension, hosts based blockers such as AdAway, OpenWrt tools including Mosdns and Dnsmasq, proxy clients including Clash Meta, Quantumult X, Shadowrocket, Surge and Surfboard, and RouterOS routing systems.

How often is the AWAvenue Ads Rule list updated?

The release feed shows 1.6.9-release on 2025-11-13, 1.7.6-release on 2026-07-26 and 1.7.8-release on 2026-09-21. The repository is not archived and the last push was on 2026-10-26, and the project calls itself a personal project maintained casually.

Official sources

  1. License: GPL-3.0
  2. Project website
  3. README
  4. Releases
  5. TG-Twilight/AWAvenue-Ads-Rule on GitHub
Add this badge to your README

If you maintain this project, the badge below links readers to this analysis and shows its maintenance status from the daily GitHub snapshot. Paste the markdown into your README; add ?metric=license or ?metric=stars to the image URL for a different field.

Add this badge to your README

markdown
[![Hysen Labs](https://hysenlabs.com/badge/tg-twilight-awavenue-ads-rule.svg)](https://hysenlabs.com/projects/tg-twilight-awavenue-ads-rule)

Star history chart for your README

markdown
[![Star history](https://hysenlabs.com/chart/tg-twilight-awavenue-ads-rule.svg)](https://hysenlabs.com/projects/tg-twilight-awavenue-ads-rule)

Was this useful?