Getting started

Understand browser access and permissions

Learn why Shield needs website access and which optional capabilities differ between browsers.

Quick answer

Shield AdBlock supports Chrome, Edge, and Firefox. It needs website access to apply protection across the websites you visit. Withholding that access can leave page features unavailable, even when a protection setting is switched on.

Browsers do not expose every capability in the same way. Built-in Page Fixes are separate from fixes supplied by sources you add. You do not need added-source fixes to use Shield’s default protection.

Where to find it

Open your browser’s extension or add-on manager and find Shield AdBlock. Review its enabled state and website access. The exact permission labels depend on your browser. Shield also displays access or capability warnings in its own interface when it can identify a limitation.

What to do

  1. Check that Shield is enabled in the browser’s extension manager.
  2. Review its website access if Shield reports an access warning.
  3. Allow access on the websites where you want Shield to work.
  4. Reload the affected website after changing access.
  5. Open Shield on that website and check its status again.

Chrome and Edge use browser-managed request-blocking rules. Firefox uses its request-blocking extension API. Page hiding and other page features also need access to the page. A count, or the absence of one, cannot confirm that every protection feature is working.

Shield AdBlock 1.0.2 packages for Chrome, Edge and Firefox omit Fixes from Added Sources, including scriptlets from lists you add and from rules you write. A browser permission cannot add that omitted capability. Built-in Page Fixes still have their own setting.

Automatic backups ask for the optional downloads permission when you turn them on. You can decline it. That choice affects only the backup files, not ordinary ad blocking. Read the backup guidance before turning on automatic backups on a shared device.

What should happen

With suitable website access, Shield should be able to apply the features available in your browser package. Restricted browser pages and extension stores are not ordinary website test pages. Check a normal HTTP or HTTPS website instead.

Undo or limit access

You can revise website access in your browser’s extension manager. If you restrict it, expect gaps on affected sites. For a short troubleshooting test on one website, a site pause is easier to review and resume inside Shield.

If that does not work

Record the browser version, Shield version, and exact warning. Follow Shield appears inactive if protection still seems absent after a reload. Avoid enabling Developer Mode merely to dismiss a warning.

Contact support and share a report if you need more help. You can also find the support contact details.

Still need help? Contact support