## Description
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.
Most members of this API do **not** require any permissions. This permission is needed for [`connectNative()`](https://developer.chrome.com/docs/extensions/reference/api/runtime#method-connectNative), [`sendNativeMessage()`](https://developer.chrome.com/docs/extensions/reference/api/runtime#method-sendNativeMessage) and [`onNativeConnect`](https://developer.chrome.com/docs/extensions/reference/api/runtime#event-onConnectNative).
The following example shows how to declare the `"nativeMessaging"` permission in the manifest:
manifest.json:
{
"name": "My extension",
...
"permissions": [
"nativeMessaging"
],
...
}
## Concepts and usage
The Runtime API provides methods to support a number of areas that your extensions
can use:
Message passing
: Your extension can communicate with different contexts within your extension and also with other extensions using these methods and events:
[`connect()`](https://developer.chrome.com/docs/extensions/reference/api/runtime#method-connect),
[`onConnect`](https://developer.chrome.com/docs/extensions/reference/api/runtime#event-onConnect),
[`onConnectExternal`](https://developer.chrome.com/docs/extensions/reference/api/runtime#event-onConnectExternal),
[`sendMessage()`](https://developer.chrome.com/docs/extensions/reference/api/runtime#method-sendMessage),
[`onMessage`](https://developer.chrome.com/docs/extensions/reference/api/runtime#event-onMessage) and
[`onMessageExternal`](https://developer.chrome.com/docs/extensions/reference/api/runtime#event-onMessageExternal).
In addition, your extension can pass messages to native applications on the user's device using
[`connectNative()`](https://developer.chrome.com/docs/extensions/reference/api/runtime#method-connectNative) and
[`sendNativeMessage()`](https://developer.chrome.com/docs/extensions/reference/api/runtime#method-sendNativeMessage).
> [!NOTE]
> **Note:** See [Message Passing](https://developer.chrome.com/docs/extensions/mv3/messaging) for an overview of the subject.
Accessing extension and platform metadata
: These methods let you retrieve several specific pieces of metadata about the extension and the
platform. Methods in this category include
[`getManifest()`](https://developer.chrome.com/docs/extensions/reference/api/runtime#method-getManifest), and
[`getPlatformInfo()`](https://developer.chrome.com/docs/extensions/reference/api/runtime#method-getPlatformInfo).
Managing extension lifecycle and options
: These properties let you perform some meta-operations on the extension, and display the options page.
Methods and events in this category include
[`onInstalled`](https://developer.chrome.com/docs/extensions/reference/api/runtime#event-onInstalled),
[`onStartup`](https://developer.chrome.com/docs/extensions/reference/api/runtime#event-onStartup),
[`openOptionsPage()`](https://developer.chrome.com/docs/extensions/reference/api/runtime#method-openOptionsPage),
[`reload()`](https://developer.chrome.com/docs/extensions/reference/api/runtime#method-reload),
[`requestUpdateCheck()`](https://developer.chrome.com/docs/extensions/reference/api/runtime#method-requestUpdateCheck), and
[`setUninstallURL()`](https://developer.chrome.com/docs/extensions/reference/api/runtime#method-setUninstallURL).
Helper utilities
: These methods provide utility such as the conversion of internal resource representations to
external formats. Methods in this category include
[`getURL()`](https://developer.chrome.com/docs/extensions/reference/api/runtime#method-getURL).
Kiosk mode utilities
: These methods are available only on ChromeOS, and exist mainly to support kiosk implementations.
Methods in this category include
[`restart()`](https://developer.chrome.com/docs/extensions/reference/api/runtime#method-restart) and
[`restartAfterDelay()`\`](https://developer.chrome.com/docs/extensions/reference/api/runtime#method-restartAfterDelay).
### Unpacked extension behavior
When an [unpacked](https://developer.chrome.com/docs/extensions/get-started/tutorial/hello-world#load-unpacked) extension is [reloaded](https://developer.chrome.com/docs/extensions/get-started/tutorial/hello-world#reload), this is treated as an update. This means that the
[`browser.runtime.onInstalled`](https://developer.chrome.com/docs/extensions/reference/api/runtime#event-onInstalled) event will fire with the `"update"` reason. This
includes when the extension is reloaded with [`browser.runtime.reload()`](https://developer.chrome.com/docs/extensions/reference/api/runtime#method-reload).
## Use cases
### Add an image to a web page
For a web page to access an asset hosted on another domain, it must specify the resource's full URL
(e.g. ``). The same is true to include an extension asset on
a web page. The two differences are that the extension's assets must be exposed as [web
accessible resources](https://developer.chrome.com/docs/extensions/mv3/manifest/web_accessible_resources) and that typically content scripts are responsible for injecting
extension assets.
In this example, the extension will add `logo.png` to the page that the [content
script](https://developer.chrome.com/docs/extensions/develop/concepts/content-scripts) is being [injected](https://developer.chrome.com/docs/extensions/develop/concepts/content-scripts#functionality) into by using `runtime.getURL()` to create a
fully-qualified URL. But first, the asset must be declared as a web accessible resource in the manifest.
manifest.json:
{
...
"web_accessible_resources": [
{
"resources": [ "logo.png" ],
"matches": [ "https://*/*" ]
}
],
...
}
content.js:
{ // Block used to avoid setting global variables
const img = document.createElement('img');
img.src = browser.runtime.getURL('logo.png');
document.body.append(img);
}
### Send data from a content script to the service worker
Its common for an extension's content scripts to need data managed by another part of the extension,
like the service worker. Much like two browser windows opened to the same web page, these
two contexts cannot directly access each other's values. Instead, the extension can use [message
passing](https://developer.chrome.com/docs/extensions/develop/concepts/messaging) to coordinate across these different contexts.
In this example, the content script needs some data from the extension's service worker to
initialize its UI. To get this data, it passes the developer-defined `get-user-data` message
to the service worker, and it responds with a copy of the user's information.
content.js:
// 1. Send a message to the service worker requesting the user's data
browser.runtime.sendMessage('get-user-data', (response) => {
// 3. Got an asynchronous response with the data from the service worker
console.log('received user data', response);
initializeUI(response);
});
service-worker.js:
// Example of a simple user data object
const user = {
username: 'demo-user'
};
browser.runtime.onMessage.addListener((message, sender, sendResponse) => {
// 2. A page requested user data, respond with a copy of `user`
if (message === 'get-user-data') {
sendResponse(user);
}
});
### Gather feedback on uninstall
Many extensions use post-uninstall surveys to understand how the extension could better serve its
users and improve retention. The following example shows how to add this functionality.
background.js:
browser.runtime.onInstalled.addListener(details => {
if (details.reason === browser.runtime.OnInstalledReason.INSTALL) {
browser.runtime.setUninstallURL('https://example.com/extension-survey');
}
});
## Examples
See the [Manifest V3 - Web Accessible Resources demo](https://github.com/GoogleChrome/chrome-extensions-samples/tree/main/api-samples/web-accessible-resources) for more Runtime API examples.
## Types
### ContextFilter
Chrome 114+ browser.\* since Chrome 148
A filter to match against certain extension contexts. Matching contexts must match all specified filters; any filter that is not specified matches all available contexts. Thus, a filter of \`{}\` will match all available contexts.
#### Properties
- contextIds string\[\] optional
- contextTypes [ContextType](https://developer.chrome.com/docs/extensions/reference/api/runtime#type-ContextType)\[\] optional
- documentIds string\[\] optional
- documentOrigins string\[\] optional
- documentUrls string\[\] optional
- frameIds number\[\] optional
- incognito boolean optional
- tabIds number\[\] optional
- windowIds number\[\] optional
### ContextType
Chrome 114+ browser.\* since Chrome 148
#### Enum
"TAB"
Specifies the context type as a tab
"POPUP"
Specifies the context type as an extension popup window
"BACKGROUND"
Specifies the context type as a service worker.
"OFFSCREEN_DOCUMENT"
Specifies the context type as an offscreen document.
"SIDE_PANEL"
Specifies the context type as a side panel.
"DEVELOPER_TOOLS"
Specifies the context type as developer tools.
### ExtensionContext
Chrome 114+ browser.\* since Chrome 148
A context hosting extension content.
#### Properties
- contextId string
A unique identifier for this context
- contextType [ContextType](https://developer.chrome.com/docs/extensions/reference/api/runtime#type-ContextType)
The type of context this corresponds to.
- documentId string optional
A UUID for the document associated with this context, or undefined if this context is hosted not in a document.
- documentOrigin string optional
The origin of the document associated with this context, or undefined if the context is not hosted in a document.
- documentUrl string optional
The URL of the document associated with this context, or undefined if the context is not hosted in a document.
- frameId number
The ID of the frame for this context, or -1 if this context is not hosted in a frame.
- incognito boolean
Whether the context is associated with an incognito profile.
- tabId number
The ID of the tab for this context, or -1 if this context is not hosted in a tab.
- windowId number
The ID of the window for this context, or -1 if this context is not hosted in a window.
### ExtensionLoadDetails
Chrome 157+
Details about the extension load event.
#### Properties
- previousVersion string optional
Indicates the previous version of the extension. This is present only if 'reason' is 'update' or 'enable'. If 'reason' is 'update', this is the version of the extension before it was updated. If 'reason' is 'enable', this is the current version of the extension.
- reason [OnLoadedReason](https://developer.chrome.com/docs/extensions/reference/api/runtime#type-OnLoadedReason)
The reason that this event is being dispatched.
### MessageSender
An object containing information about the script context that sent a message or request.
#### Properties
- documentId string optional
Chrome 106+ browser.\* since Chrome 148
A UUID of the document that opened the connection.
- documentLifecycle string optional
Chrome 106+ browser.\* since Chrome 148
The lifecycle the document that opened the connection is in at the time the port was created. Note that the lifecycle state of the document may have changed since port creation.
- frameId number optional
The [frame](https://developer.chrome.com/docs/extensions/reference/webNavigation/#frame_ids) that opened the connection. 0 for top-level frames, positive for child frames. This will only be set when `tab` is set.
- id string optional
The ID of the extension that opened the connection, if any.
- nativeApplication string optional
Chrome 74+ browser.\* since Chrome 148
The name of the native application that opened the connection, if any.
- origin string optional
Chrome 80+ browser.\* since Chrome 148
The origin of the page or frame that opened the connection. It can vary from the url property (e.g., about:blank) or can be opaque (e.g., sandboxed iframes). This is useful for identifying if the origin can be trusted if we can't immediately tell from the URL.
- tab [Tab](https://developer.chrome.com/docs/extensions/reference/tabs/#type-Tab) optional
The [`tabs.Tab`](https://developer.chrome.com/docs/extensions/reference/tabs/#type-Tab) which opened the connection, if any. This property will **only** be present when the connection was opened from a tab (including content scripts), and **only** if the receiver is an extension, not an app.
- tlsChannelId string optional
The TLS channel ID of the page or frame that opened the connection, if requested by the extension, and if available.
- url string optional
The URL of the page or frame that opened the connection. If the sender is in an iframe, it will be iframe's URL not the URL of the page which hosts it.
### OnInstalledReason
Chrome 44+ browser.\* since Chrome 148
The reason that this event is being dispatched.
#### Enum
"install"
Specifies the event reason as an installation.
"update"
Specifies the event reason as an extension update.
"chrome_update"
Specifies the event reason as a Chrome update.
"shared_module_update"
Specifies the event reason as an update to a shared module.
### OnLoadedReason
Chrome 157+
The reason that this event is being dispatched.
#### Enum
"install"
The extension was newly installed.
"update"
The extension was reloaded after an update.
"browser_update"
The browser was updated to a new version.
"enable"
The extension was re-enabled from a disabled state.
"startup"
The extension is being loaded during browser startup.
"reload"
The extension was reloaded (e.g. via chrome.runtime.reload() or the user manually reloaded the extension).
### OnRestartRequiredReason
Chrome 44+ browser.\* since Chrome 148
The reason that the event is being dispatched. 'app_update' is used when the restart is needed because the application is updated to a newer version. 'os_update' is used when the restart is needed because the browser/OS is updated to a newer version. 'periodic' is used when the system runs for more than the permitted uptime set in the enterprise policy.
#### Enum
"app_update"
Specifies the event reason as an update to the app.
"os_update"
Specifies the event reason as an update to the operating system.
"periodic"
Specifies the event reason as a periodic restart of the app.
### PlatformArch
Chrome 44+ browser.\* since Chrome 148
The machine's processor architecture.
#### Enum
"arm"
Specifies the processer architecture as arm.
"arm64"
Specifies the processer architecture as arm64.
"x86-32"
Specifies the processer architecture as x86-32.
"x86-64"
Specifies the processer architecture as x86-64.
"mips"
Specifies the processer architecture as mips.
"mips64"
Specifies the processer architecture as mips64.
"riscv64"
Specifies the processer architecture as riscv64.
### PlatformInfo
An object containing information about the current platform.
#### Properties
- arch [PlatformArch](https://developer.chrome.com/docs/extensions/reference/api/runtime#type-PlatformArch)
The machine's processor architecture.
- nacl_arch [PlatformNaclArch](https://developer.chrome.com/docs/extensions/reference/api/runtime#type-PlatformNaclArch) optional
Deprecated since Chrome 149
This attribute is deprecated following complete removal of Native Client.
The native client architecture. This may be different from arch on some platforms.
- os [PlatformOs](https://developer.chrome.com/docs/extensions/reference/api/runtime#type-PlatformOs)
The operating system Chrome is running on.
### PlatformNaclArch
Chrome 44+ browser.\* since Chrome 148 Deprecated since Chrome 149
This enum is deprecated following complete removal of Native Client.
The native client architecture. This may be different from arch on some platforms.
#### Enum
"arm"
Specifies the native client architecture as arm.
"x86-32"
Specifies the native client architecture as x86-32.
"x86-64"
Specifies the native client architecture as x86-64.
"mips"
Specifies the native client architecture as mips.
"mips64"
Specifies the native client architecture as mips64.
### PlatformOs
Chrome 44+ browser.\* since Chrome 148
The operating system Chrome is running on.
#### Enum
"mac"
Specifies the MacOS operating system.
"win"
Specifies the Windows operating system.
"android"
Specifies the Android operating system.
"cros"
Specifies the Chrome operating system.
"linux"
Specifies the Linux operating system.
"openbsd"
Specifies the OpenBSD operating system.
### Port
An object which allows two way communication with other pages. See [Long-lived connections](https://developer.chrome.com/docs/extensions/messaging#connect) for more information.
#### Properties
- name string
The name of the port, as specified in the call to [`runtime.connect`](https://developer.chrome.com/docs/extensions/reference/api/runtime#method-connect).
- onDisconnect Event\
Fired when the port is disconnected from the other end(s). [`runtime.lastError`](https://developer.chrome.com/docs/extensions/reference/api/runtime#property-lastError) may be set if the port was disconnected by an error. If the port is closed via [disconnect](https://developer.chrome.com/docs/extensions/reference/api/runtime#method-Port-disconnect), then this event is *only* fired on the other end. This event is fired at most once (see also [Port lifetime](https://developer.chrome.com/docs/extensions/messaging#port-lifetime)).
The `onDisconnect.addListener` function looks like:
```typescript
(callback: function) => {...}
```
- callback function
The `callback` parameter looks like:
```typescript
(port: Port) => void
```
- port [Port](https://developer.chrome.com/docs/extensions/reference/api/runtime#type-Port)
- onMessage Event\
This event is fired when [postMessage](https://developer.chrome.com/docs/extensions/reference/api/runtime#method-Port-postMessage) is called by the other end of the port.
The `onMessage.addListener` function looks like:
```typescript
(callback: function) => {...}
```
- callback function
The `callback` parameter looks like:
```typescript
(message: any, port: Port) => void
```
- message any
- port [Port](https://developer.chrome.com/docs/extensions/reference/api/runtime#type-Port)
- sender [MessageSender](https://developer.chrome.com/docs/extensions/reference/api/runtime#type-MessageSender) optional
This property will **only** be present on ports passed to [onConnect](https://developer.chrome.com/docs/extensions/reference/api/runtime#event-onConnect) / [onConnectExternal](https://developer.chrome.com/docs/extensions/reference/api/runtime#event-onConnectExternal) / [onConnectNative](https://developer.chrome.com/docs/extensions/reference/api/runtime#event-onConnectExternal) listeners.
- disconnect void
Immediately disconnect the port. Calling `disconnect()` on an already-disconnected port has no effect. When a port is disconnected, no new events will be dispatched to this port.
The `disconnect` function looks like:
```typescript
() => {...}
```
- postMessage void
Send a message to the other end of the port. If the port is disconnected, an error is thrown.
The `postMessage` function looks like:
```typescript
(message: any) => {...}
```
- message any
Chrome 52+ browser.\* since Chrome 148
The message to send. This object should be JSON-ifiable.
### RequestUpdateCheckStatus
Chrome 44+ browser.\* since Chrome 148
Result of the update check.
#### Enum
"throttled"
Specifies that the status check has been throttled. This can occur after repeated checks within a short amount of time.
"no_update"
Specifies that there are no available updates to install.
"update_available"
Specifies that there is an available update to install.
## Properties
### id
The ID of the extension/app.
#### Type
string
### lastError
Populated with an error message if calling an API function fails; otherwise undefined. This is only defined within the scope of that function's callback. If an error is produced, but `runtime.lastError` is not accessed within the callback, a message is logged to the console listing the API function that produced the error. API functions that return promises do not set this property.
#### Type
object
#### Properties
- message string optional
Details about the error which occurred.
## Methods
### connect()
```typescript
browser.runtime.connect(
extensionId?: string,
connectInfo?: object,
): Port
```
Attempts to connect listeners within an extension (such as the background page), or other extensions/apps. This is useful for content scripts connecting to their extension processes, inter-app/extension communication, and [web messaging](https://developer.chrome.com/docs/extensions/manifest/externally_connectable). Note that this does not connect to any listeners in a content script. Extensions may connect to content scripts embedded in tabs via [`tabs.connect`](https://developer.chrome.com/docs/extensions/reference/tabs/#method-connect).
#### Parameters
- extensionId string optional
The ID of the extension to connect to. If omitted, a connection will be attempted with your own extension. Required if sending messages from a web page for [web messaging](https://developer.chrome.com/docs/extensions/reference/manifest/externally-connectable).
- connectInfo object optional
- includeTlsChannelId boolean optional
Whether the TLS channel ID will be passed into onConnectExternal for processes that are listening for the connection event.
- name string optional
Will be passed into onConnect for processes that are listening for the connection event.
#### Returns
- [Port](https://developer.chrome.com/docs/extensions/reference/api/runtime#type-Port)
Port through which messages can be sent and received. The port's [onDisconnect](https://developer.chrome.com/docs/extensions/reference/api/runtime#type-Port) event is fired if the extension does not exist.
### connectNative()
```typescript
browser.runtime.connectNative(
application: string,
): Port
```
Connects to a native application in the host machine. This method requires the `"nativeMessaging"` permission. See [Native Messaging](https://developer.chrome.com/extensions/develop/concepts/native-messaging) for more information.
#### Parameters
- application string
The name of the registered application to connect to.
#### Returns
- [Port](https://developer.chrome.com/docs/extensions/reference/api/runtime#type-Port)
Port through which messages can be sent and received with the application
### getBackgroundPage()
Foreground only Deprecated since Chrome 133
```typescript
browser.runtime.getBackgroundPage(): Promise
```
Background pages do not exist in MV3 extensions.
Retrieves the JavaScript 'window' object for the background page running inside the current extension/app. If the background page is an event page, the system will ensure it is loaded before calling the callback. If there is no background page, an error is set.
#### Returns
- Promise\
Chrome 99+ browser.\* since Chrome 148
### getContexts()
Chrome 116+ browser.\* since Chrome 148 MV3+
```typescript
browser.runtime.getContexts(
filter: ContextFilter,
): Promise
```
Fetches information about active contexts associated with this extension
#### Parameters
- filter [ContextFilter](https://developer.chrome.com/docs/extensions/reference/api/runtime#type-ContextFilter)
A filter to find matching contexts. A context matches if it matches all specified fields in the filter. Any unspecified field in the filter matches all contexts.
#### Returns
- Promise\<[ExtensionContext](https://developer.chrome.com/docs/extensions/reference/api/runtime#type-ExtensionContext)\[\]\>
Promise that resolves with the matching contexts, if any.
### getManifest()
```typescript
browser.runtime.getManifest(): object
```
Returns details about the app or extension from the manifest. The object returned is a serialization of the full [manifest file](https://developer.chrome.com/docs/extensions/reference/manifest).
#### Returns
- object
The manifest details.
### getPackageDirectoryEntry()
Foreground only
```typescript
browser.runtime.getPackageDirectoryEntry(): Promise
```
Returns a DirectoryEntry for the package directory.
#### Returns
- Promise\
Chrome 122+ browser.\* since Chrome 148
### getPlatformInfo()
```typescript
browser.runtime.getPlatformInfo(): Promise
```
Returns information about the current platform.
#### Returns
- Promise\<[PlatformInfo](https://developer.chrome.com/docs/extensions/reference/api/runtime#type-PlatformInfo)\>
Chrome 99+ browser.\* since Chrome 148
Promise that resolves with information about the current platform.
### getURL()
```typescript
browser.runtime.getURL(
path: string,
): string
```
Converts a relative path within an app/extension install directory to a fully-qualified URL.
#### Parameters
- path string
A path to a resource within an app/extension expressed relative to its install directory.
#### Returns
- string
The fully-qualified URL to the resource.
### getVersion()
Chrome 143+ browser.\* since Chrome 148
```typescript
browser.runtime.getVersion(): string
```
Returns the extension's version as declared in the manifest.
#### Returns
- string
The extension's version.
### openOptionsPage()
```typescript
browser.runtime.openOptionsPage(): Promise
```
Open your Extension's options page, if possible.
The precise behavior may depend on your manifest's [`options_ui`](https://developer.chrome.com/docs/extensions/develop/ui/options-page#embedded_options) or [`options_page`](https://developer.chrome.com/docs/extensions/develop/ui/options-page#full_page) key, or what Chrome happens to support at the time. For example, the page may be opened in a new tab, within chrome://extensions, within an App, or it may just focus an open options page. It will never cause the caller page to reload.
If your Extension does not declare an options page, or Chrome failed to create one for some other reason, the callback will set [`lastError`](https://developer.chrome.com/docs/extensions/reference/api/runtime#property-lastError).
#### Returns
- Promise\
Chrome 99+ browser.\* since Chrome 148
### reload()
```typescript
browser.runtime.reload(): void
```
Reloads the app or extension. This method is not supported in kiosk mode. For kiosk mode, use chrome.runtime.restart() method.
### requestUpdateCheck()
```typescript
browser.runtime.requestUpdateCheck(): Promise
`). The same is true to include an extension asset on
a web page. The two differences are that the extension's assets must be exposed as [web
accessible resources](https://developer.chrome.com/docs/extensions/mv3/manifest/web_accessible_resources) and that typically content scripts are responsible for injecting
extension assets.
In this example, the extension will add `logo.png` to the page that the [content
script](https://developer.chrome.com/docs/extensions/develop/concepts/content-scripts) is being [injected](https://developer.chrome.com/docs/extensions/develop/concepts/content-scripts#functionality) into by using `runtime.getURL()` to create a
fully-qualified URL. But first, the asset must be declared as a web accessible resource in the manifest.
manifest.json:
{
...
"web_accessible_resources": [
{
"resources": [ "logo.png" ],
"matches": [ "https://*/*" ]
}
],
...
}
content.js:
{ // Block used to avoid setting global variables
const img = document.createElement('img');
img.src = browser.runtime.getURL('logo.png');
document.body.append(img);
}
### Send data from a content script to the service worker
Its common for an extension's content scripts to need data managed by another part of the extension,
like the service worker. Much like two browser windows opened to the same web page, these
two contexts cannot directly access each other's values. Instead, the extension can use [message
passing](https://developer.chrome.com/docs/extensions/develop/concepts/messaging) to coordinate across these different contexts.
In this example, the content script needs some data from the extension's service worker to
initialize its UI. To get this data, it passes the developer-defined `get-user-data` message
to the service worker, and it responds with a copy of the user's information.
content.js:
// 1. Send a message to the service worker requesting the user's data
browser.runtime.sendMessage('get-user-data', (response) => {
// 3. Got an asynchronous response with the data from the service worker
console.log('received user data', response);
initializeUI(response);
});
service-worker.js:
// Example of a simple user data object
const user = {
username: 'demo-user'
};
browser.runtime.onMessage.addListener((message, sender, sendResponse) => {
// 2. A page requested user data, respond with a copy of `user`
if (message === 'get-user-data') {
sendResponse(user);
}
});
### Gather feedback on uninstall
Many extensions use post-uninstall surveys to understand how the extension could better serve its
users and improve retention. The following example shows how to add this functionality.
background.js:
browser.runtime.onInstalled.addListener(details => {
if (details.reason === browser.runtime.OnInstalledReason.INSTALL) {
browser.runtime.setUninstallURL('https://example.com/extension-survey');
}
});
## Examples
See the [Manifest V3 - Web Accessible Resources demo](https://github.com/GoogleChrome/chrome-extensions-samples/tree/main/api-samples/web-accessible-resources) for more Runtime API examples.