How to Block Ads and Popups on Any Device or Browser

Online ads have evolved from simple banners into an aggressive ecosystem of autoplay videos, interstitial overlays, tracking scripts, and popups that hijack your attention — and sometimes your browser. Blocking them isn't just about comfort. It's also about page load speed, data usage, privacy, and occasionally security, since malicious ads (malvertising) can execute code without a click.

Here's how ad and popup blocking actually works, what your options are, and why the right approach varies significantly from one setup to the next.

How Ad Blocking Works

Ad blockers operate by intercepting network requests before they load. When your browser tries to fetch a resource, the blocker checks it against a filter list — a regularly updated database of known ad servers, tracking domains, and script patterns. If there's a match, the request is blocked before it renders.

Some blockers work at the browser extension level, some at the DNS level, and others at the operating system or network level. Each layer has different capabilities and tradeoffs.

Browser-Level Blocking: Extensions and Built-In Tools

The most common method is a browser extension. These run inside your browser and can read page content, intercept requests, and hide elements using CSS rules. Most support multiple filter lists, including EasyList (general ads), EasyPrivacy (trackers), and regional lists for non-English sites.

Key things to understand about browser extensions:

• They only protect traffic through that specific browser
• They can be bypassed by sites that detect extension presence
• Some extension stores have seen fake or compromised ad blockers — always check install counts and reviews
• Manifest V3, Chrome's newer extension framework, limits how extensions interact with network requests, which affects how some ad blockers function in Chromium-based browsers

Many browsers now include built-in popup and ad blocking to varying degrees:

Brave uses a native blocker that doesn't rely on the extension framework at all, which gives it more flexibility — but it also means your control over filter lists and exceptions works differently than it would in an extension.

DNS-Level Blocking: Network-Wide Coverage 🔒

A DNS-based blocker works by replacing your DNS resolver with one that refuses to resolve known ad and tracker domains. Instead of the request reaching the ad server, it simply fails to connect.

The major benefit: it covers every device on your network, including smart TVs, game consoles, and mobile apps — none of which support browser extensions. This includes in-app ads that extensions can't touch.

The limitations: DNS blockers can't see inside encrypted HTTPS traffic, can't remove cosmetic ad placeholders left behind on pages, and can't block ads that are served from the same domain as the content (common with YouTube and some streaming platforms).

DNS blocking can be set up at the router level, on individual devices, or through a cloud-based service. Technical skill required ranges from minimal (change DNS settings on your phone) to moderate (configure a self-hosted instance on a home server or Raspberry Pi).

System-Level and App-Level Options on Mobile

Mobile is its own challenge. iOS doesn't allow traditional browser extensions in the same way, but it does support content blockers — lightweight apps that provide filter lists to Safari. These work well within Safari but don't affect other apps.

On Android, some browsers with built-in blocking are available. There are also VPN-based blocking apps that route all device traffic through a local VPN and filter it — effectively giving you system-wide blocking without changing your DNS settings manually.

Both platforms have tradeoffs: content blockers on iOS are Safari-only, and VPN-based blockers on Android may conflict with work VPNs or increase battery usage slightly.

What Determines How Well Blocking Works

Not all setups block the same things. Several variables affect your real-world results:

• Filter list quality and update frequency — stale lists miss new ad domains
• Browser and extension compatibility — especially relevant given Manifest V3 changes in Chrome
• Site-specific counter-measures — some publishers detect ad blockers and withhold content
• Ad delivery method — ads served from a site's own domain (first-party) are very difficult to block without breaking the page
• Device type — desktops have the most options; smart TVs and IoT devices have the fewest
• Network configuration — DNS-level blocking requires router or device access you may not always have (hotel Wi-Fi, mobile data)

Popups Specifically: A Different Problem Than Ads

Popup blocking is handled somewhat differently from ad blocking. Most browsers block unsolicited new window popups by default now. What users usually encounter today are overlay popups within the page itself — newsletter prompts, cookie consent walls, chat widgets, exit-intent modals.

These can't be blocked at the DNS level because they're part of the page's own code. They require element-hiding rules in a browser extension, or manual rule creation if a site uses unusual markup. Some filter lists include cosmetic rules specifically for these patterns, but coverage is inconsistent.

The Variables That Make This Personal

What works well depends heavily on:

• Whether you need cross-device or single-browser coverage
• How comfortable you are adjusting DNS settings or managing a local server
• Whether mobile app ads are a priority
• How you use your browser (extensions, sync services, work vs. personal)
• What your threat model looks like — privacy-focused users often want tracker blocking as much as ad blocking

A casual desktop user and a privacy-conscious person running a home network with multiple devices will end up with meaningfully different setups — even if both just want fewer ads. The right combination of tools depends entirely on where your traffic flows and what you actually need to protect.