Chrome Extension declarativeNetRequest Permission (2026)

Chrome extension declarativeNetRequest permission

The declarativeNetRequest permission lets an extension block, redirect or modify network requests using predefined rules, shown to users as "block content on any page". It powers most Manifest V3 ad blockers, privacy tools and content filters without letting the extension read page content directly.

Last reviewed September 26, 2026 · 1 listing · Independent, not affiliated with Google

This permission replaced the older, more invasive webRequest blocking approach in Manifest V3, so an extension using it follows a more restricted, rule-based model. It is expected in ad blockers and content filters, and understanding how it differs from broader access helps you judge extensions using it.

What the declarativeNetRequest permission allows

This permission lets an extension supply Chrome with a set of rules to block, redirect or modify network requests, such as blocking ad-serving domains or stripping tracking parameters from URLs. Chrome enforces the rules itself, so the extension does not need to inspect every request's content directly.

Which extensions legitimately need it

Ad blockers, tracker blockers, privacy filters and content-blocking security tools need this permission because filtering network requests is their core function. It is a standard, expected permission for this category and is generally lower risk than permissions granting direct page content access.

How to check or remove this permission

Open chrome://extensions, click Details on the extension to view its permissions and site access. To stop the blocking rules from applying, you can disable or remove the extension from the Details page or from Manage extensions.

Chrome extension declarativeNetRequest permission: FAQs

What does the declarativeNetRequest permission do?

It lets an extension supply rules that tell Chrome to block, redirect or modify network requests, such as blocking ad domains, without the extension needing to inspect every request's content itself.

Why is declarativeNetRequest shown as "block content on any page"?

Because the rules an extension supplies can apply across any website you visit, Chrome summarizes this broad blocking capability under a single, more understandable warning.

Is declarativeNetRequest safer than the older webRequest permission?

Generally yes. Since Chrome enforces the rules itself rather than routing every request through the extension's code, this model limits how much request content the extension can directly inspect.

Do all ad blockers use the declarativeNetRequest permission?

Most modern ad blockers built for Manifest V3 use it, since Chrome requires this rule-based approach for network blocking rather than the older, more invasive request-interception method.

Can declarativeNetRequest read the content of pages I visit?

No, not by itself. It works by matching and acting on network requests using predefined rules; reading actual page content requires separate permissions such as host access or scripting.

How do I remove a content-blocking extension?

Open chrome://extensions in your browser, find the extension in the list, and click Remove to uninstall it. You can review its Details page first to see exactly which rules and permissions it uses before removing it.

Why do privacy extensions request declarativeNetRequest?

Privacy extensions use it to block trackers, analytics scripts or third-party requests across websites, which is exactly the kind of network-level blocking this permission is designed for.

Does this permission let an extension redirect me to other sites?

Yes, the rules can redirect matching requests to a different URL, which is a legitimate technique for some privacy tools but worth confirming for less familiar extensions.

Is declarativeNetRequest required for Manifest V3 extensions?

It is the standard approach for network request blocking under Manifest V3, replacing broader blocking through the older webRequest API used in Manifest V2.

Should I trust an extension with both declarativeNetRequest and all-urls?

This combination is common and expected for ad and tracker blockers, since they need both broad reach and request-blocking rules to filter content across every site.

Does declarativeNetRequest work the same in Edge and Brave?

Chromium-based browsers like Edge and Brave support the same declarativeNetRequest API as Chrome, so extensions using it behave consistently across these browsers.