NodlumeNodlume
Manifest V3 generator

Manifest V3 scripting permission

The scripting permission enables chrome.scripting — executeScript, insertCSS, removeCSS and the dynamic registration of content scripts from the service worker. It is how a Manifest V3 extension injects code on demand instead of only through the static content_scripts array.

The permission alone injects nothing: it also needs access to the target page, from either activeTab (after a user gesture) or a host_permissions match. It produces no install warning by itself; the host permission it is paired with is what the user sees.

Scripting at a glance

Manifest key
"permissions": ["scripting"]
What it enables
Inject scripts into pages on demand, rather than only through the declared content scripts below.
Install warning
None — granted silently at install.
Cross-browser API
browser.scripting via webextension-polyfill

The manifest that declares it

Manifest with this permission

manifest.json
{
  "manifest_version": 3,
  "name": "my-extension",
  "version": "0.1.0",
  "action": {
    "default_popup": "src/popup.html"
  },
  "background": {
    "service_worker": "src/background.ts",
    "type": "module"
  },
  "permissions": [
    "scripting"
  ]
}

This manifest installs with no permission warning.

scripting, answered

The longer version is in the guide Manifest V3 permissions: a practical guide.

What does the scripting permission do in Manifest V3?
Inject scripts into pages on demand, rather than only through the declared content scripts below. It is declared as the string "scripting" in the manifest's permissions array; the browser grants it at install time, and the extension's service worker, popup and other pages can then call the matching API.
Does scripting show an install warning?
No. scripting is granted silently — it appears in the manifest but adds nothing to the install prompt. Host permissions and warning-bearing permissions such as tabs or downloads are what change the prompt.
Can I request scripting at runtime instead?
Yes. Move it from permissions to optional_permissions and call browser.permissions.request({ permissions: ["scripting"] }) from a user gesture when the feature is first used. The manifest generator emits the install-time form; optional grants are an edit to that JSON.

Build the whole manifest

The Chrome extension manifest generator declares every permission with its install warning shown up front, adds the surfaces the browser opens, and validates content-script match patterns before they can reject the whole extension. In the Nodlume workspace the same selection becomes a complete Manifest V3 project with a service worker and a Vite build.

Open the generator

Other Manifest V3 permissions

We'd like to use Google cookies to understand how Nodlume is used and to measure our advertising. Nothing loads until you choose, and declining does not affect anything in the app.