Use the chrome.contentSettings API to change settings that control whether websites can use features such as cookies, JavaScript, and plugins. More generally speaking, content settings allow you to customize Chrome's behavior on a per-site basis

This permission triggers a warning. Use the chrome.bookmarks API to create, organize, and otherwise manipulate bookmarks. Also see Override Pages, which you can use to create a custom Bookmark Manager page. You must declare the "bookmarks" permission

Use the chrome.contentSettings API to change settings that control whether websites can use features such as cookies, JavaScript, and plugins. More generally speaking, content settings allow you to customize Chrome's behavior on a per-site basis

Use the chrome.bookmarks API to create, organize, and otherwise manipulate bookmarks. Also see Override Pages, which you can use to create a custom Bookmark Manager page. You must declare the "bookmarks" permission in the extension manifest to use

Samples for Chrome Extensions are available on GitHub.

In connection with the Google Chrome Web Store, Google may make certain Chrome Web Store applications available in Google's Play for Education site. If You or Your organization is interested in participating, please verify that the

The Chrome Web Store is committed to fostering a high-quality and trustworthy ecosystem for developers and users. To align with this goal, we're announcing a series of policy updates designed to provide clarity and consistency across our platform.

This reference describes the methods and resource representation available for the Chrome Web Store Publish API. Each resource type has one or more data representations and one or more methods. See Using the Chrome Web Store Publish API for a guide

How to programmatically create, update, and publish items in the Chrome Web Store.

TODO

Extension policies

Use the chrome.sessions API to query and restore tabs and windows from a browsing session. string The name of the foreign device. Session [] A list of open window sessions for the foreign device, sorted from most recently to least recently modified

Use the chrome.printing API to send print jobs to printers installed on Chromebook. All chrome.printing methods and events require you to declare the "printing" permission in the extension manifest. For example: The examples below demonstrate using

Use the userScripts API to execute user scripts in the User Scripts context. To use the User Scripts API, chrome.userScripts, add the "userScripts" permission to your manifest.json and "host_permissions" for sites you want to run scripts on. A user

Use the chrome.sessions API to query and restore tabs and windows from a browsing session. string The name of the foreign device. Session [] A list of open window sessions for the foreign device, sorted from most recently to least recently modified

Use the chrome.printing API to send print jobs to printers installed on Chromebook. All chrome.printing methods and events require you to declare the "printing" permission in the extension manifest. For example: The examples below demonstrate using

Learn how to develop extensions with AI

Learn how to develop Chrome extensions.

Use the chrome.i18n infrastructure to implement internationalization across your whole app or extension. If an extension has a /_locales directory, the manifest must define "default_locale". You need to put all of its user-visible strings into a file

Use the chrome.storage API to store, retrieve, and track changes to user data. The Storage API provides an extension-specific way to persist user data and state. It's similar to the web platform's storage APIs ( IndexedDB, and Storage ), but was

Use the chrome.storage API to store, retrieve, and track changes to user data. To use the storage API, declare the "storage" permission in the extension manifest. For example: The Storage API provides an extension-specific way to persist user data

Use the chrome.enterprise.platformKeys API to generate keys and install certificates for these keys. The certificates will be managed by the platform and can be used for TLS authentication, network access or by other extension through

Use the chrome.enterprise.platformKeys API to generate keys and install certificates for these keys. The certificates will be managed by the platform and can be used for TLS authentication, network access or by other extension through

Use the chrome.permissions API to request declared optional permissions at run time rather than install time, so users understand why the permissions are needed and grant only those that are necessary. Permission warnings exist to describe the

Use the chrome.permissions API to request declared optional permissions at run time rather than install time, so users understand why the permissions are needed and grant only those that are necessary. Permission warnings exist to describe the

Use the chrome.runtime API to retrieve the service worker, return details about the manifest, and listen for and respond to events in the extension lifecycle. You can also use this API to convert the relative path of URLs to fully-qualified URLs. The

An overview of the recent changes in Chrome Extensions, plus exciting upcoming extensions features developers can look forward to.

Use the chrome.tabs API to interact with the browser's tab system. You can use this API to create, modify, and rearrange tabs in the browser. The Tabs API not only offers features for manipulating and managing tabs, but can also detect the language

Use the chrome.tabs API to interact with the browser's tab system. You can use this API to create, modify, and rearrange tabs in the browser. The Tabs API not only offers features for manipulating and managing tabs, but can also detect the language

Use the chrome.ttsEngine API to implement a text-to-speech(TTS) engine using an extension. If your extension registers using this API, it will receive events containing an utterance to be spoken and other parameters when any extension or Chrome App

Use the chrome.cookies API to query and modify cookies, and to be notified when they change. To use the cookies API, you must declare the "cookies" permission in your manifest, along with host permissions for any hosts whose cookies you want to

Use the chrome.cookies API to query and modify cookies, and to be notified when they change. To use the cookies API, declare the "cookies" permission in your manifest along with host permissions for any hosts whose cookies you want to access. For

Use the chrome.ttsEngine API to implement a text-to-speech(TTS) engine using an extension. If your extension registers using this API, it will receive events containing an utterance to be spoken and other parameters when any extension or Chrome App

Recent changes to the Chrome extensions platform, documentation, and policy

Use the chrome.pageCapture API to save a tab as MHTML. MHTML is a standard format supported by most browsers. It encapsulates in a single file a page and all its resources (CSS files, images..). Note that for security reasons a MHTML file can only be

Use the chrome.pageCapture API to save a tab as MHTML. MHTML is a standard format supported by most browsers. It encapsulates in a single file a page and all its resources (CSS files, images..). Note that for security reasons a MHTML file can only be

Chrome Web Store An online marketplace where users can browse for extensions and themes. Publish your extension there and make it accessible to the world. dashboard Developer Dashboard Publish your extension and manage your store items. local_mall

Use the chrome.action API to control the extension's icon in the Google Chrome toolbar. The following keys must be declared in the manifest to use this API. To use the chrome.action API, specify a "manifest_version" of 3 and include the "action" key

Use this API to expose certificates to the platform which can use these certificates for TLS authentications. Typical usage of this API to expose client certificates to ChromeOS follows these steps: The actual sequence of steps can be different. For

The complete reference to all APIs made available to Chrome Extensions. This includes APIs for the deprecated Chrome Apps platform as well as APIs still in beta and dev.

The chrome.extension API has utilities that can be used by any extension page. It includes support for exchanging messages between an extension and its content scripts or between extensions, as described in detail in Message Passing. The type of

The chrome.extension API has utilities that can be used by any extension page. It includes support for exchanging messages between an extension and its content scripts or between extensions, as described in detail in Message Passing. The type of

Use the chrome.declarativeContent API to take actions depending on the content of a page, without requiring permission to read the page's content. The Declarative Content API lets you enable your extension's action depending on the URL of a web page,

Note: this API is deprecated. Check out the declarativeNetRequest API instead. Use the chrome.declarativeWebRequest API to intercept, block, or modify requests in-flight. It is significantly faster than the chrome.webRequest API because you can

Use the chrome.declarativeContent API to take actions depending on the content of a page, without requiring permission to read the page's content. The Declarative Content API allows you to enable your extension's action depending on the URL of a web

Use this API to expose certificates to the platform which can use these certificates for TLS authentications. Typical usage of this API to expose client certificates to ChromeOS follows these steps: The actual sequence of steps can be different. For

Use the commands API to add keyboard shortcuts that trigger actions in your extension, for example, an action to open the browser action or send a command to the extension. The following keys must be declared in the manifest to use this API. The

Use the offscreen API to create and manage offscreen documents. To use the Offscreen API, declare the "offscreen" permission in the extension manifest. For example: Service workers don't have DOM access, and many websites have content security

