chrome.experimental.* APIs

List of APIs

We'd like your feedback on the following experimental APIs:

experimental.devtools.audits Use the chrome.experimental.devtools.audits API to add new audit categories to the Developer Tools' Audit panel.
experimental.devtools.console Use the chrome.experimental.devtools.console API to retrieve messages from the inspected page console and post messages there.

Pay special attention to the following APIs, which we expect to finalize soon: devtools, permissions, For examples of using the experimental APIs, see Samples.

Caution: Don't depend on these experimental APIs. They might disappear, and they will change. Also, the Chrome Web Store doesn't allow you to upload items that use experimental APIs.

How to use experimental APIs

  1. Make sure you're using either Canary (which you can use at the same time as other Chrome channels) or the Dev channel. Although the experimental APIs might work in other versions, we need your feedback on the latest incarnation of the APIs, which you can find in Canary and on the Dev channel.
  2. Specify the "experimental" permission in your manifest, like this:
    "permissions": [
  3. Enable the experimental API in your browser. You can do this in either of two ways:
    • Go to chrome://flags, find "Experimental Extension APIs", click its "Enable" link, and restart Chrome. From now on, unless you return to that page and disable experimental APIs, you'll be able to run extensions and apps that use experimental APIs.
    • Specify the --enable-experimental-extension-apis flag each time you launch the browser. On Windows, you can do this by modifying the properties of the shortcut that you use to launch Google Chrome. For example:
      path_to_chrome.exe --enable-experimental-extension-apis
  4. Give us feedback! Your comments and suggestions help us improve the APIs and decide which ones should move from experimental to supported.

More APIs

For information on the standard APIs, see chrome.* APIs and Other APIs.