A Safari content blocker for macOS, iOS, and iPadOS.
750,000 rules across 5 extensions, Protocol Buffer storage, LZ4 compression, and 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 |
|
iPadOS Interface Full-featured blocking on iPad |
|
Core Architecture
|
Dependencies & Standards
|
How does wBlock compare to other ad blockers?
Check out our comparison guide vs uBlock Origin Lite, Wipr 2, and AdGuard Mini.
Should I install wBlock from the App Store or the DMG/Homebrew release?
The App Store version is generally preferred because it provides automatic app updates. The DMG/Homebrew release has the same features and is available for users who prefer installing outside the App Store.
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.
Should I enable more filter lists for better blocking?
Usually not. The recommended defaults already cover most ads and trackers, and most other general-purpose lists overlap with them. Enabling more mainly uses up Safari's rule limit and increases the chance of site breakage. The exceptions are Annoyances filters (cookie banners, popups, social widgets) and regional filters for non-English sites, which block things the defaults don't.
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 and iPadOS?
Yes. The userscript engine implements the Greasemonkey API (GM_getValue, GM_setValue, GM_xmlhttpRequest, GM_addStyle) on iOS, iPadOS, 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. On macOS, enabling auto-update registers a bundled launch agent that can keep checking while the app is closed through a background update service. On iOS and iPadOS, background checks are best-effort and may wait until the system wakes wBlock or you reopen it. Opening Safari does not trigger updates. Updates use HTTP conditional requests (If-Modified-Since/ETag headers) to minimize bandwidth usage.
Is the element zapper available on iOS and iPadOS?
Yes. Open the wBlock extension popup in Safari and tap Activate Element Zapper.