Use the system.display API to query display metadata. An enum to tell if the display is detected and used by the system. The display is considered 'inactive', if it is not detected by the system (maybe disconnected, or considered disconnected due to

Use the system.display API to query display metadata. An enum to tell if the display is detected and used by the system. The display is considered 'inactive', if it is not detected by the system (maybe disconnected, or considered disconnected due to

How to prepare your extension for the new extensions menu.

The chrome.debugger API serves as an alternate transport for Chrome's remote debugging protocol. Use chrome.debugger to attach to one or more tabs to instrument network interaction, debug JavaScript, mutate the DOM and CSS, and more. Use the Debuggee

Use the chrome.wallpaper API to change the ChromeOS wallpaper. You must declare the "wallpaper" permission in the app's manifest to use the wallpaper API. For example: For example, to set the wallpaper as the image at https://example.com/a_file.png,

Use the chrome.processes API to interact with the browser's processes. number The part of the cache that is utilized, in bytes. number The size of the cache, in bytes. number optional The most recent measurement of the process's CPU usage, expressed

Use the chrome.tts API to play synthesized text-to-speech (TTS). See also the related ttsEngine API, which allows an extension to implement a speech engine. Chrome provides this capability on Windows (using SAPI 5), Mac OS X, and ChromeOS,

The chrome.management API provides ways to manage installed apps and extensions. You must declare the "management" permission in the extension manifest to use the management API. For example: management.getPermissionWarningsByManifest,

The chrome.management API provides ways to manage installed apps and extensions. You must declare the "management" permission in the extension manifest to use the management API. For example: management.getPermissionWarningsByManifest(),

The chrome.declarativeNetRequest API is used to block or modify network requests by specifying declarative rules. This lets extensions modify network requests without intercepting them and viewing their content, thus providing more privacy. The "

Use the chrome.browsingData API to remove browsing data from a user's local profile. You must declare the "browsingData" permission in the extension manifest to use this API. The simplest use-case for this API is a a time-based mechanism for clearing

Use chrome.gcm to enable apps and extensions to send and receive messages through Firebase Cloud Messaging (FCM). The maximum size (in bytes) of all key/value pairs in a message. 4096 Registers the application with FCM. The registration ID will be

Use the chrome.identity API to get OAuth2 access tokens. string A unique identifier for the account. This ID will not change for the lifetime of the account. "SYNC" Specifies that Sync is enabled for the primary account. "ANY" Specifies the existence

Use the chrome.windows API to interact with browser windows. You can use this API to create, modify, and rearrange windows in the browser. When requested, a windows.Window contains an array of tabs.Tab objects. You must declare the "tabs" permission

Use browser actions to put icons in the main Google Chrome toolbar, to the right of the address bar. In addition to its icon, a browser action can have a tooltip, a badge, and a popup. In the following figure, the multicolored square to the right of

Use the chrome.identity API to get OAuth2 access tokens. string A unique identifier for the account. This ID will not change for the lifetime of the account. "SYNC" Specifies that Sync is enabled for the primary account. "ANY" Specifies the existence

Use the chrome.webNavigation API to receive notifications about the status of navigation requests in-flight. All chrome.webNavigation methods and events require you to declare the "webNavigation" permission in the extension manifest. For example: For

Use the chrome.enterprise.hardwarePlatform API to get the manufacturer and model of the hardware platform where the browser runs. Note: This API is only available to extensions installed by enterprise policy. string string Obtains the manufacturer

Use the chrome.vpnProvider API to implement a VPN client. Typical usage of vpnProvider is as follows: Create VPN configurations using the createConfig method. A VPN configuration is a persistent entry shown to the user in a native ChromeOS UI. The

Use the chrome.systemLog API to record Chrome system logs from extensions. string Adds a new log record. MessageOptions The logging options. function optional The callback parameter looks like: Promise<void> Promises are supported in Manifest

Use the chrome.notifications API to create rich notifications using templates and show these notifications to users in the system tray. string optional Button icons not visible for Mac OS X users. string string Additional details about this item.

Use the chrome.loginState API to read and monitor the login state. "SIGNIN_PROFILE" Specifies that the extension is in the signin profile. "USER_PROFILE" Specifies that the extension is in the user profile. "UNKNOWN" Specifies that the session state

Use the chrome.input.ime API to implement a custom IME for Chrome OS. This allows your extension to handle keystrokes, set the composition, and manage the candidate window. You must declare the "input" permission in the extension manifest to use the

The Desktop Capture API captures the content of the screen, individual windows, or individual tabs. Enum used to define set of desktop media sources used in chooseDesktopMedia(). "screen" "window" "tab" "audio" Mirrors SelfCapturePreferenceEnum.

Use the chrome.fileSystemProvider API to create file systems, that can be accessible from the file manager on Chrome OS. You must declare the "fileSystemProvider" permission and section in the extension manifest to use the File System Provider API.

This permission triggers a warning Use the chrome.downloads API to programmatically initiate, monitor, manipulate, and search for downloads. You must declare the "downloads" permission in the extension manifest to use this API. You can find simple

Use the chrome.downloads API to programmatically initiate, monitor, manipulate, and search for downloads. You must declare the "downloads" permission in the extension manifest to use this API. You can find simple examples of using the

Use the chrome.sidePanel API to host content in the browser's side panel alongside the main content of a webpage. To use the Side Panel API, add the "sidePanel" permission in the extension manifest file: manifest.json: The Side Panel API allows

Use the chrome.enterprise.deviceAttributes API to read device attributes. Note: This API is only available to extensions force-installed by enterprise policy. Fetches the administrator-annotated Location. If the current user is not affiliated or no

Use the chrome.power API to override the system's power management features. Using this API, you can specify the Level to which power management is disabled. The "system" level keeps the system active, but allows the screen to be dimmed or turned

Use the chrome.webNavigation API to receive notifications about the status of navigation requests in-flight. All chrome.webNavigation methods and events require you to declare the "webNavigation" permission in the extension manifest. For example: For

Use the chrome.tabCapture API to interact with tab media streams. The chrome.tabCapture API allows you to access a MediaStream containing video and audio of the current tab. It can only be called after the user invokes an extension, such as

Use the chrome.devtools.panels API to integrate your extension into Developer Tools window UI: create your own panels, access existing panels, and add sidebars. The following keys must be declared in the manifest to use this API. See DevTools APIs

Use the chrome.platformKeys API to access client certificates managed by the platform. If the user or policy grants the permission, an extension can use such a certficate in its custom authentication protocol. E.g. this allows usage of platform

Use the chrome.printingMetrics API to fetch data about printing usage. "BLACK_AND_WHITE" Specifies that black and white mode was used. "COLOR" Specifies that color mode was used. "ONE_SIDED" Specifies that one-sided printing was used.

The complete reference to all APIs made available to Chrome Extensions. This includes APIs for the deprecated Chrome Apps platform as well as APIs still in beta and dev.

Use the chrome.notifications API to create rich notifications using templates and show these notifications to users in the system tray. string optional Button icons not visible for Mac OS X users. string string Additional details about this item.

Use the chrome.windows API to interact with browser windows. You can use this API to create, modify, and rearrange windows in the browser. When requested, a windows.Window contains an array of tabs.Tab objects. You must declare the "tabs" permission

The chrome.debugger API serves as an alternate transport for Chrome's remote debugging protocol. Use chrome.debugger to attach to one or more tabs to instrument network interaction, debug JavaScript, mutate the DOM and CSS, and more. Use the Debuggee

Use the chrome.documentScan API to discover and retrieve images from attached document scanners. The Document Scan API is designed to allow apps and extensions to view the content of paper documents on an attached document scanner. string Provides

Use the chrome.fontSettings API to manage Chrome's font settings. To use the Font Settings API, you must declare the "fontSettings" permission in the extension manifest. For example: Chrome allows for some font settings to depend on certain generic

Use the chrome.browsingData API to remove browsing data from a user's local profile. You must declare the "browsingData" permission in the extension manifest to use this API. The simplest use-case for this API is a a time-based mechanism for clearing

Use the chrome.webRequest API to observe and analyze traffic and to intercept, block, or modify requests in-flight. You must declare the "webRequest" permission in the extension manifest to use the web request API, along with the necessary host

An overview of the recent changes in Chrome Extensions, plus exciting upcoming extensions features developers can look forward to.

We're excited to launch a set of UI changes making the Chrome Web Store Developer Dashboard more responsive and mobile-friendly. We hope this gives you a more convenient and accessible experience when monitoring store listing performance, making

The chrome.declarativeNetRequest API is used to block or modify network requests by specifying declarative rules. This lets extensions modify network requests without intercepting them and viewing their content, thus providing more privacy.

Use the chrome.devtools.performance API to listen to recording status updates in the Performance panel in DevTools. See DevTools APIs summary for general introduction to using Developer Tools APIs. The chrome.devtools.performance API allows

Use the chrome.devtools.network API to retrieve the information about network requests displayed by the Developer Tools in the Network panel. Network requests information is represented in the HTTP Archive format ( HAR ). The description of HAR is

Use the chrome.devtools.panels API to integrate your extension into Developer Tools window UI: create your own panels, access existing panels, and add sidebars. Each extension panel and sidebar is displayed as a separate HTML page. All extension

Best practices on how to make a high-quality, engaging listing page for your item in the Chrome Web Store.

An extension must have a single purpose that is narrow and easy to understand. Don't create an extension that requires users to accept bundles of unrelated functionality. If two pieces of functionality are clearly separate, they should be put into

Research and understand the Chrome Web Store policies. Before developing a Chrome extension, it is important to review the Chrome Web Store Developer Program Policies and ensure your extension complies with all guidelines and requirements. Extensions

Extensions must be marketed responsibly. The set of functionalities promised by the extension must be stated clearly and in a transparent manner. The outcome of any user interaction should match the reasonable expectations that were set with the

An overview of the recent changes in Chrome Extensions, plus exciting upcoming extension features developers can look forward to.

If your product has a blank description field or is missing an icon or screenshots, it will be rejected. Ensure your product's listing information is up to date, accurate, and comprehensive. We don't allow extensions with misleading, inaccurate,

This announcement includes a series of updates to Developer Program Policies page designed to encourage the development of high quality products, prevent deceptive behavior, and ensure informed user consent.

Frequently asked questions about Chrome Web Store's policies on deceptive installation tactics.

Frequently asked questions about the single purpose policy.

Use the chrome.input.ime API to implement a custom IME for Chrome OS. This allows your extension to handle keystrokes, set the composition, and manage the candidate window. You must declare the "input" permission in the extension manifest to use the

YouTube is enhancing platform security with Trusted Types to prevent cross-site scripting attacks, but it may impact your extension.

Use the chrome.enterprise.deviceAttributes API to read device attributes. Note: This API is only available to extensions force-installed by enterprise policy. Fetches the administrator-annotated Location. If the current user is not affiliated or no

Use the chrome.enterprise.hardwarePlatform API to get the manufacturer and model of the hardware platform where the browser runs. Note: This API is only available to extensions installed by enterprise policy. string string Obtains the manufacturer

Use the chrome.enterprise.networkingAttributes API to read information about your current network. Note: This API is only available to extensions force-installed by enterprise policy. string optional The device's local IPv4 address (undefined if not

Use the chrome.enterprise.networkingAttributes API to read information about your current network. Note: This API is only available to extensions force-installed by enterprise policy. string optional The device's local IPv4 address (undefined if not

We sat down with the team that leads review in the Chrome Web Store.

Learn how to develop extensions

An explanation of content filtering and how to approach it in your Chrome Extension.

Use the chrome.proxy API to manage Chrome's proxy settings. This API relies on the ChromeSetting prototype of the type API for getting and setting the proxy configuration. You must declare the "proxy" permission in the extension manifest to use the

Use the chrome.loginState API to read and monitor the login state. "SIGNIN_PROFILE" Specifies that the extension is in the signin profile. "USER_PROFILE" Specifies that the extension is in the user profile. "UNKNOWN" Specifies that the session state

Use the chrome.scripting API to execute script in different contexts. To use the chrome.scripting API, declare the "scripting" permission in the manifest plus the host permissions for the pages to inject scripts into. Use the "host_permissions" key

Use the system.cpu API to query CPU metadata. string The architecture name of the processors. string[] A set of feature codes indicating some of the processor's capabilities. The currently supported codes are "mmx", "sse", "sse2", "sse3", "ssse3",

Use the chrome.fileSystemProvider API to create file systems, that can be accessible from the file manager on Chrome OS. You must declare the "fileSystemProvider" permission and section in the extension manifest to use the File System Provider API.

Use the chrome.readingList API to read from and modify the items in the Reading List. To use the Reading List API, add the "readingList" permission in the extension manifest file: manifest.json: Chrome features a reading list located on the side

Use the chrome.platformKeys API to access client certificates managed by the platform. If the user or policy grants the permission, an extension can use such a certficate in its custom authentication protocol. E.g. this allows usage of platform

Use the chrome.fileBrowserHandler API to extend the Chrome OS file browser. For example, you can use this API to enable users to upload files to your website. The ChromeOS file browser comes up when the user either presses Alt+Shift+M or connects an

Use the chrome.idle API to detect when the machine's idle state changes. You must declare the "idle" permission in your extension's manifest to use the idle API. For example: "active" "idle" "locked" Gets the time, in seconds, it takes until the

The chrome.printerProvider API exposes events used by print manager to query printers controlled by extensions, to query their capabilities and to submit print jobs to these printers. string optional Printer's human readable description. string

The chrome.types API contains type declarations for Chrome. The ChromeSetting type provides a common set of functions ( get(), set(), and clear() ) as well as an event publisher ( onChange ) for settings of the Chrome browser. The proxy

Use the chrome.accessibilityFeatures API to manage Chrome's accessibility features. This API relies on the ChromeSetting prototype of the type API for getting and setting individual accessibility features. In order to get feature states the extension

Use the chrome.contextMenus API to add items to Google Chrome's context menu. You can choose what types of objects your context menu additions apply to, such as images, hyperlinks, and pages. You must declare the "contextMenus" permission in your

The omnibox API allows you to register a keyword with Google Chrome's address bar, which is also known as the omnibox. When the user enters your extension's keyword, the user starts interacting solely with your extension. Each keystroke is sent to

The Desktop Capture API captures the content of the screen, individual windows, or individual tabs. Enum used to define set of desktop media sources used in chooseDesktopMedia(). "screen" "window" "tab" "audio" Mirrors SelfCapturePreferenceEnum.

Use the chrome.dom API to access special DOM APIs for Extensions Gets the open shadow root or the closed shadow root hosted by the specified element. If the element doesn't attach the shadow root, it will return null. HTMLElement object See

Use the chrome.i18n infrastructure to implement internationalization across your whole app or extension. You need to put all of its user-visible strings into a file named messages.json. Each time you add a new locale, you add a messages file under a

Use the chrome.history API to interact with the browser's record of visited pages. You can add, remove, and query for URLs in the browser's history. To override the history page with your own version, see Override Pages. To interact with the user's

Use the chrome.devtools.recorder API to customize the Recorder panel in DevTools. See DevTools APIs summary for general introduction to using Developer Tools APIs. devtools.recorder API is a preview feature that allows you to extend the Recorder

Use the chrome.topSites API to access the top sites (i.e. most visited sites) that are displayed on the new tab page. These do not include shortcuts customized by the user. You must declare the "topSites" permission in your extension's manifest to

Use the chrome.accessibilityFeatures API to manage Chrome's accessibility features. This API relies on the ChromeSetting prototype of the type API for getting and setting individual accessibility features. In order to get feature states the extension

Use chrome.gcm to enable apps and extensions to send and receive messages through Firebase Cloud Messaging (FCM). The maximum size (in bytes) of all key/value pairs in a message. 4096 Registers the application with FCM. The registration ID will be

Use the chrome.fontSettings API to manage Chrome's font settings. To use the Font Settings API, you must declare the "fontSettings" permission in the extension manifest. For example: Chrome allows for some font settings to depend on certain generic

Use the chrome.pageAction API to put icons in the main Google Chrome toolbar, to the right of the address bar. Page actions represent actions that can be taken on the current page, but that aren't applicable to all pages. Page actions appear grayed

Use the chrome.tabGroups API to interact with the browser's tab grouping system. You can use this API to modify and rearrange tab groups in the browser. To group and ungroup tabs, or to query what tabs are in groups, use the chrome.tabs API. The

Use the chrome.dom API to access special DOM APIs for Extensions Gets the open shadow root or the closed shadow root hosted by the specified element. If the element doesn't attach the shadow root, it will return null. HTMLElement object See

Use the chrome.search API to search via the default provider. "CURRENT_TAB" Specifies that the search results display in the calling tab or the tab from the active browser. "NEW_TAB" Specifies that the search results display in a new tab.

The chrome.system.memory API. number The amount of available capacity, in bytes. number The total amount of physical memory capacity, in bytes. Get physical memory information. function optional The callback parameter looks like: MemoryInfo

The chrome.printerProvider API exposes events used by print manager to query printers controlled by extensions, to query their capabilities and to submit print jobs to these printers. string optional Printer's human readable description. string

Use the chrome.devtools.inspectedWindow API to interact with the inspected window: obtain the tab ID for the inspected page, evaluate the code in the context of the inspected window, reload the page, or obtain the list of resources within the page.

Use the chrome.dns API for dns resolution. To use this API, you must declare the "dns" permission in the manifest. The following code calls resolve() to retrieve the IP address of example.com. service-worker.js: string optional A string representing

Use the chrome.system.storage API to query storage device information and be notified when a removable storage device is attached and detached. "success" The ejection command is successful -- the application can prompt the user to remove the device.

Use the chrome.alarms API to schedule code to run periodically or at a specified time in the future. To use the chrome.alarms API, declare the "alarms" permission in the manifest: To ensure reliable behavior, it is helpful to understand how the API

Use the chrome.search API to search via the default provider. "CURRENT_TAB" Specifies that the search results display in the calling tab or the tab from the active browser. "NEW_TAB" Specifies that the search results display in a new tab.

Use chrome.instanceID to access the Instance ID service. Resets the app instance identifier and revokes all tokens associated with it. function optional The callback parameter looks like: Promise<void> Promises are only supported for Manifest

Use chrome.instanceID to access the Instance ID service. Resets the app instance identifier and revokes all tokens associated with it. function optional The callback parameter looks like: Promise<void> Promises are supported in Manifest V3 and

Use the chrome.processes API to interact with the browser's processes. number The part of the cache that is utilized, in bytes. number The size of the cache, in bytes. number optional The most recent measurement of the process's CPU usage, expressed

Use the chrome.wallpaper API to change the ChromeOS wallpaper. You must declare the "wallpaper" permission in the app's manifest to use the wallpaper API. For example: For example, to set the wallpaper as the image at https://example.com/a_file.png,

Use the chrome.devtools.inspectedWindow API to interact with the inspected window: obtain the tab ID for the inspected page, evaluate the code in the context of the inspected window, reload the page, or obtain the list of resources within the page.

Use the chrome.contextMenus API to add items to Google Chrome's context menu. You can choose what types of objects your context menu additions apply to, such as images, hyperlinks, and pages. Context menu items can appear in any document (or frame

Use the commands API to add keyboard shortcuts that trigger actions in your extension, for example, an action to open the browser action or send a command to the extension. The following keys must be declared in the manifest to use this API. The

Use the chrome.history API to interact with the browser's record of visited pages. You can add, remove, and query for URLs in the browser's history. To override the history page with your own version, see Override Pages. You must declare the

Use the chrome.tts API to play synthesized text-to-speech (TTS). See also the related ttsEngine API, which allows an extension to implement a speech engine. Chrome provides native support for speech on Windows (using SAPI 5), Mac OS X, and ChromeOS,

Use the chrome.alarms API to schedule code to run periodically or at a specified time in the future. To use the chrome.alarms API, declare the "alarms" permission in the manifest: The following examples show how to use and respond to an alarm. To try

Use the chrome.dns API for dns resolution. To use this API, you must declare the "dns" permission in the manifest. The following code calls resolve() to retrieve the IP address of example.com. service-worker.js: string optional A string representing

The chrome.webAuthenticationProxy API lets remote desktop software running on a remote host intercept Web Authentication API (WebAuthn) requests in order to handle them on a local client. string The PublicKeyCredentialCreationOptions passed to

Use the chrome.documentScan API to discover and retrieve images from attached document scanners.

The chrome.events namespace contains common types used by APIs dispatching events to notify you when something interesting happens. An Event is an object that allows you to be notified when something interesting happens. Here's an example of using

The omnibox API allows you to register a keyword with Google Chrome's address bar, which is also known as the omnibox. When the user enters your extension's keyword, the user starts interacting solely with your extension. Each keystroke is sent to

Use the system.cpu API to query CPU metadata. string The architecture name of the processors. string[] A set of feature codes indicating some of the processor's capabilities. The currently supported codes are "mmx", "sse", "sse2", "sse3", "ssse3",

Use the chrome.power API to override the system's power management features. Using this API, you can specify the Level to which power management is disabled. The "system" level keeps the system active, but allows the screen to be dimmed or turned

Use the chrome.system.storage API to query storage device information and be notified when a removable storage device is attached and detached. "success" The ejection command is successful -- the application can prompt the user to remove the device.

Use the chrome.tabCapture API to interact with tab media streams. The chrome.tabCapture API lets you access a MediaStream containing video and audio of the current tab. It can only be called after the user invokes an extension, such as by clicking

Use the chrome.idle API to detect when the machine's idle state changes. You must declare the "idle" permission in your extension's manifest to use the idle API. For example: "active" "idle" "locked" Gets the time, in seconds, it takes until the

Use the chrome.proxy API to manage Chrome's proxy settings. This API relies on the ChromeSetting prototype of the type API for getting and setting the proxy configuration. You must declare the "proxy" permission in the extension manifest to use the

The chrome.types API contains type declarations for Chrome. The ChromeSetting prototype provides a common set of functions ( get(), set(), and clear() ) as well as an event publisher ( onChange ) for settings of the Chrome browser. The proxy

Use the chrome.fileBrowserHandler API to extend the Chrome OS file browser. For example, you can use this API to enable users to upload files to your website. The ChromeOS file browser comes up when the user either presses Alt+Shift+M or connects an

Use the chrome.devtools.recorder API to customize the Recorder panel in DevTools. devtools.recorder API is a preview feature that allows you to extend the Recorder panel in Chrome DevTools. See DevTools APIs summary for general introduction to using

Use the chrome.vpnProvider API to implement a VPN client. Typical usage of chrome.vpnProvider is as follows: Create VPN configurations by calling createConfig(). A VPN configuration is a persistent entry shown to the user in a ChromeOS UI. The user

The chrome.audio API is provided to allow users to get information about and control the audio devices attached to the system. This API is currently only available in kiosk mode for ChromeOS. string Device name. DeviceType Type of the device. string

Use the chrome.systemLog API to record Chrome system logs from extensions. string Adds a new log record. MessageOptions The logging options. function optional The callback parameter looks like: Promise<void> Promises are only supported for

Use the chrome.printingMetrics API to fetch data about printing usage. "BLACK_AND_WHITE" Specifies that black and white mode was used. "COLOR" Specifies that color mode was used. "ONE_SIDED" Specifies that one-sided printing was used.

The chrome.events namespace contains common types used by APIs dispatching events to notify you when something interesting happens. An Event is an object that lets you be notified when something interesting happens. Here's an example of using the

Use the chrome.webRequest API to observe and analyze traffic and to intercept, block, or modify requests in-flight. You must declare the "webRequest" permission in the extension manifest to use the web request API, along with the necessary host

The chrome.audio API is provided to allow users to get information about and control the audio devices attached to the system. This API is currently only available in kiosk mode for ChromeOS. string Device name. DeviceType Type of the device. string

The chrome.system.memory API. number The amount of available capacity, in bytes. number The total amount of physical memory capacity, in bytes. Get physical memory information. function optional The callback parameter looks like: MemoryInfo

Use the chrome.devtools.network API to retrieve the information about network requests displayed by the Developer Tools in the Network panel. The following keys must be declared in the manifest to use this API. See DevTools APIs summary for general

Use the chrome.topSites API to access the top sites (i.e. most visited sites) that are displayed on the new tab page. These do not include shortcuts customized by the user. You must declare the "topSites" permission in your extension's manifest to

The chrome.extensionTypes API contains type declarations for Chrome extensions. The origin of injected CSS. "author" "user" Details of the CSS to remove. Either the code or the file property must be set, but both may not be set at the same time.

The chrome.extensionTypes API contains type declarations for Chrome extensions. The origin of injected CSS. "author" "user" Details of the CSS to remove. Either the code or the file property must be set, but both may not be set at the same time.

An overview of expedited review for Declarative Net Request changes.

All the basics to get started with Chrome extensions

Reference documentation for the minimum_chrome_version property of manifest.json.

Reference documentation for the trial_tokens property of manifest.json.

An overview of the recent changes in Chrome Extensions, plus exciting upcoming extension features developers can look forward to.

This week we're excited to launch a new feature that lets developers roll back their extensions to the previous published version in the Chrome Web Store. Our goal is to give developers increased peace-of-mind when publishing updates, especially with

How to rollback an extension that you previously published on the

Extensions using Manifest V3 must meet additional requirements related to the extension's code. Specifically, the full functionality of an extension must be easily discernible from its submitted code, unless otherwise exempt as noted in Section 2.

Use the chrome.privacy API to control usage of the features in Chrome that can affect a user's privacy. This API relies on the ChromeSetting prototype of the type API for getting and setting Chrome's configuration. You must declare the "privacy"

Use the chrome.privacy API to control usage of the features in Chrome that can affect a user's privacy. This API relies on the ChromeSetting prototype of the type API for getting and setting Chrome's configuration. You must declare the "privacy"

Solve common development tasks around Chrome extensions

Use the chrome.i18n API to render your interface in multiple languages.

For many users, accessibility literally is the user interface, and its features are useful to many others.

In this post, the eyeo team shares their journey into the problem of testing extension service workers. In particular, how to to make sure that their Chrome Extensions works correctly when a service worker gets suspended.

We don't allow content that contains nudity, graphic sex acts, sexually explicit material, or content that drives traffic to commercial pornography sites. We also don't allow content that promotes incest, bestiality, necrophilia, or non-consensual

The chrome.location API is no longer supported. We recommend using open web alternatives such as the Geolocation API instead.

An extension requires at least one icon to represent it in the toolbar.

TBD

The WebUSB API, which exposes non-standard Universal Serial Bus (USB) compatible devices to the web, is available in extensions.

A guide to converting Manifest V2 extensions to Manifest V3 extensions.

The WebHID API, which exposes Human Interface Device (HID) compatible devices to the web, is available in extensions.

Reference documentation for the content security policy properties of manifest.json.

How to register as a Chrome Web Store developer.

TBD

Developer's requirement to disclose and verify their trader/non-trader status.

Samples Explore samples from the Chrome Extension samples repository. Use these to learn how extensions work or as starting points for building your own extensions. action.disable action.enable action.getBadgeBackgroundColor action.getBadgeText

Use the chrome.runtime API to retrieve the service worker, return details about the manifest, and listen for and respond to events in the extension lifecycle. You can also use this API to convert the relative path of URLs to fully-qualified URLs.

A list of permissions and user warnings available on the extensions platform.

Step by step guide on how to use Web Push with Chrome Extensions

An overview of the valid values for the permissions property in manifest.json.

How permission warnings work in Chrome extensions.

The Web Store program policies.

Respond to custom key combinations in an extension.

An overview of the recent changes in Chrome Extensions, plus exciting upcoming extension features developers can look forward to.

Trigger actions from the omnibox.

Step by step guide on how to use Firebase Messaging with chrome.gcm

Respond to a user clicking the toolbar.

Managing real-time updates in Extensions

Implement a popup, which is a window that lets users invoke extension features.

A service worker enables extensions to run only when needed, saving resources.

How to host your Chrome extension.

Implement a popup, which is a window that lets users invoke extension features.

Reference for the extensions manifest, related permissions and APIs

Manifest V3 Manifest V3 is the latest version of the extensions platform. We have made a number of changes to the available APIs and added a number of new features. Manifest V3 aims to be the first step in our platform vision to improve the privacy,

As of 06/12/2018, inline installation is deprecated. For more information, read our Chromium Blog post and Migration FAQ.

A catalog of user interface elements available in extensions.

In December of last year, we paused the planned deprecation of Manifest V2 in order to address developer feedback and deliver better solutions to migration issues. As a result of this feedback, we’ve made a number of changes to Manifest V3 to close

Over the past year, we have been actively involved in discussions with the vendors behind several content blocking extensions around ways to improve the MV3 extensions platform. Based on these discussions, many of which took place in the

A summary of important changes in Chrome 120 for Chrome Extension developers.

Reference documentation for the file_handlers property of manifest.json.

How to open files in Chrome extension service workers, popups, side panels, or content scripts.

An overview of the recent changes in Chrome Extensions, plus exciting upcoming extension features developers can look forward to.

How to set up your Chrome Web Store developer account.

Prepare your extension files.

How to write an automated test for Chrome Extensions using Puppeteer.

How to write end-to-end tests for extensions.

How to write unit tests for extensions.

Check whether a bug or feature request has already been reported.

Submit a request for a feature that you believe could improve the extension platform.

Give us feedback to help us improve the platform and fix its bugs.

How to report extension bugs or problems with documentation.

Learn how to use DevTools to debug Chrome extensions.

Overview of how web storage APIs and cookies work in extensions.

Guidance for publishing a new Manifest V3 extension

Experience and advice on participating in Google Summer of Code.

Starting in Chrome 117, Chrome will proactively highlight to users when an extension they have installed is no longer in the Chrome Web Store.

Reference documentation for the "content_scripts" property of manifest.json.

See analytics for your Chrome Web Store listing in addition to the metrics offered in the Developer Dashboard.

A summary of important changes in Chrome 116 for Chrome Extension developers.

An overview of the changes so far this year in Chrome Extensions, plus exciting upcoming extension features developers can look forward to.

Step-by-step instructions on how to connect to a WebSocket in your Chrome extension.

How to use geolocation in Chrome extension service workers, popups, side panels, or content scripts.

Introducing the new Side Panel API for Chrome extensions.

Reference documentation for the background property of manifest.json.

Extension service workers are an extension's central event handler. That makes them different from web service workers.

Extension service workers respond to both standard service worker events and many events in the extension APIs.

Extension service workers are installed and updated differently from web service workers.

Extension service workers respond to both standard service worker events and events in extension namespaces. They are presented together because often one type follows another during an extension's use.

How to record audio or video from a tab, window, or screen.

Learn how to create and debug an extension service worker.

The manifest.json file requires a slightly different format for Manifest V3 than for Manifest V2.

The second of three sections describing changes needed for code that is not part of the extension service worker.

A quick reference for upgrading your extensions from Manifest V2 to Manifest V3.

The first of three sections describing changes needed for code that is not part of the extension service worker.

A service worker enables extensions to run only when needed, saving resources.

The last of three sections describing changes needed for code that is not part of the extension service worker.

Exchange messages with native applications from your Chrome Extension.

Where to go for help with questions not covered by the documentation.

A guide explaining how to test service worker termination using Puppeteer.

Extension service workers can now stay alive as long as they're receiving events. This increases the reliability of extension services workers, but has a pitfall you should avoid.

Introducing the Offscreen Documents API for Chrome extension development.

How to get a website's favicon.

Frequently asked questions about Chrome Web Store's policies on affiliate ads.

Chrome is updating the Chrome Web Store's Developer Program Policies to clearly state our guiding principals, provide more context on enforcement, and make our policies easier to understand.

Any affiliate program must be described prominently in the product's Chrome Web Store page, user interface, and before installation. Related user action is required before the inclusion of each affiliate code, link, or cookie. Some example violations

The Extensions API has been updated to support back/forward cache, preloading navigations.

Reference documentation for the oauth2 property of manifest.json.

We do not allow products that deceive or mislead users, including in the content, title, description, or screenshots. If any of your product's content, title, icon, description, or screenshots contains false or misleading information, we may remove

If your product is associated with a security vulnerability that could be exploited to compromise another application, service, browser, or system, we may remove your product from the Chrome Web Store and take other measures to protect users. In such

Ads are considered part of your Product for purposes of content review and compliance with developer terms, and therefore must comply with the above content policies. Ads which are inconsistent with the content rating of your products or extension

Don't engage in or promote unlawful activities in your product, such as rape, illegal sex work, or the sale of prescription drugs without a prescription. We will remove content which promotes, glorifies, or encourages dangerous or illegal activity

This policy establishes the Chrome Web Store's minimum user data privacy requirements; you or your Product must comply with applicable laws. You must limit your use of the data to the practices you disclosed. Collection and use of web browsing

Request access to the narrowest permissions necessary to implement your Product's features or services. If more than one permission could be used to implement a feature, you must request those with the least access to data or functionality. Don't

The Chrome Web Store features products that align with our standards, values, and that we believe will produce valuable user experiences. Certain products that don't meet these standards, but which do not explicitly violate Chrome Web Store

Don't pretend to be someone else, and don't represent that your product is authorized by, endorsed by, or produced by another company or organization, if that is not the case. Your Product and its user experience also must not mimic functionality or

If you collect sensitive personal information through your Product for sales, you must follow these requirements: You must securely collect, store, and transmit all credit card and other sensitive personal information in accordance with privacy and

You must be transparent in how you handle user data (e.g., information provided by a user or collected about a user or a user's use of the Product or Chrome Browser), including by disclosing the collection, use, and sharing of the data. If your

We don't allow any developer, related developer accounts, or their affiliates to submit multiple extensions that provide duplicate experiences or functionality on the Chrome Web Store. Extensions should provide value to users through the creation of

To ensure a great user experience, Chrome Apps distributed through the Chrome Web Store must follow the additional quality guidelines listed below. The guidelines in this section apply only to Chrome Apps. Packaged apps should: Take advantage of the

Don't transmit viruses, worms, defects, Trojan horses, malware, or any other products of a destructive nature. We don't allow content that harms or interferes with the operation of the networks, servers, or other infrastructure of Google or any

Do not post an extension with a single purpose of installing or launching another app, theme, webpage, or extension. Extensions with broken functionality—such as dead sites or non-functioning features—are not allowed. Extensions must provide a basic

Developers must not obfuscate code or conceal functionality of their extension. This also applies to any external code or resource fetched by the extension package. Minification is allowed, including the following forms: Removal of whitespace,

Chrome is updating the Chrome Web Store's Developer Program Policies to clearly state our guiding principals, provide more context on enforcement, and make our policies easier to understand.

Extensions must use existing Chrome APIs for their designated use case. Use of any other method, for which an API exists, would be considered a violation. For example, overriding the Chrome New Tab Page through any means other than the URL Overrides

Depictions of gratuitous violence are not allowed. Products should not contain materials that threaten, harass, or bully other users. We don't allow content or products that advocating against or inciting hatred towards groups of people based on

Any attempt to circumvent intended limitations or enforcement actions will result in the immediate termination of your developer account, and possibly related developer accounts.

In the event that your Product is removed from the Chrome Web Store, you will receive an email notification to that effect, with further instructions if applicable. Verify that the associated publisher account with your Product can receive emails

If your Product handles any user data, then you must post an accurate and up to date privacy policy. The privacy policy must, together with any in-Product disclosures, comprehensively disclose: How your Product collects, uses and shares user data All

Serious or repeated violations of the Chrome Web Store Distribution Agreement or these Program Policies will result in the suspension of your developer account, and possibly related developer accounts. Additionally, you may be banned from using the

To ensure the security of Chrome Web Store accounts, 2-Step Verification is required for all developer accounts prior to publishing an extension or updating an existing extension. Developers can activate 2-Step Verification for their Google accounts

Reference documentation for the input_components property of manifest.json.

A better way to start the Chrome developer learning journey.

Learn how to automatically add new elements to existing webpages.

Learn how to programmatically organize tabs using tab groups.

Create your first Hello World Chrome extension.

Learn how to simplify the style of the current page.

Reference documentation for the author name property of manifest.json.

New details about the plan to move extensions to Manifest V3

Recently, we announced changes to the Manifest V2 deprecation timeline, and while we remain firmly committed to Manifest V3 we acknowledge there is more work to do on our part. We are committed to closing the following gaps before announcing a new

Google is rolling out a revamped item analytics experience for the Chrome Web Store Developer Dashboard. The new dashboard is easier to understand at a glance and consolidates the most useful information upfront.

An overview of how users find items on the Chrome Web Store, and how our editors select items to feature.

An overview of the review process and how enforcement actions result from detected policy violations.

Updating our security requirements and further clarifying a few policies to keep the quality of extensions high, and the experience for developers consistent.

Sharing details about the plan to move extensions to Manifest V3

Details of the Manifest V2 phase-out and end of life.

Follow-up on reviews and provide user support in the Chrome Web Store.

How to check the review status of your Chrome Web Store item.

Understanding metrics and performance of your Chrome Web Store store listing.

Reference documentation for the cross_origin_opener_policy property of manifest.json.

Reference documentation for the cross_origin_embedder_policy property of manifest.json.

Overview of cross-origin isolation for extensions

Reference documentation for the cross_origin_opener_policy property of manifest.json.

Overview of cross-origin isolation for extensions

Reference documentation for the cross_origin_embedder_policy property of manifest.json.

How to distribute extensions to enterprise users

Updating our security requirements and further clarifying a few policies to keep the quality of extensions high, and the experience for developers consistent.

Chrome extensions had Browser and Page Actions APIs for years, but Manifest V3 replaced both with a generic Actions API. This post explores the history of these APIs and what has changed in Manifest V3.

The Scripting API is a new Manifest V3 API focused on, well, scripting. Let's dig into the motivations for this change and how it's different.

Open source tool to convert extensions to Manifest V3. You'll still need to manually update any code with non-mechanical changes, such as adapting to use service workers or some script injection.

Web Accessible Resources for Manifest V3 is here! Now `manifest.json` supports permission definitions. Developers can restrict resources based on the requesting site origin or extension id.

How to choose which countries will list your item and who will see it in the Chrome Web Store.

How to add listing information for your Chrome Web Store item.

How to update an extension or theme ("item") that you previously published on the Chrome Web Store.

Guidelines for understanding why an item was rejected or removed from the Chrome Web Store and how to fix the problem.

Documentation for Chrome extensions developers.

Why the payments is deprecated, details about the deprecation timeline, and more.

How to delete a developer or group publisher account on the Chrome Web Store.

How to share ownership of your Chrome Web Store items with other developers.

Use the privacy practices tab to help the Chrome Web Store team review your extension as quickly as possible.

Frequently asked questions about Chrome Web Store's spam policy.

Guidelines for updating your Extensions to handle the runtime host permission changes starting in Chrome 70.

Frequently asked questions about the deprecation of inline installations for Chrome Extensions.

Guidelines about the kinds of images you need to supply to the Chrome Web Store.

Guidelines for use of Google trademarks.

How to migrate a persistent background script to an event-based, non-persistent model to improve the performance of your Chrome Extension.

Guidelines on how to build a high-performance Chrome Extension.

Guidelines for ensuring that your Chrome Extension protects user privacy.

Guidelines for ensuring that your Chrome Extension protects user privacy.

UI and design guidelines for Chrome Extensions.

How to keep your Chrome Extension secure.

How to keep your Chrome Extension secure.

How to package, host, and update crx files from a personal server for Linux users.

How to package, host, and update crx files from a personal server.

How to create a high-quality extension and Chrome Web store listing.

Frequently asked questions about Chrome Web Store's user data policy.

Frequently asked questions about Chrome Web Store's user data policy.

Reference documentation for the event_rules property of manifest.json.

Reference documentation for the event_rules property of manifest.json.

Media Source Extensions (MSE) provide extended buffering and playback control for the HTML5 audio and video elements. While originally developed to facilitate Dynamic Adaptive Streaming over HTTP (DASH) based video players, MSE can be used for audio; specifically for gapless playback.

An explanation of the Chrome Web Store and why you might want to use it.

How to share code between Chrome Extensions.

How to share code between Chrome Extensions.

Show notifications to Chrome Extension users.

How to show notifications to your Chrome Extension users.

Details about the hosting changes for Chrome Extensions that started in version 33 of Chrome.

How to publish a new extension or theme to the Chrome Web Store.

The legal agreement governing the relationship between Chrome Web Store developers and the Chrome Web Store.

Guidelines about how the Chrome Web Store rates the maturity of content.

Step-by-step instructions on how to create a Chrome Extension.

Frequently asked questions about Chrome Extensions.

Guidelines on how to migrate from manifest v1 to manifest v2.

Reference documentation for the chrome.location API.

How to override Chrome settings from a Chrome Extension.

How to override Chrome settings from a Chrome Extension.

Reference documentation for the storage property of manifest.json.

Reference documentation for the storage property of manifest.json.

Reference documentation for the externally_connectable property of manifest.json.

Reference documentation for the externally_connectable property of manifest.json.

Reference documentation for the name and short_name properties of manifest.json.

Reference documentation for the icons property of manifest.json.

Reference documentation for the sandbox property of manifest.json.

Reference documentation for the sandbox property of manifest.json.

Reference documentation for the nacl_modules property of manifest.json.

Reference documentation for the incognito property of manifest.json.

Reference documentation for the requirements property of manifest.json.

Reference documentation for the description property of manifest.json.

Reference documentation for the homepage_url property of manifest.json.

Reference documentation for the short_name property of manifest.json.

Reference documentation for the key property of manifest.json.

Reference documentation for the incognito property of manifest.json.

Reference documentation for the web_accessible_resources property of manifest.json.

Reference documentation for the name property of manifest.json.

Reference documentation for the web_accessible_resources property of manifest.json.

Reference documentation for the minimum_chrome_version property of manifest.json.

Reference documentation for the homepage_url property of manifest.json.

Reference documentation for the key property of manifest.json.

Reference documentation for the offline_enabled property of manifest.json.

Reference documentation for the icons property of manifest.json.

Reference documentation for the requirements property of manifest.json.

Reference documentation for the version property of manifest.json.

Reference documentation for the manifest_version property of manifest.json.

Reference documentation for the default_locale property of manifest.json.

Reference documentation for the version property of manifest.json.

Reference documentation for the default_locale property of manifest.json.

Reference documentation for the description property of manifest.json.

An overview of the purpose of Chrome Extensions and how they're developed.

An overview of the valid values for the permissions property in manifest.json.

How to use the activeTab permission in your Chrome Extension.

How to use the activeTab permission in your Chrome Extension.

Guidelines on how to create a theme.

Step-by-step instructions on how to build an extension that accesses a user's Google contacts via the Google People API, the Chrome Identity API, and OAuth2.

How to override the Chrome bookmark manager, history, and new tab pages from your Chrome Extension.

How host permission and content script pattern matching works, with examples.

Step-by-step instructions on how to debug Chrome Extensions.

Step-by-step instructions on how to track usage of your Extension with Google Analytics.

How to implement permissions to protect your users and your Extension.

Instructions for debugging Chrome Extensions.

How to use eval() in a Chrome Extension.

How to pass messages between extensions and content scripts.

A high-level explanation of the software architecture of Chrome Extensions.

How to use eval() in a Chrome Extension.

Implement cross-origin network requests in your Chrome Extension.

An overview of the manifest.json properties that you can use in your Chrome Extension.

How to let users customize your Extension.

How to pass messages between extensions and content scripts.

The manifest_version property of manifest.json indicates which version of the manifest specification a Chrome Extension targets.

Step-by-step instructions on how to track usage of your Extension with Google Analytics 4.

Step-by-step instructions on how to build an extension that accesses a user's Google contacts via the Google People API, the Chrome Identity API, and OAuth2.

How to implement cross-origin XHR in your Chrome Extension.

How to let users customize your extension.

Understanding URL match patterns in Chrome extensions.

Reference documentation about the format of the messages.json file for Chrome Extensions.

Guidelines on how to create a theme.

Reference documentation about the format of the messages.json file for Chrome Extensions.

An overview of the manifest.json properties of a Chrome Extension.

How to override the Chrome bookmark manager, history, and new tab pages from your Chrome Extension.

How to host your extension in the Chrome Web Store and update an extension that's hosted in the Chrome Web Store.

How to create a Chrome Extension that adds functionality to Chrome DevTools.

How to make your Manifest V2 Chrome Extension accessible.

How to respond to browser triggers (events) from a Chrome Extension background script.

How to install Chrome Extensions using preferences JSON or Windows registry.

How to implement notifications in your Chrome Extension.

How to make your Chrome Extension accessible.

How to distribute Chrome Extensions outside of the Chrome Web Store.

An overview of Chrome Extension capabilities and components.

An explanation of content scripts and how to use them in your Chrome Extension.

An explanation of content scripts and how to use them in your Chrome Extension.

How to create a Chrome Extension that adds features to Chrome DevTools.

Use the chrome.contentSettings API to change settings that control whether websites can use features such as cookies, JavaScript, and plugins. More generally speaking, content settings allow you to customize Chrome's behavior on a per-site basis

This permission triggers a warning. Use the chrome.bookmarks API to create, organize, and otherwise manipulate bookmarks. Also see Override Pages, which you can use to create a custom Bookmark Manager page. You must declare the "bookmarks" permission

Use the chrome.contentSettings API to change settings that control whether websites can use features such as cookies, JavaScript, and plugins. More generally speaking, content settings allow you to customize Chrome's behavior on a per-site basis

Use the chrome.bookmarks API to create, organize, and otherwise manipulate bookmarks. Also see Override Pages, which you can use to create a custom Bookmark Manager page. You must declare the "bookmarks" permission in the extension manifest to use

Samples for Chrome Extensions are available on GitHub.

In connection with the Google Chrome Web Store, Google may make certain Chrome Web Store applications available in Google's Play for Education site. If You or Your organization is interested in participating, please verify that the

The Chrome Web Store is committed to fostering a high-quality and trustworthy ecosystem for developers and users. To align with this goal, we're announcing a series of policy updates designed to provide clarity and consistency across our platform.

This reference describes the methods and resource representation available for the Chrome Web Store Publish API. Each resource type has one or more data representations and one or more methods. See Using the Chrome Web Store Publish API for a guide

How to programmatically create, update, and publish items in the Chrome Web Store.

TODO

Extension policies

Use the chrome.sessions API to query and restore tabs and windows from a browsing session. string The name of the foreign device. Session [] A list of open window sessions for the foreign device, sorted from most recently to least recently modified

Use the chrome.printing API to send print jobs to printers installed on Chromebook. All chrome.printing methods and events require you to declare the "printing" permission in the extension manifest. For example: The examples below demonstrate using

Use the userScripts API to execute user scripts in the User Scripts context. To use the User Scripts API, chrome.userScripts, add the "userScripts" permission to your manifest.json and "host_permissions" for sites you want to run scripts on. A user

Use the chrome.sessions API to query and restore tabs and windows from a browsing session. string The name of the foreign device. Session [] A list of open window sessions for the foreign device, sorted from most recently to least recently modified

Use the chrome.printing API to send print jobs to printers installed on Chromebook. All chrome.printing methods and events require you to declare the "printing" permission in the extension manifest. For example: The examples below demonstrate using

Learn how to develop extensions with AI

Learn how to develop Chrome extensions.

Use the chrome.i18n infrastructure to implement internationalization across your whole app or extension. If an extension has a /_locales directory, the manifest must define "default_locale". You need to put all of its user-visible strings into a file

Use the chrome.storage API to store, retrieve, and track changes to user data. The Storage API provides an extension-specific way to persist user data and state. It's similar to the web platform's storage APIs ( IndexedDB, and Storage ), but was

Use the chrome.storage API to store, retrieve, and track changes to user data. To use the storage API, declare the "storage" permission in the extension manifest. For example: The Storage API provides an extension-specific way to persist user data

Use the chrome.enterprise.platformKeys API to generate keys and install certificates for these keys. The certificates will be managed by the platform and can be used for TLS authentication, network access or by other extension through

Use the chrome.enterprise.platformKeys API to generate keys and install certificates for these keys. The certificates will be managed by the platform and can be used for TLS authentication, network access or by other extension through

Use the chrome.permissions API to request declared optional permissions at run time rather than install time, so users understand why the permissions are needed and grant only those that are necessary. Permission warnings exist to describe the

Use the chrome.permissions API to request declared optional permissions at run time rather than install time, so users understand why the permissions are needed and grant only those that are necessary. Permission warnings exist to describe the

Use the chrome.runtime API to retrieve the service worker, return details about the manifest, and listen for and respond to events in the extension lifecycle. You can also use this API to convert the relative path of URLs to fully-qualified URLs. The

An overview of the recent changes in Chrome Extensions, plus exciting upcoming extensions features developers can look forward to.

Use the chrome.tabs API to interact with the browser's tab system. You can use this API to create, modify, and rearrange tabs in the browser. The Tabs API not only offers features for manipulating and managing tabs, but can also detect the language

Use the chrome.tabs API to interact with the browser's tab system. You can use this API to create, modify, and rearrange tabs in the browser. The Tabs API not only offers features for manipulating and managing tabs, but can also detect the language

Use the chrome.ttsEngine API to implement a text-to-speech(TTS) engine using an extension. If your extension registers using this API, it will receive events containing an utterance to be spoken and other parameters when any extension or Chrome App

Use the chrome.cookies API to query and modify cookies, and to be notified when they change. To use the cookies API, you must declare the "cookies" permission in your manifest, along with host permissions for any hosts whose cookies you want to

Use the chrome.cookies API to query and modify cookies, and to be notified when they change. To use the cookies API, declare the "cookies" permission in your manifest along with host permissions for any hosts whose cookies you want to access. For

Use the chrome.ttsEngine API to implement a text-to-speech(TTS) engine using an extension. If your extension registers using this API, it will receive events containing an utterance to be spoken and other parameters when any extension or Chrome App

Recent changes to the Chrome extensions platform, documentation, and policy

Use the chrome.pageCapture API to save a tab as MHTML. MHTML is a standard format supported by most browsers. It encapsulates in a single file a page and all its resources (CSS files, images..). Note that for security reasons a MHTML file can only be

Use the chrome.pageCapture API to save a tab as MHTML. MHTML is a standard format supported by most browsers. It encapsulates in a single file a page and all its resources (CSS files, images..). Note that for security reasons a MHTML file can only be

Chrome Web Store An online marketplace where users can browse for extensions and themes. Publish your extension there and make it accessible to the world. dashboard Developer Dashboard Publish your extension and manage your store items. local_mall

Use the chrome.action API to control the extension's icon in the Google Chrome toolbar. The following keys must be declared in the manifest to use this API. To use the chrome.action API, specify a "manifest_version" of 3 and include the "action" key

Use this API to expose certificates to the platform which can use these certificates for TLS authentications. Typical usage of this API to expose client certificates to ChromeOS follows these steps: The actual sequence of steps can be different. For

The complete reference to all APIs made available to Chrome Extensions. This includes APIs for the deprecated Chrome Apps platform as well as APIs still in beta and dev.

The chrome.extension API has utilities that can be used by any extension page. It includes support for exchanging messages between an extension and its content scripts or between extensions, as described in detail in Message Passing. The type of

The chrome.extension API has utilities that can be used by any extension page. It includes support for exchanging messages between an extension and its content scripts or between extensions, as described in detail in Message Passing. The type of

Use the chrome.declarativeContent API to take actions depending on the content of a page, without requiring permission to read the page's content. The Declarative Content API lets you enable your extension's action depending on the URL of a web page,

Note: this API is deprecated. Check out the declarativeNetRequest API instead. Use the chrome.declarativeWebRequest API to intercept, block, or modify requests in-flight. It is significantly faster than the chrome.webRequest API because you can

Use the chrome.declarativeContent API to take actions depending on the content of a page, without requiring permission to read the page's content. The Declarative Content API allows you to enable your extension's action depending on the URL of a web

Use this API to expose certificates to the platform which can use these certificates for TLS authentications. Typical usage of this API to expose client certificates to ChromeOS follows these steps: The actual sequence of steps can be different. For

Use the commands API to add keyboard shortcuts that trigger actions in your extension, for example, an action to open the browser action or send a command to the extension. The following keys must be declared in the manifest to use this API. The

Use the offscreen API to create and manage offscreen documents. To use the Offscreen API, declare the "offscreen" permission in the extension manifest. For example: Service workers don't have DOM access, and many websites have content security

Use the system.display API to query display metadata. An enum to tell if the display is detected and used by the system. The display is considered 'inactive', if it is not detected by the system (maybe disconnected, or considered disconnected due to

Use the system.display API to query display metadata. An enum to tell if the display is detected and used by the system. The display is considered 'inactive', if it is not detected by the system (maybe disconnected, or considered disconnected due to

How to prepare your extension for the new extensions menu.

The chrome.debugger API serves as an alternate transport for Chrome's remote debugging protocol. Use chrome.debugger to attach to one or more tabs to instrument network interaction, debug JavaScript, mutate the DOM and CSS, and more. Use the Debuggee

Use the chrome.wallpaper API to change the ChromeOS wallpaper. You must declare the "wallpaper" permission in the app's manifest to use the wallpaper API. For example: For example, to set the wallpaper as the image at https://example.com/a_file.png,

Use the chrome.processes API to interact with the browser's processes. number The part of the cache that is utilized, in bytes. number The size of the cache, in bytes. number optional The most recent measurement of the process's CPU usage, expressed

Use the chrome.tts API to play synthesized text-to-speech (TTS). See also the related ttsEngine API, which allows an extension to implement a speech engine. Chrome provides this capability on Windows (using SAPI 5), Mac OS X, and ChromeOS,

The chrome.management API provides ways to manage installed apps and extensions. You must declare the "management" permission in the extension manifest to use the management API. For example: management.getPermissionWarningsByManifest,

The chrome.management API provides ways to manage installed apps and extensions. You must declare the "management" permission in the extension manifest to use the management API. For example: management.getPermissionWarningsByManifest(),

The chrome.declarativeNetRequest API is used to block or modify network requests by specifying declarative rules. This lets extensions modify network requests without intercepting them and viewing their content, thus providing more privacy. The "

Use the chrome.browsingData API to remove browsing data from a user's local profile. You must declare the "browsingData" permission in the extension manifest to use this API. The simplest use-case for this API is a a time-based mechanism for clearing

Use chrome.gcm to enable apps and extensions to send and receive messages through Firebase Cloud Messaging (FCM). The maximum size (in bytes) of all key/value pairs in a message. 4096 Registers the application with FCM. The registration ID will be

Use the chrome.identity API to get OAuth2 access tokens. string A unique identifier for the account. This ID will not change for the lifetime of the account. "SYNC" Specifies that Sync is enabled for the primary account. "ANY" Specifies the existence

Use the chrome.windows API to interact with browser windows. You can use this API to create, modify, and rearrange windows in the browser. When requested, a windows.Window contains an array of tabs.Tab objects. You must declare the "tabs" permission

Use browser actions to put icons in the main Google Chrome toolbar, to the right of the address bar. In addition to its icon, a browser action can have a tooltip, a badge, and a popup. In the following figure, the multicolored square to the right of

Use the chrome.identity API to get OAuth2 access tokens. string A unique identifier for the account. This ID will not change for the lifetime of the account. "SYNC" Specifies that Sync is enabled for the primary account. "ANY" Specifies the existence

Use the chrome.webNavigation API to receive notifications about the status of navigation requests in-flight. All chrome.webNavigation methods and events require you to declare the "webNavigation" permission in the extension manifest. For example: For

Use the chrome.enterprise.hardwarePlatform API to get the manufacturer and model of the hardware platform where the browser runs. Note: This API is only available to extensions installed by enterprise policy. string string Obtains the manufacturer

Use the chrome.vpnProvider API to implement a VPN client. Typical usage of vpnProvider is as follows: Create VPN configurations using the createConfig method. A VPN configuration is a persistent entry shown to the user in a native ChromeOS UI. The

Use the chrome.systemLog API to record Chrome system logs from extensions. string Adds a new log record. MessageOptions The logging options. function optional The callback parameter looks like: Promise<void> Promises are supported in Manifest

Use the chrome.notifications API to create rich notifications using templates and show these notifications to users in the system tray. string optional Button icons not visible for Mac OS X users. string string Additional details about this item.

Use the chrome.loginState API to read and monitor the login state. "SIGNIN_PROFILE" Specifies that the extension is in the signin profile. "USER_PROFILE" Specifies that the extension is in the user profile. "UNKNOWN" Specifies that the session state

Use the chrome.input.ime API to implement a custom IME for Chrome OS. This allows your extension to handle keystrokes, set the composition, and manage the candidate window. You must declare the "input" permission in the extension manifest to use the

The Desktop Capture API captures the content of the screen, individual windows, or individual tabs. Enum used to define set of desktop media sources used in chooseDesktopMedia(). "screen" "window" "tab" "audio" Mirrors SelfCapturePreferenceEnum.

Use the chrome.fileSystemProvider API to create file systems, that can be accessible from the file manager on Chrome OS. You must declare the "fileSystemProvider" permission and section in the extension manifest to use the File System Provider API.

This permission triggers a warning Use the chrome.downloads API to programmatically initiate, monitor, manipulate, and search for downloads. You must declare the "downloads" permission in the extension manifest to use this API. You can find simple

Use the chrome.downloads API to programmatically initiate, monitor, manipulate, and search for downloads. You must declare the "downloads" permission in the extension manifest to use this API. You can find simple examples of using the

Use the chrome.sidePanel API to host content in the browser's side panel alongside the main content of a webpage. To use the Side Panel API, add the "sidePanel" permission in the extension manifest file: manifest.json: The Side Panel API allows

Use the chrome.enterprise.deviceAttributes API to read device attributes. Note: This API is only available to extensions force-installed by enterprise policy. Fetches the administrator-annotated Location. If the current user is not affiliated or no

Use the chrome.power API to override the system's power management features. Using this API, you can specify the Level to which power management is disabled. The "system" level keeps the system active, but allows the screen to be dimmed or turned

Use the chrome.webNavigation API to receive notifications about the status of navigation requests in-flight. All chrome.webNavigation methods and events require you to declare the "webNavigation" permission in the extension manifest. For example: For

Use the chrome.tabCapture API to interact with tab media streams. The chrome.tabCapture API allows you to access a MediaStream containing video and audio of the current tab. It can only be called after the user invokes an extension, such as

Use the chrome.devtools.panels API to integrate your extension into Developer Tools window UI: create your own panels, access existing panels, and add sidebars. The following keys must be declared in the manifest to use this API. See DevTools APIs

Use the chrome.platformKeys API to access client certificates managed by the platform. If the user or policy grants the permission, an extension can use such a certficate in its custom authentication protocol. E.g. this allows usage of platform

Use the chrome.printingMetrics API to fetch data about printing usage. "BLACK_AND_WHITE" Specifies that black and white mode was used. "COLOR" Specifies that color mode was used. "ONE_SIDED" Specifies that one-sided printing was used.

The complete reference to all APIs made available to Chrome Extensions. This includes APIs for the deprecated Chrome Apps platform as well as APIs still in beta and dev.

Use the chrome.notifications API to create rich notifications using templates and show these notifications to users in the system tray. string optional Button icons not visible for Mac OS X users. string string Additional details about this item.

Use the chrome.windows API to interact with browser windows. You can use this API to create, modify, and rearrange windows in the browser. When requested, a windows.Window contains an array of tabs.Tab objects. You must declare the "tabs" permission

The chrome.debugger API serves as an alternate transport for Chrome's remote debugging protocol. Use chrome.debugger to attach to one or more tabs to instrument network interaction, debug JavaScript, mutate the DOM and CSS, and more. Use the Debuggee

Use the chrome.documentScan API to discover and retrieve images from attached document scanners. The Document Scan API is designed to allow apps and extensions to view the content of paper documents on an attached document scanner. string Provides

Use the chrome.fontSettings API to manage Chrome's font settings. To use the Font Settings API, you must declare the "fontSettings" permission in the extension manifest. For example: Chrome allows for some font settings to depend on certain generic

Use the chrome.browsingData API to remove browsing data from a user's local profile. You must declare the "browsingData" permission in the extension manifest to use this API. The simplest use-case for this API is a a time-based mechanism for clearing

Use the chrome.webRequest API to observe and analyze traffic and to intercept, block, or modify requests in-flight. You must declare the "webRequest" permission in the extension manifest to use the web request API, along with the necessary host

An overview of the recent changes in Chrome Extensions, plus exciting upcoming extensions features developers can look forward to.

We're excited to launch a set of UI changes making the Chrome Web Store Developer Dashboard more responsive and mobile-friendly. We hope this gives you a more convenient and accessible experience when monitoring store listing performance, making

The chrome.declarativeNetRequest API is used to block or modify network requests by specifying declarative rules. This lets extensions modify network requests without intercepting them and viewing their content, thus providing more privacy.

Use the chrome.devtools.performance API to listen to recording status updates in the Performance panel in DevTools. See DevTools APIs summary for general introduction to using Developer Tools APIs. The chrome.devtools.performance API allows

Use the chrome.devtools.network API to retrieve the information about network requests displayed by the Developer Tools in the Network panel. Network requests information is represented in the HTTP Archive format ( HAR ). The description of HAR is

Use the chrome.devtools.panels API to integrate your extension into Developer Tools window UI: create your own panels, access existing panels, and add sidebars. Each extension panel and sidebar is displayed as a separate HTML page. All extension

Best practices on how to make a high-quality, engaging listing page for your item in the Chrome Web Store.

An extension must have a single purpose that is narrow and easy to understand. Don't create an extension that requires users to accept bundles of unrelated functionality. If two pieces of functionality are clearly separate, they should be put into

Research and understand the Chrome Web Store policies. Before developing a Chrome extension, it is important to review the Chrome Web Store Developer Program Policies and ensure your extension complies with all guidelines and requirements. Extensions

Extensions must be marketed responsibly. The set of functionalities promised by the extension must be stated clearly and in a transparent manner. The outcome of any user interaction should match the reasonable expectations that were set with the

An overview of the recent changes in Chrome Extensions, plus exciting upcoming extension features developers can look forward to.

If your product has a blank description field or is missing an icon or screenshots, it will be rejected. Ensure your product's listing information is up to date, accurate, and comprehensive. We don't allow extensions with misleading, inaccurate,

This announcement includes a series of updates to Developer Program Policies page designed to encourage the development of high quality products, prevent deceptive behavior, and ensure informed user consent.

Frequently asked questions about Chrome Web Store's policies on deceptive installation tactics.

Frequently asked questions about the single purpose policy.

Use the chrome.input.ime API to implement a custom IME for Chrome OS. This allows your extension to handle keystrokes, set the composition, and manage the candidate window. You must declare the "input" permission in the extension manifest to use the

YouTube is enhancing platform security with Trusted Types to prevent cross-site scripting attacks, but it may impact your extension.

Use the chrome.enterprise.deviceAttributes API to read device attributes. Note: This API is only available to extensions force-installed by enterprise policy. Fetches the administrator-annotated Location. If the current user is not affiliated or no

Use the chrome.enterprise.hardwarePlatform API to get the manufacturer and model of the hardware platform where the browser runs. Note: This API is only available to extensions installed by enterprise policy. string string Obtains the manufacturer

Use the chrome.enterprise.networkingAttributes API to read information about your current network. Note: This API is only available to extensions force-installed by enterprise policy. string optional The device's local IPv4 address (undefined if not

Use the chrome.enterprise.networkingAttributes API to read information about your current network. Note: This API is only available to extensions force-installed by enterprise policy. string optional The device's local IPv4 address (undefined if not

We sat down with the team that leads review in the Chrome Web Store.

Learn how to develop extensions

An explanation of content filtering and how to approach it in your Chrome Extension.

Use the chrome.proxy API to manage Chrome's proxy settings. This API relies on the ChromeSetting prototype of the type API for getting and setting the proxy configuration. You must declare the "proxy" permission in the extension manifest to use the

Use the chrome.loginState API to read and monitor the login state. "SIGNIN_PROFILE" Specifies that the extension is in the signin profile. "USER_PROFILE" Specifies that the extension is in the user profile. "UNKNOWN" Specifies that the session state

Use the chrome.scripting API to execute script in different contexts. To use the chrome.scripting API, declare the "scripting" permission in the manifest plus the host permissions for the pages to inject scripts into. Use the "host_permissions" key

Use the system.cpu API to query CPU metadata. string The architecture name of the processors. string[] A set of feature codes indicating some of the processor's capabilities. The currently supported codes are "mmx", "sse", "sse2", "sse3", "ssse3",

Use the chrome.fileSystemProvider API to create file systems, that can be accessible from the file manager on Chrome OS. You must declare the "fileSystemProvider" permission and section in the extension manifest to use the File System Provider API.

Use the chrome.readingList API to read from and modify the items in the Reading List. To use the Reading List API, add the "readingList" permission in the extension manifest file: manifest.json: Chrome features a reading list located on the side

Use the chrome.platformKeys API to access client certificates managed by the platform. If the user or policy grants the permission, an extension can use such a certficate in its custom authentication protocol. E.g. this allows usage of platform

Use the chrome.fileBrowserHandler API to extend the Chrome OS file browser. For example, you can use this API to enable users to upload files to your website. The ChromeOS file browser comes up when the user either presses Alt+Shift+M or connects an

Use the chrome.idle API to detect when the machine's idle state changes. You must declare the "idle" permission in your extension's manifest to use the idle API. For example: "active" "idle" "locked" Gets the time, in seconds, it takes until the

The chrome.printerProvider API exposes events used by print manager to query printers controlled by extensions, to query their capabilities and to submit print jobs to these printers. string optional Printer's human readable description. string

The chrome.types API contains type declarations for Chrome. The ChromeSetting type provides a common set of functions ( get(), set(), and clear() ) as well as an event publisher ( onChange ) for settings of the Chrome browser. The proxy

Use the chrome.accessibilityFeatures API to manage Chrome's accessibility features. This API relies on the ChromeSetting prototype of the type API for getting and setting individual accessibility features. In order to get feature states the extension

Use the chrome.contextMenus API to add items to Google Chrome's context menu. You can choose what types of objects your context menu additions apply to, such as images, hyperlinks, and pages. You must declare the "contextMenus" permission in your

The omnibox API allows you to register a keyword with Google Chrome's address bar, which is also known as the omnibox. When the user enters your extension's keyword, the user starts interacting solely with your extension. Each keystroke is sent to

The Desktop Capture API captures the content of the screen, individual windows, or individual tabs. Enum used to define set of desktop media sources used in chooseDesktopMedia(). "screen" "window" "tab" "audio" Mirrors SelfCapturePreferenceEnum.

Use the chrome.dom API to access special DOM APIs for Extensions Gets the open shadow root or the closed shadow root hosted by the specified element. If the element doesn't attach the shadow root, it will return null. HTMLElement object See

Use the chrome.i18n infrastructure to implement internationalization across your whole app or extension. You need to put all of its user-visible strings into a file named messages.json. Each time you add a new locale, you add a messages file under a

Use the chrome.history API to interact with the browser's record of visited pages. You can add, remove, and query for URLs in the browser's history. To override the history page with your own version, see Override Pages. To interact with the user's

Use the chrome.devtools.recorder API to customize the Recorder panel in DevTools. See DevTools APIs summary for general introduction to using Developer Tools APIs. devtools.recorder API is a preview feature that allows you to extend the Recorder

Use the chrome.topSites API to access the top sites (i.e. most visited sites) that are displayed on the new tab page. These do not include shortcuts customized by the user. You must declare the "topSites" permission in your extension's manifest to

Use the chrome.accessibilityFeatures API to manage Chrome's accessibility features. This API relies on the ChromeSetting prototype of the type API for getting and setting individual accessibility features. In order to get feature states the extension

Use chrome.gcm to enable apps and extensions to send and receive messages through Firebase Cloud Messaging (FCM). The maximum size (in bytes) of all key/value pairs in a message. 4096 Registers the application with FCM. The registration ID will be

Use the chrome.fontSettings API to manage Chrome's font settings. To use the Font Settings API, you must declare the "fontSettings" permission in the extension manifest. For example: Chrome allows for some font settings to depend on certain generic

Use the chrome.pageAction API to put icons in the main Google Chrome toolbar, to the right of the address bar. Page actions represent actions that can be taken on the current page, but that aren't applicable to all pages. Page actions appear grayed

Use the chrome.tabGroups API to interact with the browser's tab grouping system. You can use this API to modify and rearrange tab groups in the browser. To group and ungroup tabs, or to query what tabs are in groups, use the chrome.tabs API. The

Use the chrome.dom API to access special DOM APIs for Extensions Gets the open shadow root or the closed shadow root hosted by the specified element. If the element doesn't attach the shadow root, it will return null. HTMLElement object See

Use the chrome.search API to search via the default provider. "CURRENT_TAB" Specifies that the search results display in the calling tab or the tab from the active browser. "NEW_TAB" Specifies that the search results display in a new tab.

The chrome.system.memory API. number The amount of available capacity, in bytes. number The total amount of physical memory capacity, in bytes. Get physical memory information. function optional The callback parameter looks like: MemoryInfo

The chrome.printerProvider API exposes events used by print manager to query printers controlled by extensions, to query their capabilities and to submit print jobs to these printers. string optional Printer's human readable description. string

Use the chrome.devtools.inspectedWindow API to interact with the inspected window: obtain the tab ID for the inspected page, evaluate the code in the context of the inspected window, reload the page, or obtain the list of resources within the page.

Use the chrome.dns API for dns resolution. To use this API, you must declare the "dns" permission in the manifest. The following code calls resolve() to retrieve the IP address of example.com. service-worker.js: string optional A string representing

Use the chrome.system.storage API to query storage device information and be notified when a removable storage device is attached and detached. "success" The ejection command is successful -- the application can prompt the user to remove the device.

Use the chrome.alarms API to schedule code to run periodically or at a specified time in the future. To use the chrome.alarms API, declare the "alarms" permission in the manifest: To ensure reliable behavior, it is helpful to understand how the API

Use the chrome.search API to search via the default provider. "CURRENT_TAB" Specifies that the search results display in the calling tab or the tab from the active browser. "NEW_TAB" Specifies that the search results display in a new tab.

Use chrome.instanceID to access the Instance ID service. Resets the app instance identifier and revokes all tokens associated with it. function optional The callback parameter looks like: Promise<void> Promises are only supported for Manifest

Use chrome.instanceID to access the Instance ID service. Resets the app instance identifier and revokes all tokens associated with it. function optional The callback parameter looks like: Promise<void> Promises are supported in Manifest V3 and

Use the chrome.processes API to interact with the browser's processes. number The part of the cache that is utilized, in bytes. number The size of the cache, in bytes. number optional The most recent measurement of the process's CPU usage, expressed

Use the chrome.wallpaper API to change the ChromeOS wallpaper. You must declare the "wallpaper" permission in the app's manifest to use the wallpaper API. For example: For example, to set the wallpaper as the image at https://example.com/a_file.png,

Use the chrome.devtools.inspectedWindow API to interact with the inspected window: obtain the tab ID for the inspected page, evaluate the code in the context of the inspected window, reload the page, or obtain the list of resources within the page.

Use the chrome.contextMenus API to add items to Google Chrome's context menu. You can choose what types of objects your context menu additions apply to, such as images, hyperlinks, and pages. Context menu items can appear in any document (or frame

Use the commands API to add keyboard shortcuts that trigger actions in your extension, for example, an action to open the browser action or send a command to the extension. The following keys must be declared in the manifest to use this API. The

Use the chrome.history API to interact with the browser's record of visited pages. You can add, remove, and query for URLs in the browser's history. To override the history page with your own version, see Override Pages. You must declare the

Use the chrome.tts API to play synthesized text-to-speech (TTS). See also the related ttsEngine API, which allows an extension to implement a speech engine. Chrome provides native support for speech on Windows (using SAPI 5), Mac OS X, and ChromeOS,

Use the chrome.alarms API to schedule code to run periodically or at a specified time in the future. To use the chrome.alarms API, declare the "alarms" permission in the manifest: The following examples show how to use and respond to an alarm. To try

Use the chrome.dns API for dns resolution. To use this API, you must declare the "dns" permission in the manifest. The following code calls resolve() to retrieve the IP address of example.com. service-worker.js: string optional A string representing

The chrome.webAuthenticationProxy API lets remote desktop software running on a remote host intercept Web Authentication API (WebAuthn) requests in order to handle them on a local client. string The PublicKeyCredentialCreationOptions passed to

Use the chrome.documentScan API to discover and retrieve images from attached document scanners.

The chrome.events namespace contains common types used by APIs dispatching events to notify you when something interesting happens. An Event is an object that allows you to be notified when something interesting happens. Here's an example of using

The omnibox API allows you to register a keyword with Google Chrome's address bar, which is also known as the omnibox. When the user enters your extension's keyword, the user starts interacting solely with your extension. Each keystroke is sent to

Use the system.cpu API to query CPU metadata. string The architecture name of the processors. string[] A set of feature codes indicating some of the processor's capabilities. The currently supported codes are "mmx", "sse", "sse2", "sse3", "ssse3",

Use the chrome.power API to override the system's power management features. Using this API, you can specify the Level to which power management is disabled. The "system" level keeps the system active, but allows the screen to be dimmed or turned

Use the chrome.system.storage API to query storage device information and be notified when a removable storage device is attached and detached. "success" The ejection command is successful -- the application can prompt the user to remove the device.

Use the chrome.tabCapture API to interact with tab media streams. The chrome.tabCapture API lets you access a MediaStream containing video and audio of the current tab. It can only be called after the user invokes an extension, such as by clicking

Use the chrome.idle API to detect when the machine's idle state changes. You must declare the "idle" permission in your extension's manifest to use the idle API. For example: "active" "idle" "locked" Gets the time, in seconds, it takes until the

Use the chrome.proxy API to manage Chrome's proxy settings. This API relies on the ChromeSetting prototype of the type API for getting and setting the proxy configuration. You must declare the "proxy" permission in the extension manifest to use the

The chrome.types API contains type declarations for Chrome. The ChromeSetting prototype provides a common set of functions ( get(), set(), and clear() ) as well as an event publisher ( onChange ) for settings of the Chrome browser. The proxy

Use the chrome.fileBrowserHandler API to extend the Chrome OS file browser. For example, you can use this API to enable users to upload files to your website. The ChromeOS file browser comes up when the user either presses Alt+Shift+M or connects an

Use the chrome.devtools.recorder API to customize the Recorder panel in DevTools. devtools.recorder API is a preview feature that allows you to extend the Recorder panel in Chrome DevTools. See DevTools APIs summary for general introduction to using

Use the chrome.vpnProvider API to implement a VPN client. Typical usage of chrome.vpnProvider is as follows: Create VPN configurations by calling createConfig(). A VPN configuration is a persistent entry shown to the user in a ChromeOS UI. The user

The chrome.audio API is provided to allow users to get information about and control the audio devices attached to the system. This API is currently only available in kiosk mode for ChromeOS. string Device name. DeviceType Type of the device. string

Use the chrome.systemLog API to record Chrome system logs from extensions. string Adds a new log record. MessageOptions The logging options. function optional The callback parameter looks like: Promise<void> Promises are only supported for

Use the chrome.printingMetrics API to fetch data about printing usage. "BLACK_AND_WHITE" Specifies that black and white mode was used. "COLOR" Specifies that color mode was used. "ONE_SIDED" Specifies that one-sided printing was used.

The chrome.events namespace contains common types used by APIs dispatching events to notify you when something interesting happens. An Event is an object that lets you be notified when something interesting happens. Here's an example of using the

Use the chrome.webRequest API to observe and analyze traffic and to intercept, block, or modify requests in-flight. You must declare the "webRequest" permission in the extension manifest to use the web request API, along with the necessary host

The chrome.audio API is provided to allow users to get information about and control the audio devices attached to the system. This API is currently only available in kiosk mode for ChromeOS. string Device name. DeviceType Type of the device. string

The chrome.system.memory API. number The amount of available capacity, in bytes. number The total amount of physical memory capacity, in bytes. Get physical memory information. function optional The callback parameter looks like: MemoryInfo

Use the chrome.devtools.network API to retrieve the information about network requests displayed by the Developer Tools in the Network panel. The following keys must be declared in the manifest to use this API. See DevTools APIs summary for general

Use the chrome.topSites API to access the top sites (i.e. most visited sites) that are displayed on the new tab page. These do not include shortcuts customized by the user. You must declare the "topSites" permission in your extension's manifest to

The chrome.extensionTypes API contains type declarations for Chrome extensions. The origin of injected CSS. "author" "user" Details of the CSS to remove. Either the code or the file property must be set, but both may not be set at the same time.

The chrome.extensionTypes API contains type declarations for Chrome extensions. The origin of injected CSS. "author" "user" Details of the CSS to remove. Either the code or the file property must be set, but both may not be set at the same time.

An overview of expedited review for Declarative Net Request changes.

All the basics to get started with Chrome extensions

Reference documentation for the minimum_chrome_version property of manifest.json.

Reference documentation for the trial_tokens property of manifest.json.

An overview of the recent changes in Chrome Extensions, plus exciting upcoming extension features developers can look forward to.

This week we're excited to launch a new feature that lets developers roll back their extensions to the previous published version in the Chrome Web Store. Our goal is to give developers increased peace-of-mind when publishing updates, especially with

How to rollback an extension that you previously published on the

Extensions using Manifest V3 must meet additional requirements related to the extension's code. Specifically, the full functionality of an extension must be easily discernible from its submitted code, unless otherwise exempt as noted in Section 2.

Use the chrome.privacy API to control usage of the features in Chrome that can affect a user's privacy. This API relies on the ChromeSetting prototype of the type API for getting and setting Chrome's configuration. You must declare the "privacy"

Use the chrome.privacy API to control usage of the features in Chrome that can affect a user's privacy. This API relies on the ChromeSetting prototype of the type API for getting and setting Chrome's configuration. You must declare the "privacy"

Solve common development tasks around Chrome extensions

Use the chrome.i18n API to render your interface in multiple languages.

For many users, accessibility literally is the user interface, and its features are useful to many others.

In this post, the eyeo team shares their journey into the problem of testing extension service workers. In particular, how to to make sure that their Chrome Extensions works correctly when a service worker gets suspended.

We don't allow content that contains nudity, graphic sex acts, sexually explicit material, or content that drives traffic to commercial pornography sites. We also don't allow content that promotes incest, bestiality, necrophilia, or non-consensual

The chrome.location API is no longer supported. We recommend using open web alternatives such as the Geolocation API instead.

An extension requires at least one icon to represent it in the toolbar.

TBD

The WebUSB API, which exposes non-standard Universal Serial Bus (USB) compatible devices to the web, is available in extensions.

A guide to converting Manifest V2 extensions to Manifest V3 extensions.

The WebHID API, which exposes Human Interface Device (HID) compatible devices to the web, is available in extensions.

Reference documentation for the content security policy properties of manifest.json.

How to register as a Chrome Web Store developer.

TBD

Developer's requirement to disclose and verify their trader/non-trader status.

Samples Explore samples from the Chrome Extension samples repository. Use these to learn how extensions work or as starting points for building your own extensions. action.disable action.enable action.getBadgeBackgroundColor action.getBadgeText

Use the chrome.runtime API to retrieve the service worker, return details about the manifest, and listen for and respond to events in the extension lifecycle. You can also use this API to convert the relative path of URLs to fully-qualified URLs.

A list of permissions and user warnings available on the extensions platform.

Step by step guide on how to use Web Push with Chrome Extensions

An overview of the valid values for the permissions property in manifest.json.

How permission warnings work in Chrome extensions.

The Web Store program policies.

Respond to custom key combinations in an extension.

An overview of the recent changes in Chrome Extensions, plus exciting upcoming extension features developers can look forward to.

Trigger actions from the omnibox.

Step by step guide on how to use Firebase Messaging with chrome.gcm

Respond to a user clicking the toolbar.

Managing real-time updates in Extensions

Implement a popup, which is a window that lets users invoke extension features.

A service worker enables extensions to run only when needed, saving resources.

How to host your Chrome extension.

Implement a popup, which is a window that lets users invoke extension features.

Reference for the extensions manifest, related permissions and APIs

Manifest V3 Manifest V3 is the latest version of the extensions platform. We have made a number of changes to the available APIs and added a number of new features. Manifest V3 aims to be the first step in our platform vision to improve the privacy,

As of 06/12/2018, inline installation is deprecated. For more information, read our Chromium Blog post and Migration FAQ.

A catalog of user interface elements available in extensions.

In December of last year, we paused the planned deprecation of Manifest V2 in order to address developer feedback and deliver better solutions to migration issues. As a result of this feedback, we’ve made a number of changes to Manifest V3 to close

Over the past year, we have been actively involved in discussions with the vendors behind several content blocking extensions around ways to improve the MV3 extensions platform. Based on these discussions, many of which took place in the

A summary of important changes in Chrome 120 for Chrome Extension developers.

Reference documentation for the file_handlers property of manifest.json.

How to open files in Chrome extension service workers, popups, side panels, or content scripts.

An overview of the recent changes in Chrome Extensions, plus exciting upcoming extension features developers can look forward to.

How to set up your Chrome Web Store developer account.

Prepare your extension files.

How to write an automated test for Chrome Extensions using Puppeteer.

How to write end-to-end tests for extensions.

How to write unit tests for extensions.

Check whether a bug or feature request has already been reported.

Submit a request for a feature that you believe could improve the extension platform.

Give us feedback to help us improve the platform and fix its bugs.

How to report extension bugs or problems with documentation.

Learn how to use DevTools to debug Chrome extensions.

Overview of how web storage APIs and cookies work in extensions.

Guidance for publishing a new Manifest V3 extension

Experience and advice on participating in Google Summer of Code.

Starting in Chrome 117, Chrome will proactively highlight to users when an extension they have installed is no longer in the Chrome Web Store.

Reference documentation for the "content_scripts" property of manifest.json.

See analytics for your Chrome Web Store listing in addition to the metrics offered in the Developer Dashboard.

A summary of important changes in Chrome 116 for Chrome Extension developers.

An overview of the changes so far this year in Chrome Extensions, plus exciting upcoming extension features developers can look forward to.

Step-by-step instructions on how to connect to a WebSocket in your Chrome extension.

How to use geolocation in Chrome extension service workers, popups, side panels, or content scripts.

Introducing the new Side Panel API for Chrome extensions.

Reference documentation for the background property of manifest.json.

Extension service workers are an extension's central event handler. That makes them different from web service workers.

Extension service workers respond to both standard service worker events and many events in the extension APIs.

Extension service workers are installed and updated differently from web service workers.

Extension service workers respond to both standard service worker events and events in extension namespaces. They are presented together because often one type follows another during an extension's use.

How to record audio or video from a tab, window, or screen.

Learn how to create and debug an extension service worker.

The manifest.json file requires a slightly different format for Manifest V3 than for Manifest V2.

The second of three sections describing changes needed for code that is not part of the extension service worker.

A quick reference for upgrading your extensions from Manifest V2 to Manifest V3.

The first of three sections describing changes needed for code that is not part of the extension service worker.

A service worker enables extensions to run only when needed, saving resources.

The last of three sections describing changes needed for code that is not part of the extension service worker.

Exchange messages with native applications from your Chrome Extension.

Where to go for help with questions not covered by the documentation.

A guide explaining how to test service worker termination using Puppeteer.

Extension service workers can now stay alive as long as they're receiving events. This increases the reliability of extension services workers, but has a pitfall you should avoid.

Introducing the Offscreen Documents API for Chrome extension development.

How to get a website's favicon.

Frequently asked questions about Chrome Web Store's policies on affiliate ads.

Chrome is updating the Chrome Web Store's Developer Program Policies to clearly state our guiding principals, provide more context on enforcement, and make our policies easier to understand.

Any affiliate program must be described prominently in the product's Chrome Web Store page, user interface, and before installation. Related user action is required before the inclusion of each affiliate code, link, or cookie. Some example violations

The Extensions API has been updated to support back/forward cache, preloading navigations.

Reference documentation for the oauth2 property of manifest.json.

We do not allow products that deceive or mislead users, including in the content, title, description, or screenshots. If any of your product's content, title, icon, description, or screenshots contains false or misleading information, we may remove

If your product is associated with a security vulnerability that could be exploited to compromise another application, service, browser, or system, we may remove your product from the Chrome Web Store and take other measures to protect users. In such

Ads are considered part of your Product for purposes of content review and compliance with developer terms, and therefore must comply with the above content policies. Ads which are inconsistent with the content rating of your products or extension

Don't engage in or promote unlawful activities in your product, such as rape, illegal sex work, or the sale of prescription drugs without a prescription. We will remove content which promotes, glorifies, or encourages dangerous or illegal activity

This policy establishes the Chrome Web Store's minimum user data privacy requirements; you or your Product must comply with applicable laws. You must limit your use of the data to the practices you disclosed. Collection and use of web browsing

Request access to the narrowest permissions necessary to implement your Product's features or services. If more than one permission could be used to implement a feature, you must request those with the least access to data or functionality. Don't

The Chrome Web Store features products that align with our standards, values, and that we believe will produce valuable user experiences. Certain products that don't meet these standards, but which do not explicitly violate Chrome Web Store

Don't pretend to be someone else, and don't represent that your product is authorized by, endorsed by, or produced by another company or organization, if that is not the case. Your Product and its user experience also must not mimic functionality or

If you collect sensitive personal information through your Product for sales, you must follow these requirements: You must securely collect, store, and transmit all credit card and other sensitive personal information in accordance with privacy and

You must be transparent in how you handle user data (e.g., information provided by a user or collected about a user or a user's use of the Product or Chrome Browser), including by disclosing the collection, use, and sharing of the data. If your

We don't allow any developer, related developer accounts, or their affiliates to submit multiple extensions that provide duplicate experiences or functionality on the Chrome Web Store. Extensions should provide value to users through the creation of

To ensure a great user experience, Chrome Apps distributed through the Chrome Web Store must follow the additional quality guidelines listed below. The guidelines in this section apply only to Chrome Apps. Packaged apps should: Take advantage of the

Don't transmit viruses, worms, defects, Trojan horses, malware, or any other products of a destructive nature. We don't allow content that harms or interferes with the operation of the networks, servers, or other infrastructure of Google or any

Do not post an extension with a single purpose of installing or launching another app, theme, webpage, or extension. Extensions with broken functionality—such as dead sites or non-functioning features—are not allowed. Extensions must provide a basic

Developers must not obfuscate code or conceal functionality of their extension. This also applies to any external code or resource fetched by the extension package. Minification is allowed, including the following forms: Removal of whitespace,

Chrome is updating the Chrome Web Store's Developer Program Policies to clearly state our guiding principals, provide more context on enforcement, and make our policies easier to understand.

Extensions must use existing Chrome APIs for their designated use case. Use of any other method, for which an API exists, would be considered a violation. For example, overriding the Chrome New Tab Page through any means other than the URL Overrides

Depictions of gratuitous violence are not allowed. Products should not contain materials that threaten, harass, or bully other users. We don't allow content or products that advocating against or inciting hatred towards groups of people based on

Any attempt to circumvent intended limitations or enforcement actions will result in the immediate termination of your developer account, and possibly related developer accounts.

In the event that your Product is removed from the Chrome Web Store, you will receive an email notification to that effect, with further instructions if applicable. Verify that the associated publisher account with your Product can receive emails

If your Product handles any user data, then you must post an accurate and up to date privacy policy. The privacy policy must, together with any in-Product disclosures, comprehensively disclose: How your Product collects, uses and shares user data All

Serious or repeated violations of the Chrome Web Store Distribution Agreement or these Program Policies will result in the suspension of your developer account, and possibly related developer accounts. Additionally, you may be banned from using the

To ensure the security of Chrome Web Store accounts, 2-Step Verification is required for all developer accounts prior to publishing an extension or updating an existing extension. Developers can activate 2-Step Verification for their Google accounts

Reference documentation for the input_components property of manifest.json.

A better way to start the Chrome developer learning journey.

Learn how to automatically add new elements to existing webpages.

Learn how to programmatically organize tabs using tab groups.

Create your first Hello World Chrome extension.

Learn how to simplify the style of the current page.

Reference documentation for the author name property of manifest.json.

New details about the plan to move extensions to Manifest V3

Recently, we announced changes to the Manifest V2 deprecation timeline, and while we remain firmly committed to Manifest V3 we acknowledge there is more work to do on our part. We are committed to closing the following gaps before announcing a new

Google is rolling out a revamped item analytics experience for the Chrome Web Store Developer Dashboard. The new dashboard is easier to understand at a glance and consolidates the most useful information upfront.

An overview of how users find items on the Chrome Web Store, and how our editors select items to feature.

An overview of the review process and how enforcement actions result from detected policy violations.

Updating our security requirements and further clarifying a few policies to keep the quality of extensions high, and the experience for developers consistent.

Sharing details about the plan to move extensions to Manifest V3

Details of the Manifest V2 phase-out and end of life.

Follow-up on reviews and provide user support in the Chrome Web Store.

How to check the review status of your Chrome Web Store item.

Understanding metrics and performance of your Chrome Web Store store listing.

Reference documentation for the cross_origin_opener_policy property of manifest.json.

Reference documentation for the cross_origin_embedder_policy property of manifest.json.

Overview of cross-origin isolation for extensions

Reference documentation for the cross_origin_opener_policy property of manifest.json.

Overview of cross-origin isolation for extensions

Reference documentation for the cross_origin_embedder_policy property of manifest.json.

How to distribute extensions to enterprise users

Updating our security requirements and further clarifying a few policies to keep the quality of extensions high, and the experience for developers consistent.

Chrome extensions had Browser and Page Actions APIs for years, but Manifest V3 replaced both with a generic Actions API. This post explores the history of these APIs and what has changed in Manifest V3.

The Scripting API is a new Manifest V3 API focused on, well, scripting. Let's dig into the motivations for this change and how it's different.

Open source tool to convert extensions to Manifest V3. You'll still need to manually update any code with non-mechanical changes, such as adapting to use service workers or some script injection.

Web Accessible Resources for Manifest V3 is here! Now `manifest.json` supports permission definitions. Developers can restrict resources based on the requesting site origin or extension id.

How to choose which countries will list your item and who will see it in the Chrome Web Store.

How to add listing information for your Chrome Web Store item.

How to update an extension or theme ("item") that you previously published on the Chrome Web Store.

Guidelines for understanding why an item was rejected or removed from the Chrome Web Store and how to fix the problem.

Documentation for Chrome extensions developers.

Why the payments is deprecated, details about the deprecation timeline, and more.

How to delete a developer or group publisher account on the Chrome Web Store.

How to share ownership of your Chrome Web Store items with other developers.

Use the privacy practices tab to help the Chrome Web Store team review your extension as quickly as possible.

Frequently asked questions about Chrome Web Store's spam policy.

Guidelines for updating your Extensions to handle the runtime host permission changes starting in Chrome 70.

Frequently asked questions about the deprecation of inline installations for Chrome Extensions.

Guidelines about the kinds of images you need to supply to the Chrome Web Store.

Guidelines for use of Google trademarks.

How to migrate a persistent background script to an event-based, non-persistent model to improve the performance of your Chrome Extension.

Guidelines on how to build a high-performance Chrome Extension.

Guidelines for ensuring that your Chrome Extension protects user privacy.

Guidelines for ensuring that your Chrome Extension protects user privacy.

UI and design guidelines for Chrome Extensions.

How to keep your Chrome Extension secure.

How to keep your Chrome Extension secure.

How to package, host, and update crx files from a personal server for Linux users.

How to package, host, and update crx files from a personal server.

How to create a high-quality extension and Chrome Web store listing.

Frequently asked questions about Chrome Web Store's user data policy.

Frequently asked questions about Chrome Web Store's user data policy.

Reference documentation for the event_rules property of manifest.json.

Reference documentation for the event_rules property of manifest.json.

Media Source Extensions (MSE) provide extended buffering and playback control for the HTML5 audio and video elements. While originally developed to facilitate Dynamic Adaptive Streaming over HTTP (DASH) based video players, MSE can be used for audio; specifically for gapless playback.

An explanation of the Chrome Web Store and why you might want to use it.

How to share code between Chrome Extensions.

How to share code between Chrome Extensions.

Show notifications to Chrome Extension users.

How to show notifications to your Chrome Extension users.

Details about the hosting changes for Chrome Extensions that started in version 33 of Chrome.

How to publish a new extension or theme to the Chrome Web Store.

The legal agreement governing the relationship between Chrome Web Store developers and the Chrome Web Store.

Guidelines about how the Chrome Web Store rates the maturity of content.

Step-by-step instructions on how to create a Chrome Extension.

Frequently asked questions about Chrome Extensions.

Guidelines on how to migrate from manifest v1 to manifest v2.

Reference documentation for the chrome.location API.

How to override Chrome settings from a Chrome Extension.

How to override Chrome settings from a Chrome Extension.

Reference documentation for the storage property of manifest.json.

Reference documentation for the storage property of manifest.json.

Reference documentation for the externally_connectable property of manifest.json.

Reference documentation for the externally_connectable property of manifest.json.

Reference documentation for the name and short_name properties of manifest.json.

Reference documentation for the icons property of manifest.json.

Reference documentation for the sandbox property of manifest.json.

Reference documentation for the sandbox property of manifest.json.

Reference documentation for the nacl_modules property of manifest.json.

Reference documentation for the incognito property of manifest.json.

Reference documentation for the requirements property of manifest.json.

Reference documentation for the description property of manifest.json.

Reference documentation for the homepage_url property of manifest.json.

Reference documentation for the short_name property of manifest.json.

Reference documentation for the key property of manifest.json.

Reference documentation for the incognito property of manifest.json.

Reference documentation for the web_accessible_resources property of manifest.json.

Reference documentation for the name property of manifest.json.