How Phoenix Ad Blocker Works

A detailed look at how Phoenix Ad Blocker (built by Better Web For All) blocks ads, protects privacy, and operates without conflicts of interest.

How Phoenix Ad Blocker Blocks Ads

Phoenix Ad Blocker uses content filtering to identify and block ads, trackers, and analytics scripts before they load in your browser. The process works like this:

  1. You visit a website - Your browser begins requesting the page and its resources
  2. Phoenix intercepts network requests - Before ads and trackers load, Phoenix checks each request against filter lists
  3. Matching requests are blocked - Requests that match known ad or tracking patterns never reach your browser
  4. The page loads without ads - You see clean content, faster load times, and reduced bandwidth usage

Phoenix Ad Blocker uses community-maintained filter lists like EasyList and EasyPrivacy. These lists are continuously updated by contributors worldwide who identify new ad serving domains, tracking scripts, and analytics patterns. The lists contain thousands of rules refined over years of use across millions of browsers.

Why this matters for performance: Ads aren't just visual annoyances. Modern ad systems load JavaScript tracking libraries, download images and videos, make dozens of network requests to ad exchanges, and run analytics that monitor your behavior. By blocking these requests before they execute, Phoenix Ad Blocker makes pages load significantly faster (target: 25 to 30% improvement) while using less bandwidth and battery on mobile devices.

Privacy by Architecture

Phoenix Ad Blocker is designed so Better Web For All cannot access your browsing data. This isn't a policy promise. It's how the system is built.

Local Processing Only

All ad filtering and tracker blocking happens entirely on your device. Phoenix Ad Blocker processes filter list rules locally. Your browsing history, the sites you visit, and what you do on those sites never leave your computer.

No Analytics Infrastructure

Better Web For All doesn't run servers that collect usage data, browsing patterns, or analytics. There's no backend database storing user information. No logs of what sites get blocked. The infrastructure to collect this data doesn't exist.

Open Source Code

When Phoenix Ad Blocker launches, the source code will be publicly available. Security researchers, developers, and technically-minded users can audit exactly what Phoenix Ad Blocker does. You can verify our claims by reading the code yourself or trusting independent audits.

Privacy policies can change. Companies can be acquired. Business models can shift. That's why Phoenix Ad Blocker is built around privacy by architecture rather than privacy by policy. The way the system works makes data collection technically infeasible, not just against our stated principles. Better Web For All can't change this without rebuilding Phoenix Ad Blocker from scratch, which would be immediately obvious in the open-source code.

What We Do (and Don't Do)

Phoenix WILL DO Phoenix WILL NOT DO
✓ Block 100% of ads ✗ Allowlist "acceptable" ads
✓ Run locally on your device ✗ Send data to servers
✓ Accept donations ✗ Sell your browsing data
✓ Publish open-source code ✗ Hide behind proprietary code
✓ Block trackers and analytics ✗ Make deals with advertisers
✓ Stay free forever ✗ Paywall core features

How Better Web For All Sustains Phoenix Ad Blocker

When Phoenix Ad Blocker launches, we'll accept donations to support development and infrastructure. Phoenix Ad Blocker will always be free for everyone. Donations simply help Better Web For All build faster, support more browsers, and maintain the extension long-term.

Better Web For All operates on optional donations from users, with no revenue from advertisers.

This model eliminates conflicts of interest that emerge when ad blockers need recurring revenue. If your business depends on charging advertisers for exceptions or selling user data, you're balancing two interests that don't align. Better Web For All's donation model means we only answer to users.

  • No investors pushing for growth metrics or exit strategies
  • No corporate owners with different priorities
  • No acceptable ads programs where advertisers pay for allowlisting
  • No data collection or selling user information
  • No premium tiers or paywalled features

The donation model at scale: Wikipedia raises over $185 million annually from voluntary donations. Signal supports millions of users on donations alone. Mozilla sustains Firefox development. These organizations prove that donation models work when users trust the mission and see transparent financial reporting.

Our goal isn't to build a billion-dollar company. It's to support a small team of 7 to 10 contributors building excellent ad blocking software that never compromises user interests. That's achievable with a donation model and aligned user base.

Technical Details

Browser Support

Phoenix launches on Chrome first, which has approximately 65% of the browser market. This approach lets us reach the majority of users quickly while gathering feedback to improve the extension. Edge support will follow shortly after Chrome launch, as Edge uses the same Chromium foundation. We're building Phoenix with a browser-agnostic architecture that makes porting to new browsers more straightforward as we grow.

Manifest V3 Compatibility

Phoenix is designed from the ground up to work within Chrome's Manifest V3 extension architecture. Manifest V3 introduced significant changes to how extensions can block content, with new limitations on the declarativeNetRequest API and removal of the older webRequest blocking capabilities. Building Phoenix specifically for V3 rather than adapting an older extension gives us more flexibility to optimize within these constraints while maintaining effective ad blocking.

Filter Lists

Phoenix uses community-maintained filter lists including EasyList (general ad blocking), EasyPrivacy (tracking protection), and additional regional lists as needed. These lists have been refined over more than a decade by contributors who identify new tracking methods and ad serving patterns. Users who want more control can add custom filter rules to block specific elements or domains. The filter lists update automatically to catch new ads and trackers as they emerge.

Performance Targets

Our goal is 25 to 30% faster page load times compared to browsing without an ad blocker. This comes from preventing ads, analytics, and tracking scripts from loading entirely. We're also optimizing Phoenix for minimal memory usage so it runs efficiently on devices with limited resources. Ad blocking shouldn't slow down your browser. It should speed it up by eliminating unnecessary network requests and JavaScript execution.

Questions About Phoenix Ad Blocker?

Visit our FAQ page for more detailed answers about Phoenix Ad Blocker's structure, privacy approach, and business model. You can also read Better Web For All's full story to understand why we're building Phoenix Ad Blocker this way.