The arms race between ad blocking and anti-ad-blocking is older than most internet users. It’s also increasingly settled, in ways that matter for everyday browsing.

The 2026 picture is less dramatic than the discourse suggests. Most users still successfully block most ads. Most major sites still try and mostly fail to detect blocking. A few specific tactics have shifted the equilibrium. Here’s the practical situation.

What still works

Browser-based ad blocking with established extensions still works on the vast majority of websites. uBlock Origin remains the gold standard. AdGuard, Pi-hole at the network level, and various other tools also work effectively.

The blocking is largely transparent — most sites don’t notice. The minority that detect blocking and request you turn it off are the ones running anti-blocker scripts, and even those are usually bypassable with one of several methods.

What changed: Manifest v3

Chrome’s transition to Manifest v3 was supposed to be the end of effective ad blocking. It hasn’t quite been that. The transition limited some advanced filtering capabilities but didn’t eliminate them.

Several adaptations happened:

• uBlock Origin Lite was developed for Manifest v3 environments, with reduced but still effective capabilities
• Firefox maintained Manifest v2 support, becoming the preferred browser for users prioritizing ad blocking
• Brave browser continued with built-in blocking that doesn’t depend on extension architecture
• Network-level blocking (Pi-hole, NextDNS) became more popular as a Chrome workaround

The result is that Chrome users have less powerful blocking than before but still functional blocking. Users wanting maximum blocking effectiveness have moved to Firefox or use network-level approaches.

The site-side response

Sites trying to combat ad blockers have used several tactics:

Soft requests. Modal popups asking users to disable blocking. Mostly ignored, mostly closed. Rarely effective at conversion to seeing ads but probably not driving away meaningful traffic either.

Hard paywalls for blockers. Some sites block content entirely if blocking is detected. This works in the sense that the site enforces its preference, but it usually drives users to alternatives rather than to disabling blocking.

Server-side ad insertion. A few publishers have moved to inserting ads in the same HTML stream as content, making them harder to filter. The technical work is significant and only the largest publishers can do it economically. The result is some sites where blocking is genuinely harder.

Detection with consequences. Detecting blocking and degrading the experience (slower load times, missing features, fewer articles per session). More common but quietly executed.

Premium tiers. Most sustainable response — offering an ad-free experience for a subscription. The major news sites, YouTube, Spotify, and others have all moved this direction.

The premium-tier question

Many users now have at least one premium tier for an ad-supported service:

• YouTube Premium ($14.99 in Australia for individual)
• Spotify Premium for music streaming
• News subscription for one or two key publications
• Various others

The aggregate spending on these is significant — often $40-80/month combined. For some users this is excellent value. For others it’s the kind of accumulated subscription spend that adds up without delivering proportional benefit.

The question worth asking annually: which of these premium tiers do I actually use enough to justify the cost? Cancelling unused tiers often makes more sense than the optimization of “should I subscribe to one more service to escape ads on it?”

The mobile situation

Mobile ad blocking is harder than desktop blocking. The tools available are more limited, and the integration with browsing is more friction.

What mostly works on mobile in 2026:

• Firefox on Android with uBlock Origin extension
• Brave browser on iOS and Android (built-in blocking)
• Network-level blocking (configured DNS, VPN with blocking, Pi-hole on home network)
• Various adblocking VPN services (mixed results)

What mostly doesn’t work:

• Safari on iOS with extensions (limited capability)
• Chrome on Android with extensions (extensions not supported)
• Default browsers on most phones (no blocking)

The result is that mobile browsing typically has more ads than desktop browsing for users who block on desktop. This is a substantial percentage of overall internet usage where the blocking isn’t effective.

App-level advertising

Mobile app advertising is largely outside the blocking ecosystem. In-app ads run inside the app’s own infrastructure and aren’t visible to browser extensions.

Counter-measures for app ads:

• Choosing apps that don’t show ads (or pay for ad-free tiers)
• Network-level blocking that catches some app ads
• Avoiding apps that are heavily ad-supported in favor of paid alternatives
• Using web versions of services where possible

Many users have functionally given up on blocking app ads, accepting them as the cost of free apps. This is reasonable but it shifts a lot of advertising exposure to a context where blocking doesn’t help.

What the publisher economics look like

The publisher side of the ad blocking question often gets ignored. Many news sites and content businesses depend on ad revenue. When blocking reduces that revenue, sites have responded with:

• Paywalls (forcing payment for content)
• Reduced quality (less expensive editorial)
• Closure (some content sources have shut down)
• Subscription pivots (the financially healthier ones)
• Aggressive ads on the users not blocking (which makes blocking more attractive for everyone else)

There’s a real ethical question about how to support content sources while not being subjected to surveillance advertising. Many users have settled on a compromise: subscribe to a few specific outlets they value, block elsewhere.

The privacy dimension

Ad blocking is partly about user experience and partly about privacy. Many ads include extensive tracking infrastructure. Blocking ads usually blocks the tracking too.

The privacy benefit is real and probably more important than the user experience benefit for most users. The tracking infrastructure embedded in default web browsing is invasive enough that even users who don’t mind ads benefit from blocking.

Practical recommendations

For most users in 2026:

• Use Firefox or Brave with default ad blocking on all devices
• Add uBlock Origin to Firefox for additional control
• Consider network-level blocking at home (Pi-hole, NextDNS) for whole-house benefits
• Subscribe to ad-free tiers for the services you actually use heavily (probably 2-3 services maximum)
• Accept that mobile app ads will continue to mostly bypass blocking

For users who want more aggressive blocking:

• Network-level blocking handles most edge cases
• VPN services with built-in blocking handle mobile more effectively
• Privacy-focused operating system choices on mobile (GrapheneOS for Android, etc.) reduce baseline tracking

The arms race continues but the practical equilibrium is reasonable for users willing to make modest configuration choices. Default browser usage is more ad-saturated than necessary. Modest active engagement reduces the ad and tracking burden significantly.

This isn’t a permanent state. Browsers, sites, and ad networks will continue evolving. Users who pay attention will continue having effective blocking. Users who don’t will see more ads. That’s been the pattern for fifteen years and it continues.