User scripts and the Manifest V2 phase out
Some extensions run your own scripts on pages, and Chrome no longer runs the old extension format.
chrome.userScripts runs user code on pages; its MAIN world is visible to the page and to other extensions. Chrome 139 removed Manifest V2 extensions, which changes what blockers can do. Userscript managers like Tampermonkey sometimes leave detectable traces.
What it can and can't do
What the user does: None, the page reads it silently
It can
- Run user supplied scripts on matched pages
- Be seen by the page when it runs in the MAIN world
It cannot
- Run without you installing and allowing the extension
- Work in Safari or on phones
How it differs between platforms: Chrome 139 removed Manifest V2. Firefox still supports it. The Tampermonkey GM_info leak is low confidence.
Browser support
Version notes
- Chrome: Needs the userScripts permission, host permissions and a user toggle
- Edge: Supported
- Firefox: Partial, and Manifest V2 is still supported
- Safari: Not supported
- Safari on iPhone: Not supported
- Chrome on Android: No extensions
How a site asks for it
| API | chrome.userScripts.register({ id, matches, js, world }); GM_info; Manifest V2 background pages |
| Browser compat keys | webextensions.api.userScripts |
| How access is granted | user-toggle |
| What the user sees | You turn the extension on and allow the userScripts permission |
| Needs a secure context (HTTPS) | Yes |
| Needs a user gesture | No |
| How long it lasts | Per origin |
| How to take it back | Clear site data |
| Inside an iframe | Same as top level |
Typical flow
- Page calls the API
- Browser answers with no prompt
- Page reads the result
Data you get
What comes back: Some extensions run your own scripts on pages, and Chrome no longer runs the old extension format.
Shape: object
How often: on demand
| Field | Type | Unit | Range | Precision |
|---|---|---|---|---|
world | enum | None | USER_SCRIPT or MAIN | Not listed |
matches | list | None | URL patterns | Not listed |
GM_info | object | None | low confidence trace | Not listed |
Technical limits
- Chrome 139 removed Manifest V2
- Tampermonkey GM_info leak is low confidence
- Userscript managers are Chromium and Firefox centered
The story
What it is
Extensions can run your own small programs on websites, which changes what a page can see.
For you
If you use a userscript manager, your own code can reshape sites. A site may notice those scripts.
For makers
Extension authors need MV3 equivalents for old blocking behavior.
Where you see it
| Type | Example | Apps |
|---|---|---|
| productivity | A user script adds a missing button to a web app. | None named |
Risks
- Scripts can read pages you allow
- MAIN world code is visible to the page
What the platform says
- Chrome for Developers: chrome.userScripts. Lets an extension run user supplied scripts on pages.
Good uses and abuse
Legitimate uses
- Customize sites
Known abuse
- Detecting userscript users
Scores
| Score | Value | Meaning |
|---|---|---|
| Sensitivity | 3 of 5 | How revealing the data is |
| Utility | 3 of 5 | How useful it is to honest apps |
| Friction | 0 of 5 | How much the user has to do |
| Fingerprint bits | 2 | Rough identifying entropy, when known |
History
- 2025-08, Chrome 139: Manifest V2 extensions no longer run
Related capabilities
Related
- Extension traces in the DOM and globals. Can spot some of your extensions from what they add to the page
- Extension presence probing. Can find out which Chrome extensions you have by testing known files
Sources
- Chrome userScripts API (checked 2026-11-16)
- Chrome Manifest V2 deprecation timeline (checked 2026-11-16)
- Tampermonkey documentation (checked 2026-11-16)
How well checked: Inferred from related behavior.