Managing Safari Content Blockers and WebExtensions on iOS

This article provides a straightforward guide on how to distinguish and separately manage Content Blockers and standard WebExtensions in Safari on iOS. While Apple groups both tool types under a single menu in the system settings, they operate differently and feature distinct management controls. Below, you will learn how to identify which type of extension you are adjusting in the iOS Settings app, how to configure their specific permissions, and how to toggle Content Blockers independently from WebExtensions directly inside the Safari browser.

To manage your browser add-ons, you must first access the central extensions menu in your device settings:

  1. Open the Settings app on your iPhone or iPad.
  2. Scroll down and tap Safari (on iOS 18 and later, tap Apps at the bottom of the settings list, then select Safari).
  3. Scroll to the General section and tap Extensions.

In earlier versions of iOS, Apple separated this menu into two distinct headers: "Allow These Content Blockers" and "Allow These Extensions." In modern versions of iOS, both types are merged into a single alphabetical list. Because they are combined, you must tap on an individual item to manage its specific behavior.

Managing Content Blockers in Settings

Content Blockers do not actively read your webpage data; instead, they feed a list of rules to Safari to block ads, trackers, or specific page elements before they load. Because they do not access your browsing data, their settings menu is minimal.

  1. In the Extensions menu, tap on the name of a Content Blocker (many apps will include words like "Blocker," "AdGuard," or "1Blocker" in their sub-tools).
  2. Toggle Allow Extension on or off to enable or disable the blocker entirely.
  3. Toggle Allow in Private Browsing if you want the rules applied in private tabs.

You can immediately identify an item as a Content Blocker because there will be no Website Permissions section at the bottom of its settings page.

Managing Standard WebExtensions in Settings

Standard WebExtensions actively read and modify webpage content to perform tasks like filling in passwords, checking grammar, or applying coupon codes. Managing them requires setting both an activation toggle and data access permissions.

  1. In the Extensions menu, tap on the name of a standard WebExtension.
  2. Toggle Allow Extension on or off.
  3. Below the main toggles, look for the Permissions section. This section only appears for standard WebExtensions.
  4. Set access levels for specific websites, or tap All Websites to set a global rule (Ask, Deny, or Allow).

By adjusting the Permissions settings rather than the main toggle, you can keep a WebExtension enabled while restricting it from running automatically, whereas Content Blockers are strictly all-or-nothing in the Settings app.

Toggling Content Blockers Separately Inside Safari

If a website is broken and you want to disable your Content Blockers without turning off your active WebExtensions (like your password manager), you do not need to go into the iOS Settings app. Safari provides a dedicated override solely for Content Blockers in the address bar.

To toggle Content Blockers only:

  1. Open Safari and navigate to a webpage.
  2. Tap the Page Menu icon (the aA icon or the puzzle piece/rectangle icon, depending on your iOS version) on the left side of the address bar.
  3. Tap Turn Off Content Blockers. This immediately reloads the page without ad or tracker blocking, while leaving all standard WebExtensions fully operational.
  4. Alternatively, you can touch and hold the Reload button (the circular arrow) in the address bar and select Reload Without Content Blockers for a one-time bypass.

To toggle WebExtensions only:

  1. Tap the Page Menu icon in the Safari address bar.
  2. Tap Manage Extensions.
  3. Use the switches here to toggle standard WebExtensions on or off. Note that pure Content Blockers will not appear in this in-browser pop-up list; they can only be toggled globally via the main iOS Settings app or bypassed per-site using the "Turn Off Content Blockers" button.