Draft article not currently submitted for review. This is a draft Articles for creation (AfC) submission. It is not currently pending review. While there are no deadlines, abandoned drafts may be deleted after six months. To edit or make changes to this draft, simply click on the "Edit" tab at the top of the window. To be accepted, a draft should: Show the subject qualifies for a Wikipedia article by using multiple sources that meet four criteria. The sources should be (1) reliable (2) secondary (3) independent of the subject (4) talk about the subject in some depth. For some topics, there are alternative criteria. Be written from a neutral point of view Respect copyright and do not plagiarize. Do not copy-paste. It is strongly discouraged to write about either yourself or your business or employer. If you do so, you must declare it. Where to get help If you need help editing or submitting your draft, please ask us a question at the AfC Help Desk or get live help from experienced editors. These venues are only for help with editing and the submission process, not to get reviews. If you need feedback on your draft, or if the review is taking a lot of time, you can try asking for help on the talk page of a relevant WikiProject. Some WikiProjects are more active than others so a speedy reply is not guaranteed. How to improve a draft Wikipedia:Contributing to Wikipedia – a basic overview on how to edit Wikipedia. Help:Wikitext – how to use the markup Help:Referencing for beginners – how to include references Wikipedia:Article development – how to develop your article Wikipedia:Writing better articles – how to improve your article Wikipedia:Verifiability – make sure your article includes reliable third-party sources You can also browse Wikipedia:Featured articles and Wikipedia:Good articles to find examples of Wikipedia's best writing on topics similar to your proposed article. Improving your odds of a speedy review To improve your odds of a faster review, tag your draft with relevant WikiProject tags using the button below. This will let reviewers know a new draft has been submitted in their area of interest. For instance, if you wrote about a female astronomer, you would want to add the Biography, Astronomy, and Women scientists tags. Add tags to your draft Editor resources Easy tools: Citation bot (help) | Advanced: Fix bare URLs Last edited by Qwerfjkl (bot) (talk | contribs) 53 days ago. (Update) Submit the draft for review!

wBlock is a free and open-source content blocker and ad-blocking application for Apple's Safari web browser. It is available for macOS, iOS, and iPadOS, and is designed to block advertisements, trackers, cookie notices, pop-ups, and other unwanted web content through Safari's native content-blocking framework. The software is developed by Alexander Skula and distributed through the Apple App Store. wBlock emphasizes low memory usage, large filter-list capacity, and support for user customization through filter lists and userscripts. ^[1][2]

wBlock originated as an open-source Safari content blocker intended to provide a lightweight alternative to commercial Safari ad blockers. Early public releases were distributed through GitHub and discussed in online communities focused on Safari extensions and macOS software. During 2025, the project underwent substantial architectural changes, including support for iOS and a redesign that expanded rule capacity through the use of multiple Safari content-blocking extensions. ^[3]

By late 2025, the application became available through the Apple App Store for both macOS and iOS platforms. ^[4]

wBlock uses Safari's declarative content-blocking APIs to block:

• Advertisements
• Tracking scripts
• Cookie consent banners
• Pop-ups
• Redirects
• Other unwanted web content

The software supports both network-level request blocking and cosmetic filtering through CSS-based element hiding. It also includes script-blocking capabilities for selected web resources. ^[1]

wBlock supports:

• Built-in filter subscriptions
• AdGuard-syntax filter lists
• Custom filter lists imported from URLs, files, or pasted text
• Regional filter subscriptions
• Automatic filter updates

Filter selections can be synchronized across devices through Apple's iCloud infrastructure. ^[1]

One of wBlock's distinguishing features is support for userscripts. The application includes a userscript engine with compatibility for several Greasemonkey-style APIs, including:

• GM_getValue
• GM_setValue
• GM_xmlhttpRequest

Userscripts can be used to customize websites or add functionality not available through standard Safari extensions. ^[1][2]

wBlock includes an "Element Zapper" feature that allows users to visually select and hide webpage elements. The tool is available on macOS, iOS, iPadOS, and visionOS. Hidden elements can be converted into persistent cosmetic filtering rules. ^[1][3]

Users can:

• Disable blocking on specific websites
• Maintain a whitelist of trusted domains
• Review blocked requests (macOS version)
• Configure update intervals

These controls are accessible through Safari integration and the application's settings interface. ^[1]

wBlock is implemented primarily in Swift and relies heavily on Apple's Safari content-blocking framework. According to the project's documentation, the software uses:

• Protocol Buffers for filter storage
• LZ4 compression
• Asynchronous I/O operations
• Swift concurrency features
• Multiple Safari content-blocking extensions

Safari limits individual content-blocking extensions to a fixed rule capacity. To increase total filtering capacity, wBlock distributes rules across five separate content-blocking extensions. The project states that this architecture allows approximately 750,000 rules on supported platforms, substantially exceeding the limits of a single Safari content blocker. ^[1][3]

The project's documentation and App Store listing claim that wBlock uses approximately 40 MB of memory while idle. Because Safari executes content-blocking rules through native browser mechanisms rather than continuously running extension code, much of the filtering workload occurs outside the application's process. ^[1][2]

Independent verification of these performance claims has not been published in peer-reviewed literature.

wBlock has received positive attention within portions of the Safari and ad-blocking communities for its open-source licensing, large rule capacity, and userscript support. Community discussions have highlighted its ability to work within Safari's content-blocking restrictions while offering advanced customization options. ^[3][5]

However, users have also reported issues including:

• Inconsistent blocking effectiveness on some websites
• Website compatibility problems
• Configuration complexity arising from multiple Safari extensions
• Occasional interaction issues with Safari browser settings

Such reports have appeared in community forums and discussion boards. ^[6][7][8]

Like many Safari content blockers, wBlock relies on Apple's declarative content-blocking APIs rather than the more powerful request-interception mechanisms available to some browser extensions on other platforms. This approach generally improves efficiency and battery usage but may impose limitations on dynamic filtering capabilities. ^[1]

The software is commonly compared with Safari-focused blockers such as AdGuard for Safari and Wipr, as well as with the Safari-compatible version of uBlock Origin Lite. Community discussions show differing opinions regarding effectiveness, usability, and trustworthiness among these alternatives. ^[5][6]

wBlock is released as open-source software under the GNU General Public License version 3 (GPL-3.0). Source code is publicly available through GitHub. ^[1][9]

• Ad blocking
• Safari (web browser)
• Content blocker
• uBlock Origin
• AdGuard