Declare permissions and warn users
An extension's ability to access websites and most Chrome APIs is determined by its declared permissions. Permissions should be restricted to only what is needed for its functionality. Limiting permissions establishes an extension's capabilities and reduces possible incursion to data if the extension is compromised by an attacker. Protect extensions and their users by implementing explicit, minimal and optional permissions.
Permissions are known strings that refer to a Chrome API or match patterns that grant access to one or more hosts. They are listed in the manifest and specified as required permissions or optional permissions.
"name": "Permissions Extension",
Limit required permissions to only what is needed for the extension's core functionality. An extension should not request more permissions than it needs; do not future-proof by requesting permissions that may be needed in a future update.
Permissions needed for optional features should be registered as optional permissions. This allows users to decide how much access they are willing to provide an extension and which features are desired.
Identify required permissions
A simple extension may need to request multiple permissions, and many permissions display warnings on installation. Users are more likely to trust an extension with limited warnings or when permissions are explained to them.
Identify the core functionality of an extension and what permissions are required for it. Consider making features optional if they require permissions with warnings.
Trigger optional permissions with events
The optional permissions sample extension's core functionality is overriding the new tab page. One feature is displaying the user's goal of the day. This feature only requires the storage permission, which does not include a warning.
The extension has an additional feature; displaying the user's top sites. This feature requires the topSites permission, which has a warning.
Developing features that rely on permissions with warnings as optional and introducing those features organically gives users a risk-free introduction to the extension. Additionally, this allows users to further customize their experience with an extension and creates an opportunity to explain warnings.
Substitute the activeTab permission
"activeTab" permission grants temporary access to the site the user is on and allows the extension to use host permissions on the current tab. It replaces
"<all_urls>" in many cases and displays no warning on installation.
For details, see Using the activeTab permission.
If an extension needs to access
file:// URLs or operate in incognito mode, users will need to enable access for those features inside the extension's detail page at chrome://extensions.
An extension can detect if it is enabled in incognito mode by calling
extension.isAllowedIncognitoAccess() or able run on
file:// URLs with
Permission warnings exist to describe the capabilities granted by an API to extension users, but some of these warnings may not be obvious at first. For instance, adding the
"tabs" permission results in a seemingly unrelated warning: the extension can Read your browsing activity. Although the Tabs API might be used to only open new tabs, it can also be used to see the URL that is associated with every newly opened tab by using their tabs.Tab objects.
When possible, implement optional permissions or a less powerful API to avoid alarming warnings.
No permission warnings will be displayed if an extension is loaded as an unpacked file. To view an extension's permission warnings, navigate to
chrome://extensions, ensure developer mode is enabled and click PACK EXTENSION.
Specify the path to the extension's folder in the Extension root directory field then click the Pack Extension button. Ignore the Private key field for a first-time package.
Chrome will create two files, a
.crx file and a
.pem file. The
.pem file contain the private key used to sign the extension.
Do not lose the private key! Keep the
.pem file in a secret and secure place; it will be needed to update the extension.
.crx file by dropping it into the Chrome Extension's Management page.
After dropping the
.crx file the browser will ask if the extension can be added and display warnings.
Permissions with warnings
Some permissions may not display warnings when paired with other permissions. For example, the
"tabs" warning will not show if the extension also requests
The permissions warning table is updated on a best-effort basis and may contain slight discrepancies with the current warnings. To verify the most recent warnings shown for extension permissions, follow the steps in Viewing Warnings.
|Grants access to all hosts. Consider using the activeTab permission instead.||Read and change all your data on all websites|
|Grants access to ||Read and change your data on |
|Allows the extension to modify individual accessibility feature states. See the chrome.accessibilityFeatures API for details.||Change your accessibility settings|
|Allows the extension to read individual accessibility feature states. See the chrome.accessibilityFeatures API for details.||Read your accessibility settings|
|Grants access to the chrome.bookmarks API.||Read and change your bookmarks|
|Required if the extension uses ||Read data you copy and paste|
|Indicates the extension uses ||Modify data you copy and paste|
|Grants access to the chrome.debugger API.|
|Grants access to the chrome.declarativeNetRequest API.||Block content on any page|
|Grants access to functions and events which return information on declarative rules matched. See the chrome.declarativeNetRequest API for details.||Read your browsing history|
|Grants access to the chrome.desktopCapture API.||Capture content of your screen|
|Grants access to the chrome.downloads API.||Manage your downloads|
|Grants access to the Favicon API.||Read the icons of the websites you visit|
|Allows the extension to use the HTML5 geolocation API without prompting the user for permission.||Detect your physical location|
|Grants access to the chrome.history API.||Read and change your browsing history|
|Grants access to the email address through the chrome.identity API.||Know your email address|
|Grants access to the chrome.management API.||Manage your apps, extensions, and themes|
|Grants access to the native messaging API.||Communicate with cooperating native applications|
|Grants access to the chrome.notifications API.||Display notifications|
|Grants access to the chrome.pageCapture API.||Read and change all your data on all websites|
|Grants access to the chrome.privacy API.||Change your privacy-related settings|
|Grants access to the chrome.proxy API.||Read and change all your data on all websites|
|Grants the extension access to the chrome.sessions API and chrome.history API.||Read and change your browsing history on all your signed-in devices|
|Grants the extension access to the chrome.sessions API and privileged fields of the ||Read your browsing history on all your signed-in devices|
|Grants access to the chrome.system.storage API.||Identify and eject storage devices|
|Grants the extensions access to the chrome.tabCapture API.||Read and change all your data on all websites|
|Grants access to the chrome.tabGroups API.||View and manage your tab groups|
|Grants access to privileged fields of the ||Read your browsing history|
|Grants access to the chrome.topSites API.||Read a list of your most frequently visited websites|
|Grants access to the chrome.ttsEngine API.||Read all text spoken using synthesized speech|
|Grants access to the chrome.webNavigation API.||Read your browsing history|
When an extension is updated to include a new permission that triggers a warning it may temporarily disable it. The user will have to re-enable it after agreeing to any new warnings.
This can be avoided by making the new feature optional and adding new permission updates to
optional_permissions in the manifest.