A Safari content blocker for macOS, iOS, and iPadOS.
750,000 rules across 5 extensions, Protocol Buffer storage, LZ4 compression, iCloud sync.
Note
Looking for a detailed comparison? Check out my comparison guide to see how wBlock stacks up against other Safari content blockers.
|
|
|
Userscript Management Manage paywalls, YouTube Dislikes, and more |
|
Settings & Customization Configure auto-updates, notifications, and preferences |
|
iOS Interface Full-featured blocking on iPhone and iPad |
|
Core Architecture
|
Dependencies & Standards
|
How does wBlock compare to other ad blockers?
Check out our comparison guide vs uBlock Origin Lite, AdGuard, and Wipr.
Can I use my own filter lists?
Yes. You can add any AdGuard-compatible filter list by URL, paste rules directly, or import from a file.
Does wBlock slow down Safari?
No. wBlock uses Safari's native declarative content blocking API, which processes rules in a separate process. Memory overhead is ~40 MB at idle with no measurable impact on page load times.
Do userscripts work on iOS?
Yes. The userscript engine implements the Greasemonkey API (GM_getValue, GM_setValue, GM_xmlhttpRequest, GM_addStyle) on both iOS and macOS via Safari Web Extensions.
How often do filters update?
Auto-update intervals are configurable from 1 hour to 7 days, or manually triggered. Updates use HTTP conditional requests (If-Modified-Since/ETag headers) to minimize bandwidth usage.
Is the element zapper available on iOS?
Yes. Open the wBlock extension popup in Safari and tap Activate Element Zapper.