Safari's ad-blockers are not really comparable[0] to what's currently possible on Firefox, Chrome, or other Chromium-based browsers. They rely on declarative b

Safari's ad-blockers are not really comparable[0] to what's currently possible on Firefox, Chrome, or other Chromium-based browsers. They rely on declarative blocking and/or system-wide interception (ie, you run them as an entirely separate app outside of Safari). The majority of them are not going to be able to handle things like CNAME unmasking or page source rewrites[1]. The declarative blocking API in Safari isn't built to support those kinds of features. [0] https://github.com/el1t/uBlock-Safari/issues/158 https://github.com/el1t/uBlock-Safari/issues/158 [1] The exception to this being maybe AdGuard when you run it system-wide? I vaguely remember reading that it sets itself as a MITM for all of your web traffic at an OS level, which allows it to do page-source rewrites. I could be wrong about that though.