Which sites does <all_urls> cover?

<all_urls> covers http, https, file and other supported schemes. In practice, a content script with this match can run on almost every ordinary web page. The extension still needs the relevant API permission for specific browser data.

A more limited pattern names one host or a wildcard subdomain. Broad wildcard patterns and all_urls are common in ad blockers, password managers, accessibility tools and developer utilities, which makes context essential.

Related pages:Chrome host permissionsall sites permission

What can an extension do with it?

With all_urls and the right supporting permissions, an extension can inject scripts, read page content, observe navigation, modify forms and send messages between contexts. Without scripting or API permissions, the practical reach is smaller.

A content script can also read document.cookie where cookies are not HttpOnly. The cookies permission is separate and grants broader cookie API access.

Related pages:content script matches explainedcookies permission

How to decide whether to accept it

Ask whether the feature genuinely requires every site. A password manager may need to recognize login forms everywhere; a shopping coupon tool may need many retail sites; a niche utility usually does not need all_urls.

Look for narrow alternatives, check the publisher's privacy policy and restrict site access in the browser if the extension supports it. Review again after updates.