Chrome Extension Permissions Explained: What Each Warning Really Means
What 'Read and change all your data on all websites' and other Chrome extension warnings really allow, which permissions show no warning, and how to limit them.
When you install a Chrome extension, a small dialog lists what it will be allowed to do. The wording is vague on purpose. Google needs to describe hundreds of technical permissions in a sentence a non-developer can read. That means “Read your browsing history” can mean something narrower than it sounds, while a short, harmless-looking line can hide a lot of power.
This guide explains these permissions from the developer side: what the extension actually asked for, what it can do with it, and when you should be suspicious. The warning texts below are taken from Google’s permissions list for developers, as of November 2026.
How the permission system works
An extension’s manifest.json file declares two kinds of access:
- API permissions (the
permissionskey) unlock browser features: tabs, bookmarks, downloads, history, notifications and so on. - Host permissions (the
host_permissionskey, or content scripts with URL patterns) decide which websites the extension can read and modify.
Chrome converts these into warning sentences. Some permissions produce no warning at all, because Google considers them low-risk. Others are bundled: several different permissions can produce the same sentence.
One more rule matters a lot. If an update asks for a permission with a new warning, Chrome disables the extension and asks you to approve the new access. If you ever see an extension disabled with a note that it “needs new permissions”, stop and read them. That’s exactly the moment a sold or compromised extension tries to expand its reach.
The big one: “Read and change all your data on all websites”
This appears when an extension requests host access to every site, usually with the pattern <all_urls> or *://*/*. It allows the extension to:
- read the full content of every page you open, including text you type into forms;
- change those pages: inject scripts, add buttons, hide elements, rewrite links;
- in combination with other permissions, read and change network requests to those sites.
It does not directly give access to your saved passwords in Chrome’s password manager, to files on your computer, or to other programs. But since a page shows what you type, an extension with this access can capture anything you type into a web page, including logins.
When it’s legitimate: password managers, ad and tracker blockers, grammar checkers, dark-mode tools and translation tools need it to work on any site.
When it’s a red flag: a new-tab page, a timer, a calculator, a screenshot tool that only works when you click it (that should use activeTab, below), or anything whose job is limited to one website.
A narrower version appears as “Read and change your data on a number of websites” or “Read and change your data on example.com”. That’s much better. The extension can only touch the sites listed. Click the line in the dialog to expand it and check the list.
Common warnings, translated
| Warning you see | Permission behind it | What it really allows | Typical legitimate use |
|---|---|---|---|
| Read your browsing history | tabs (and some others) |
See the URL and title of your open tabs as you browse. With tabs alone it doesn’t read your past history database |
Tab managers, session savers |
| Read and change your browsing history on all signed-in devices | history |
Read and delete entries from your actual history, which syncs across devices | History search and cleanup tools |
| Read and change your bookmarks | bookmarks |
Read, add, move and delete bookmarks | Bookmark managers |
| Manage your downloads | downloads |
Start downloads, see your download list, open or remove downloaded files from the list | Download managers, “save as” tools |
| Block content on any page | declarativeNetRequest |
Give Chrome rules to block or redirect requests, without seeing the content of each request | Ad blockers, privacy filters |
| Read data you copy and paste | clipboardRead |
Read what’s on your clipboard | Clipboard managers |
| Display notifications | notifications |
Show system notifications | Reminders, chat tools |
| Manage your apps, extensions, and themes | management |
List, enable or disable your other extensions | Extension managers. Rare otherwise, and worth questioning |
| Communicate with cooperating native applications | nativeMessaging |
Talk to a program installed on your computer | Desktop password managers, enterprise tools |
| Change your privacy-related settings | privacy |
Change settings such as WebRTC handling or prediction services | Privacy tools |
| Capture content of your screen | desktopCapture |
Ask to record your screen, a window or a tab (you still pick what to share) | Screen recorders, meeting tools |
| View and manage your tab groups | tabGroups |
Create, rename and move tab groups | Tab organizers |
| Know your email address | identity.email |
Read the email of the Google account signed into Chrome | Sign-in for the extension’s own service |
Permissions with no warning
Several useful permissions show nothing in the install dialog:
activeTabgives temporary access to the current tab, only after you click the extension’s icon, use its context menu or press its keyboard shortcut. Access ends when you navigate away or close the tab. This is the most privacy-friendly way for a tool to work on “whatever page I’m on”, and good developers prefer it to all-sites access.storagelets the extension save its own settings.alarms,contextMenusandsidePanelhandle timers, right-click menu items and the side panel.scriptinglets it inject scripts, but only on sites it already has host access to (or the active tab after a click).
So a “no warnings” install isn’t automatically safe, but it is very limited. An extension that only has activeTab and storage can do almost nothing until you click it.
Optional permissions: the polite pattern
Well-built extensions often request extra access later, at the moment you use a feature, through optional permissions. You’ll see a small Chrome prompt such as “Allow this extension to read and change your data on github.com?” while you use the extension. This is a good sign. It means the developer kept the install footprint small, and you can say no to one feature without losing the rest.
Taking access back: Site access controls
You don’t have to accept “all sites” access just because the extension asked for it. In Chrome:
- Open
chrome://extensionsand click Details on the extension. - Under Site access, choose:
- On click: works like
activeTab. The extension only gets access to a page when you click its icon. - On specific sites: add the domains where you want it active.
- On all sites: the default for extensions that requested it.
- On click: works like
You can also click the puzzle-piece Extensions icon in the toolbar while on a page and change access for that site. Some extensions break with less access, but many work fine and simply ask for permission when needed. For anything you only use occasionally, On click is a sensible default.
What the dialog doesn’t tell you
The permission dialog describes capability, not behavior. Two extensions with identical permissions can be a trustworthy ad blocker and a data-harvesting one. The dialog also can’t tell you:
- whether data leaves your browser. The Privacy practices section of the store listing is where developers declare what they collect. Since August 2026, Chrome Web Store policy requires that any data collected be strictly necessary for the extension’s single, disclosed purpose, and that collection be prominently disclosed (policy update).
- who owns it now. Extensions get sold. See how to check if an extension is safe.
- what remote servers it talks to. Manifest V3 bans remotely hosted code: an extension can’t download and run new JavaScript outside the store review. But it can still send and receive data, and bad actors keep looking for loopholes.
A quick way to judge any permission request
Ask three questions:
- Scope: does it need all sites, or just one or two? If one, does the dialog say so?
- Timing: does it need access all the time, or only when you click it?
- Fit: would you be surprised to learn the extension used this permission? If yes, don’t install.
Here’s how that plays out for a few common extension types:
- Password manager: all sites + native messaging is expected. Choose a well-known vendor.
- Tab manager: “Read your browsing history” (the
tabspermission) is expected. All-sites access usually isn’t. - AI sidebar or summarizer: often asks for all sites. Prefer ones that work on click with
activeTab. Read our AI extension privacy checklist before installing. - Coupon or cashback tool: all sites + browsing data is its business model. Install only if you accept that trade.
For developers: ask for less
If you build extensions, the fewer warnings your install dialog shows, the more people finish installing. Prefer activeTab over all-sites access, request optional host permissions for specific features, and use declarativeNetRequest instead of observing every request. Asking for less also makes Chrome Web Store review smoother. “Excessive permissions” is one of the most common rejection reasons. We cover it in publishing to the Chrome Web Store.