Back to articles

The `desktopCapture` permission explained: what browser extensions can really do with your screen

Chrome's desktopCapture permission lets extensions record your screen, windows and tabs. Here's what the picker really allows — and how to check yours.

Maxim Kosterin
8 min read
Three hairline screen frames in a row; the one circled by an ink enso is washed in orange watercolor, and a long orange ribbon streams away from it — one pick in the picker, one continuous stream.
Three hairline screen frames in a row; the one circled by an ink enso is washed in orange watercolor, and a long orange ribbon streams away from it — one pick in the picker, one continuous stream.

Of all the permissions I've worked through in this series, desktopCapture has the strangest consent story. At install time Chrome shows one short line — Frisbie's permission catalog in Building Browser Extensions (Apress, 2025) records the warning as "Capture content of your screen." Then, every single time an extension actually wants to record, Chrome pops its own picker and makes you point at a screen, a window, or a tab.

That picker makes this feel like the safest permission in the browser. It mostly is — one approval still turns into a continuous video stream of everything on the surface you picked, until the extension decides to stop. And desktopCapture is not the only way an extension can see your screen. The neighbors are quieter.

What the desktopCapture permission is

One line in a manifest — "desktopCapture" in the permissions array — unlocks the chrome.desktopCapture API: capture of your entire screen, a single window, or a single browser tab, plus optionally the audio playing through it. It's the API behind screen recorders like Screencastify and Loom, behind "share your screen" buttons in meeting helpers, and behind remote-support tools.

It's also Chromium-only. As Frisbie notes, the API is available in Chromium browsers and nothing else — and Firefox indeed doesn't implement it: desktopCapture simply isn't in MDN's WebExtensions API index. A Firefox add-on that needs screen content goes through the standard web API instead, picker included.

It's rare, but heavy. In the Extenshi catalog's August 2026 snapshot of 362,889 live Chrome, Firefox and Edge listings, desktopCapture doesn't make the top 30 permissions — fewer than 3,150 extensions declare it, under 1% of the ecosystem. For comparison, nativeMessaging sits at 4,292. Small population, enormous per-install footprint: this is the permission that hands over pixels.

What one approval actually allows

The flow, from Chrome's API reference: the extension calls chrome.desktopCapture.chooseDesktopMedia() with the source types it wants offered — screen, window, tab, and optionally audio. Chrome draws the picker. The extension can't style it, skip it, or pre-select inside it; it's browser chrome, not page content.

When you pick a source, the callback receives a streamId: an opaque, single-use token that expires within seconds if unused. The extension feeds it to getUserMedia() and from that moment holds a live MediaStream — every pixel of the chosen surface, continuously, until the extension stops the tracks. Nothing re-prompts while the stream runs. The picker authorizes a session, not a snapshot.

Three details worth knowing:

Audio rides along. If the extension offers audio as a source, the picker shows a "Share audio" checkbox, and the callback's canRequestAudioTrack flag tells the extension whether you left it ticked. The reference also lists finer audio knobs — a system-audio preference (Chrome 105+) and a per-window audio preference (Chrome 140+), both mirroring the W3C Screen Capture spec — though the option that would carry them isn't documented yet.

The stream can be handed to a web page. chooseDesktopMedia() takes an optional targetTab. When supplied, the stream is scoped to frames in that tab whose origin matches (and that origin must be HTTPS) — the legitimate mechanism behind meeting sites that pair with a companion extension for screen sharing.

In MV3, recording happens out of sight. A service worker can't hold a MediaStream, so capture extensions do the work in an offscreen document — a hidden extension page. I built the whole pattern, step by step, in the tabCapture recording tutorial.

While capture runs, Chrome keeps its own indicators up — a highlight frame around a shared tab, a stop-sharing notice for screen and window capture. On macOS there's another gate underneath all of this: the browser itself needs Screen Recording permission in System Settings before it can capture your screen or other apps' windows.

The picker is honest. The neighbors aren't always.

