The Ad Blocker War: YouTube's Escalation and the Weapon They've Been Quietly Building
I've now written two posts about YouTube systematically degrading its free experience — background playback killed in browsers, lyrics paywalled after six years of being free. Each time I've said: this is a pattern, not a coincidence. This is deliberate, not incidental.
So let's talk about what else has been going on, and more importantly, about the weapon YouTube has been quietly building that makes the cat-and-mouse game a lot less equal.
The Ad Blocker Squeeze
While I was writing about background playback and lyrics, YouTube has been running a parallel campaign against ad blockers that's been steadily escalating.
The timeline: They started with pop-up warnings back in 2023 — "ad blockers violate YouTube's Terms of Service," that kind of thing. Extension developers pushed filter updates, users moved on. Standard cat-and-mouse.
Then in June 2025 it shifted gear. YouTube closed multiple loopholes simultaneously and rolled out something nastier: intentional video loading delays for users who still had working blockers. Not "you can't watch this." More like "enjoy watching this buffer for exactly as long as a pre-roll ad would have run." They served a pop-up alongside the spinning wheel that basically explained this explicitly. They also started targeting accounts previously flagged for ad-blocking behavior, which bypasses the detection methods extension developers normally work around.
By November 2025, widespread reports of YouTube just refusing to load entirely for some users — blank homepages, videos that spin forever. Reddit was convinced it was a global outage. It wasn't.
And then in late January 2026: fake error messages. "This content isn't available, try again later." It is available. It's just not available for you, with your blocker, on your terms. Some users found that hitting "Learn More" then pressing back could temporarily restore playback. Others reported spamming refresh until it gave up. Not exactly the experience you'd expect from one of the ten most-visited websites on the planet — unless, of course, they're doing it on purpose.
They are doing it on purpose.
The Cat-and-Mouse Game Has Always Favored Users. Until Now.
In my first post, I said that someone would eventually find a way around the background playback enforcement. I stand by that — the cat-and-mouse framing still holds for most of what I described above. Extension developers update filters, YouTube detects the approach, repeat. It's an arms race, and arms races don't have permanent winners.
But there's one development buried in all of this that breaks that pattern, and it deserves its own spotlight.
Starting around March 2025, YouTube began experimenting with server-side ad insertion (SSAI). Here's why that matters.
The way traditional ads work on YouTube, the ad is a separate request your browser makes. Your browser asks YouTube's servers for the video, and it separately fetches the ad from an ad server. That separation is what makes blocking possible — an extension can intercept the ad request before it ever plays, because it's a distinct transaction.
SSAI eliminates that distinction. Instead of your browser fetching the ad separately, YouTube stitches the ad directly into the video stream on their servers before it ever reaches your device. By the time the video arrives at your browser, the ad is already part of it. From your browser's perspective, it's one continuous stream of video. There's nothing to intercept, nothing to block, no separate request to identify and drop.
That's not a cat-and-mouse game. That's removing the mouse from the equation entirely.
It's not fully deployed — most ads are still served the old way and still blockable. But the direction is clear, and the investment they're making in this technology tells you exactly where they're headed.
Sound Familiar? It Should.
Here's where your experience on Meta's platforms probably made you nod along.
The reason Facebook and Instagram feed ads are such a nightmare to block compared to, say, a banner ad on a news site is essentially the same principle. Meta uses its Conversions API — server-side tracking that bypasses your browser entirely — and their in-feed ads are deeply integrated into the same content delivery system that serves your actual posts. Blocking them without breaking the feed is genuinely difficult because they're not cleanly separate. The ad and the organic post look like the same type of thing to your browser, served through the same pipes.
YouTube is building toward the same architecture for video. And once they get there, the browser-based blocker is essentially obsolete against it.
The difference is that Meta's approach grew out of tracking and attribution — they wanted advertisers' conversion data to survive iOS privacy changes and browser restrictions. YouTube's SSAI is more direct: they want the ad to play, period. But the underlying logic is the same — take the thing you're trying to block and bake it into the infrastructure so deeply that the blocking tool can't distinguish it from legitimate content.
What This Is Really About
I keep coming back to this because it keeps being true: this isn't just about ad revenue, and it's not just about Premium subscriptions.
When you're running an ad blocker on a browser, you're not just blocking ad revenue. You're also blocking telemetry, tracker requests, and the data collection that's baked into YouTube's ad delivery stack. You're using their platform without giving them the full picture of you that their business model depends on.
The ideal outcome from Google's perspective has never been you subscribing to Premium — Premium is second prize. The ideal outcome is you in their app, signed in, watching ads, with full device-level telemetry flowing back to them unimpeded. The browser with a blocker is the scenario they're designing against, not just for revenue reasons but for data reasons.
SSAI serves both goals simultaneously. When the ad is baked into the stream, you can't block it. When you can't block it, you're watching it. When you're watching it, they're collecting data on you. One move, two problems solved.
The Honest State of Your Options
There's no single magic bullet here, but layering helps. My own setup illustrates the point: at home and anywhere on my Tailscale network (see the homeserver series), AdGuard Home handles network-level filtering before requests even reach the browser. On desktop I run Vivaldi with uBlock Origin Lite on top of that. On iOS, Orion handles it with a combination of AdGuard and uBlock lists baked in — notable because Orion is WebKit-based but supports extensions natively, which is genuinely unusual on iOS and sidesteps a whole category of problems. It's redundant by design. No single layer catches everything, but together they cover more ground.
The honest caveat: network-level blocking is great for tracker requests and a lot of ad infrastructure, but it won't touch SSAI at all by design. You can't filter what arrives pre-baked into the video stream from YouTube's servers — by the time it reaches your network, the ad is already part of the video. That's the wall this approach eventually hits.
Chromium-based browsers are the most MV3-exposed, which limits what extensions like uBlock can do in them — Chrome worst of all, but any Chromium fork carries some of that baggage. Firefox and hardened forks like Librewolf have more headroom there. VPN-based blockers are harder for YouTube to fingerprint than browser extensions but aren't free and face the same SSAI problem at the network level.
YouTube Premium at $13.99/month buys you out of the whole fight. I understand why people pay it. I also understand why people find it insulting, given what YouTube used to be.
My Take
I've now written three posts about YouTube making things worse for users who aren't paying. Background playback. Lyrics. The ongoing ad blocker war with SSAI on the horizon.
Each individual move gets covered as its own story. But step back and look at what's being built: every door that let you use YouTube on your own terms is being closed, one at a time, methodically. And the latest technical development — server-side ad insertion — isn't just another round of the same fight. It's a structural shift that makes one of the last effective tools average users have substantially less useful.
I still use YouTube. I can't not — nothing else has the content. That monopoly is the whole reason they can keep doing this. Creators can't easily move. Users can't easily follow. The network effects are too strong, and Google knows it.
That's the part I find hardest to accept: there's no consumer action that changes this. You can vote with your wallet and subscribe. You can vote with your feet and... go where, exactly? There's no "where." The content is there. The audience is there. The alternative is just absence.
So I'll keep writing about it, because the least we can do is be clear-eyed about what's happening and why.
A Note on the "Just Use NewPipe" Crowd
After Part 2 went out, a few people on social suggested NewPipe as the obvious solution to all of this. And look — it's not a bad app. If you're on Android, comfortable sideloading outside the Play Store, and okay with something that could break without warning, it works. For now.
But that last part is doing a lot of heavy lifting.
NewPipe exists in Google's blind spot. It works because it doesn't have enough users to make Google's legal team sit up straight. We've already seen exactly what happens when an alternative client gets too popular — YouTube Vanced was more polished, more widely used, and better maintained than most alternatives out there. Google sent the cease-and-desist anyway and it was gone. Not slowed down. Gone.
"Works until Google notices" isn't a solution. It's borrowed time with extra steps. And it only works on Android — so if you're on iOS, a desktop browser, or anything else, you're not even in the conversation. For the average person who just wants to listen to a video with their screen off without jumping through hoops, recommending they sideload an APK and hope Google doesn't notice isn't really an answer. It's a workaround that proves the point: there is no clean solution here, because Google has made sure of it.
One More Thing: Manifest V3 Wasn't Really About Security
While we're being honest about Google's motives, it's worth saying the quiet part out loud about Manifest V3 — the extension framework Google pushed for Chrome that's been steadily hobbling ad blockers.
The official line was security, performance, privacy. Protecting users from malicious extensions. And sure, there are legitimate arguments buried in there somewhere.
But look at what MV3 actually does. It guts the webRequest API — the real-time request interception that made uBlock Origin so effective. Replaced it with a declarativeNetRequest system that's less flexible, has hard caps on the number of filtering rules, and critically, can't react dynamically to what it sees. The old API let a blocker work like a bouncer making judgment calls at the door. The new one gives it a fixed list and tells it not to improvise.
Google controls Chrome. Google's primary business is advertising. Google introduced a "security improvement" that surgically removes the capabilities most dangerous to ad delivery while leaving their own ad infrastructure untouched.
That's not a coincidence. That's vertical integration with a press release attached.
The practical takeaway on browsers: Chromium-based browsers are the most exposed here — Chrome most of all, but any Chromium fork inherits the MV3 limitations to varying degrees. Firefox and its hardened forks like Librewolf are in a better position because Mozilla hasn't gone down the MV3 route the same way. On iOS, Orion is worth knowing about — it's WebKit-based like Safari, but with native extension support including uBlock Origin, which keeps you out of the MV3 trap entirely on a platform where that's usually not an option. None of these are permanent solutions if SSAI becomes the norm, but for the current fight they matter.
#google #youtube #privacy #userhostile #adblockers #blog
Want to talk about big tech war on users? Find me on Mastodon at @ppb1701@ppb.social