wBlock

Apple built Safari’s content-blocking system around a deliberate trade-off. Blockers don’t watch your browsing. They hand Safari a list of declarative rules, and Safari enforces them. That design is excellent for privacy, and it is why the iPhone never had the extension mess desktop Chrome lived with for a decade. The cost is capability. Each content blocker is capped at 150,000 rules, and a serious set of filter lists covering ads, trackers, malware, annoyances and regional sites goes past that number quickly.

Most Safari blockers deal with the ceiling in one of two ways. They trim their lists and hope you don’t notice the gaps, or they keep the good parts behind a subscription. wBlock, built by independent developer Alexander Skula, does something else. It converts filter lists written in AdGuard syntax, which is the most expressive and widely maintained format in the ad-blocking world, into Safari’s native rule format. Then it spreads those rules across five separate content blockers. Five blockers at 150,000 rules each gives a theoretical ceiling of 750,000 rules. It is a workaround, but a clever and legitimate one, and it uses Apple’s API exactly as designed.

The rest of the offer is just as unusual. wBlock is free and open source under GPL-3.0, with the code on GitHub. It has no in-app purchases and collects no data. That puts it in direct competition with Wipr 2, which costs money up front, AdGuard, which saves some features for paid tiers, and uBlock Origin Lite, which is the open-source favorite. Users in the US App Store frequently rank wBlock above all three. It holds a 4.8 out of 5 from 170 ratings. That sample is small, but the enthusiasm is consistent and it shows up in the details of the reviews, which is more convincing than a large number of vague five-star ratings.

wBlock also runs on Mac, iPad and Apple Vision Pro, and settings sync through iCloud. This review covers the iOS version.

• Five-Blocker Architecture: AdGuard-syntax filter lists are converted and split across five Safari content blockers, which avoids the 150,000-rule limit per blocker.
• Link Tracking Removal: Tracking parameters are removed from URLs by default, so you don’t have to opt in.
• Scripts Extension: A separate extension runs a Greasemonkey-compatible userscript engine, supports UserCSS userstyles, and includes a built-in catalog of scripts, such as restoring YouTube dislikes or reshaping social media feeds.
• Tube Cleaner & Player Cleaner: These restore Safari’s native video controls and Picture-in-Picture. Tube Cleaner also includes SponsorBlock.
• Per-Site Toolbar Switches: Filtering, userscripts and autoplay can each be turned on or off for an individual site.
• Element Zapper: Hides any page element that the filter lists missed.
• Scheduled Updates: Filter refreshes can run anywhere from hourly to weekly.
• Power-User Plumbing: Custom filter lists, logs and iCloud settings sync.

The Five-Blocker Gambit

wBlock’s central idea is unglamorous plumbing, and it is the most important thing the app does. On Safari, an ad blocker is only as good as the rules it can load. A blocker that drops a regional list or a cosmetic annoyance filter to stay under the cap will leave visible gaps: an autoplaying video on a news site, a cookie banner that doesn’t close, a sticky newsletter popup. Splitting rules across five blockers removes that compromise for all practical purposes.

Building on AdGuard syntax was also the right decision. It is the most widely supported filter dialect in the ad-blocking world, so wBlock benefits from an established community of filter maintainers and doesn’t need its own. It also lets wBlock accept custom filter lists, which turns it from a fixed product into a platform. If you already maintain your own rules, you can bring them with you.

Then there is the default link-tracking removal. Most privacy tools treat parameter stripping as an advanced setting buried in a submenu. wBlock enables it from the start. That is a clear statement of priorities, and it helps the user who never opens the settings, who is exactly the user who needs it most.

Beyond Static Rules: The Scripts Extension

Static rules have a fundamental limit. They can block a request or hide an element, but they can’t change how a page behaves. wBlock addresses this with a second extension for scripts, and this is where it separates itself from its competitors. Reviewers repeatedly name it as the deciding factor.

A Greasemonkey-compatible userscript engine on iPhone Safari is a meaningful addition. It means the large existing library of userscripts written over the past two decades can run on a phone. UserCSS userstyles cover the cosmetic side, and the built-in catalog helps people who wouldn’t know where to find a script. Getting YouTube dislike counts back or cleaning up a social feed takes a tap from a list, not a trip to a GitHub repository.

Keeping scripts in a separate extension was a thoughtful choice. Safari web extensions that change page content need broad website permissions. Content blockers need none, because they never see your pages. Separating the two means you can use only the blocking side, with its privacy-friendly permission model, and leave the scripts extension off. Combining everything into one permission prompt would have been easier to build. This approach shows the developer understands why Apple’s model works the way it does.