Because desktopCapture always asks, it's tempting to assume any screen capture you experience went through it. Not true — there are quieter paths, and they're legitimate APIs too.

tabCapture records the currently active tab, with no picker at all. Once invoked — a click on the toolbar icon is enough — the extension can start capturing that tab's video and audio with no dialog; the only sign is a small "being shared" icon on the tab itself. The install warning is why it slips past people: per Chrome's permission list, tabCapture shows the generic "Read and change all your data on all websites" — nothing about recording.

tabs.captureVisibleTab() takes a still screenshot of whatever tab is visible — again no picker, gated only by the <all_urls> permission or by activeTab (a click on the toolbar icon). I covered the <all_urls> host permission separately; it's what makes this one broad.

And a picker doesn't mean an extension is involved at all. Any website can call navigator.mediaDevices.getDisplayMedia(), which shows the same share dialog. Per MDN, it demands a real user gesture, and the permission cannot be persisted — the site must ask every single time.

The practical risk here isn't an API going rogue. It's oversharing inside the picker. Choose "Entire screen" for a quick demo and every notification, password-manager popup and banking tab you open during that session lands in the recording. The browser faithfully captures what you point it at; the judgment call was yours, made in a two-second dialog.

When it has gone wrong

The track record for this permission is less about capture itself and more about everything around it.

The cleanest example: in 2022, security researcher Wladimir Palant found a cross-site scripting flaw in Screencastify that, as BleepingComputer reported, a malicious page could trigger through clickjacking — potentially recording through the victim's webcam and exfiltrating videos stored in their linked Google Drive. He reported it in February 2022 and Screencastify fixed the XSS within a day, but the broader exposure behind it — every page on the vendor's sites could talk to the extension — was still there when Palant published the details in May 2022. Updates over the following week closed it.

The lesson isn't that Screencastify was malicious — it plainly wasn't. It patched the bug fast; narrowing the wider attack surface took three months and a public write-up. It's that a tool holding capture capability becomes a high-value target the moment any part of its code can be fooled. I broke down the whole category, permissions included, in my screen recorder extensions review.

The other pattern is ownership. An extension sold to a new operator takes its granted capability with it — the QuickLens takeover and the ShotBird hijack showed how quickly a benign tool becomes something else after a sale. A sold screen recorder is a sold screen recorder.

Risk assessment: when to shrug, when to dig

Reach for the shrug when:

  • the extension is a purpose-built recorder or meeting tool from a vendor you recognize, and capture is the product;
  • the picker appears every session (it has no choice — that's how the API works);
  • the listing says where recordings go: uploaded, stored, retained, deleted.

Dig deeper when:

  • an extension whose features never involve screens holds desktopCapture. A coupon finder has no business offering to record your display;
  • capture sits next to <all_urls> host access and remotely-updatable logic — that combination is a surveillance kit wearing a utility's clothes;
  • nobody can tell you what happens to the video afterwards. The streamId expires in seconds, but frames already recorded are governed by company policy, not by the browser.

How to check your extensions

Open chrome://extensions, hit Details on anything that records, screenshots or joins meetings, and read the permission list. Anything mentioning screen capture deserves a "why does this need it" moment.

Before you install, paste the store URL into Extenshi's checker — one extension, one report: safety score, declared permissions, flags. If you want a worked example, here's Screencastify's security report, and the catalog's full list of screen recorder extensions if you're shopping for a safer one.

Your screen is the last surface in the browser that still feels private. Keep it that way by knowing exactly which extensions can ask for it — and which ones can take pieces of it without asking.

Check an extension →

Further reading

📚 Building Browser Extensions, 2nd Edition by Matt Frisbie — Amazon | Apress

Sources


This article is based on publicly available security research and news reporting. Extenshi does not independently verify all claims made by third-party researchers. References to specific companies or products reflect the findings of cited sources and do not constitute accusations of intentional wrongdoing. If you believe any information is inaccurate, please contact us at [email protected].

Related Articles