Chrome Extension Permissions: Which Ones Trigger Warnings
Originally published on ExtensionBooster. Chrome extension permissions decide whether a user sees a scary warning before installing, and the original guide reports that extensions requesting fewer permissions get 30% hi
Originally published on ExtensionBooster.
Chrome extension permissions decide whether a user sees a scary warning before installing, and the original guide reports that extensions requesting fewer permissions get 30% higher install rates. It also reports that 86% of popular Chrome extensions still ask for high-risk permissions they don't need. Here is a short Manifest V3 reference: what triggers a warning, what doesn't, and how to ask later instead of upfront.
Four manifest keys, two moments
Manifest V3 splits access across four keys. The only real difference is when the user is asked.
| Key | Granted | What the user sees |
|---|---|---|
permissions |
At install | Warning dialog before install |
optional_permissions |
At runtime | Prompt when the feature is used |
host_permissions |
At install | Warning about site access |
optional_host_permissions |
At runtime | Prompt for specific site access |
Rule of thumb: if a feature isn't needed on first launch, make it optional.
{
"permissions": ["storage", "alarms"],
"optional_permissions": ["bookmarks", "history"],
"host_permissions": ["https://api.yourservice.com/*"],
"optional_host_permissions": ["https://*/*"]
}
Permissions that stay silent
These show no install-time warning, so use them freely when you need them:
-
activeTab: temporary access to the current tab after the user clicks your extension -
alarms: scheduled work -
storageandunlimitedStorage: extension data without quota limits -
scripting: programmatic content-script injection -
offscreen: offscreen documents for DOM APIs -
sidePanel: Chrome's side panel -
contextMenus: right-click menu items -
idleandpower: idle detection and sleep control
The most useful pairing is activeTab plus scripting. For most features it replaces a broad host permission, so you can skip <all_urls>.
Permissions that show a warning
Each extra warning costs install conversion. A sample of what users actually read:
| Permission | Warning text |
|---|---|
bookmarks |
"Read and change your bookmarks" |
history |
"Read and change your browsing history" |
tabs |
"Read your browsing history" |
clipboardRead |
"Read data you copy and paste" |
geolocation |
"Detect your physical location" |
desktopCapture |
"Capture screen content" |
declarativeNetRequest |
"Block content on any page" |
nativeMessaging |
"Communicate with native applications" |
Broad host patterns are the worst offenders. https://*/* and <all_urls> both produce "Read and change all your data on all websites".
// Avoid unless you truly need every site
"host_permissions": ["<all_urls>"]
// Scope to what the extension uses
"host_permissions": ["https://api.yourapp.com/*"]
// Better still: ask at runtime
"optional_host_permissions": ["https://*/*"]
Ask at the moment of need
Optional permissions are requested with chrome.permissions from a click handler, right when the feature is switched on:
document.getElementById('enable-bookmarks').addEventListener('click', async () => {
const granted = await chrome.permissions.request({ permissions: ['bookmarks'] });
if (granted) loadBookmarks();
else showWhyPermissionHelps();
});
// Inspect and clean up later
const current = await chrome.permissions.getAll();
await chrome.permissions.remove({ permissions: ['history'] });
The guide reports that runtime requests convert 30% better than install-time warnings. Always handle the "no" branch so the core extension still works.
Pre-publish audit
- Delete permissions your code no longer calls.
- Move secondary-feature permissions to
optional_permissions. - Replace
<all_urls>with specific domains, or make them optional. - Use
activeTabinstead oftabsunless you need background tab URLs. - Explain each permission in your store listing.
- Test with every optional permission denied.
Two common slips: requesting tabs just to open a new tab (chrome.tabs.create() doesn't need it), and requesting history when you only need the current URL (activeTab covers that).
Key takeaways
- Fewer warnings means more installs, so every permission has to earn its place.
-
activeTabplusscriptingcovers most tab-access needs without a warning. - Anything for a secondary feature belongs in
optional_permissions. - Scope host permissions to the domains you really call.
- Audit the manifest on every release, because permission creep is easy to miss.
The full guide has the complete permission-by-permission list, a required-vs-optional decision flow and an API-to-permission map: see the complete Chrome extension permissions cheatsheet. If you want to grow an extension once the manifest is lean, ExtensionBooster's growth tools for Chrome extension developers are worth a look.
Which permission did you end up making optional, and did the install rate or review feedback change afterwards?
Originally published by Dev.to WebDev. Aggregated on AIWithGhost for educational purposes — full credit and traffic to the original publisher.