YouTube, Reclaimed

Tube Cleaner is one of the best reasons to install wBlock. YouTube’s mobile web player is designed to push you toward the app, and the results are familiar: custom controls that ignore system conventions and Picture-in-Picture that works unreliably or not at all. Tube Cleaner and Player Cleaner swap in Safari’s native video controls, which brings back PiP and makes web video behave like the rest of iOS. Tube Cleaner also includes SponsorBlock, which skips the sponsored segments inside creators’ videos that network-level blocking can’t touch. One reviewer said wBlock blocked video ads better than anything else they tested. These features explain why that claim is plausible.

Control Surface: Toggles, Zapper, Logs

Ad blockers fail in two ways: they miss things, or they break things. wBlock gives you tools for both. The per-site toolbar switches for filtering, userscripts and autoplay mean a broken checkout page can be fixed without opening the main app. Having three separate switches is the right level of control. If a site breaks because of a userscript, you shouldn’t have to disable ad blocking to fix it.

The element zapper covers what the filter lists miss. One reviewer called it the best they had tried. Logs let you diagnose what happened instead of guessing. Few blockers on iOS offer that kind of visibility.

Where It Stumbles

The complaints are specific and they deserve attention. Several users report that deleted custom filters or userscripts come back. That is a sync or state-persistence bug, and the iCloud sync is the most likely cause. It isn’t serious, but it is exactly the kind of bug that makes users stop trusting a power-user tool. If you delete something, it should stay deleted.

The more concerning report is from an iPad Pro user whose pages hung until they switched to the minimal filter preset. This is the downside of the five-blocker approach. Loading hundreds of thousands of rules has a cost, and wBlock makes it easy to load a lot of them. It is good that a minimal preset exists. Better onboarding guidance would help, along with clearer warnings when a configuration is likely to cause trouble.

Reviewers regularly describe wBlock as well designed, which is notable for a free, single-developer project. Free open-source utilities often look like they were designed by the build system. wBlock looks like an Apple-platform app. Most of its work happens inside Safari, so the main app is essentially a control panel. Its job is to make a complex system easy to read, and from user reports it does that well.

On performance, the architecture helps. Content blocking happens inside Safari’s own engine, not in a script running on every page, so the basic blocking cost is about as low as Safari allows. The developer cites about 40 MB of RAM at idle, which is modest for a tool that manages this much.

The iPad Pro hang is the exception to that efficiency. Large rule sets and heavy script use can overload a device in edge cases, and you should start conservatively and add lists as you go. Expect some variation in scheduled updates too. On iPhone, background work depends on the operating system, so an “hourly” schedule is more of a target than a guarantee. That is iOS behavior, not a wBlock failure, but you should plan around it.

On iPhone, setup has some unavoidable friction. Each of the five content blockers and the scripts extension has to be enabled in Safari’s extension settings, and that is more toggling than a single-blocker app like Wipr requires. It happens once, but it is the price of the five-blocker design, and less technical users may need to read the instructions carefully.

After setup, wBlock fits naturally into iOS. The per-site switches are in Safari’s extension menu where you’d expect them. The native-controls restoration from Tube Cleaner is especially useful on a phone, because Picture-in-Picture and system media controls matter most on a small screen where you are switching between apps constantly.

The element zapper is less pleasant with a finger. Selecting a precise page element is harder with touch than with a cursor, and on iPhone you may hide a parent container when you meant to hide a single banner.

On iPad, a trackpad or mouse makes the zapper much more accurate, and the larger screen makes managing scripts and filters more comfortable. Because of the hang report, iPad users with heavy filter configurations should keep the minimal preset in mind. iCloud sync is a real convenience for anyone who also uses Safari on a Mac, assuming the resurrecting-filters bug gets fixed.

wBlock shouldn’t be this good. It is a free, open-source project from a single developer, and it competes with commercial products that have teams and subscription revenue behind them. By most accounts, it wins. The five-blocker architecture fixes Safari’s most significant limitation. The scripts extension adds capabilities that iOS Safari has never had in one free package. Tube Cleaner solves a problem that frustrates nearly every iPhone user who watches YouTube in the browser.

It isn’t flawless. Filters and scripts reappearing after deletion is a real trust problem for a tool whose value depends on precise control, and the iPad Pro hang shows the power can outrun the hardware if you’re careless. Neither issue is fundamental, and both are fixable. The bigger picture is that wBlock has raised the bar for what a Safari ad blocker should do. For any iPhone user who cares about what loads in their browser, it should be the first install.