HTML <usermedia> element (camera and microphone)
A browser-drawn button that asks for camera or microphone; the click is the request.
In one line
Can ask for camera or microphone through a button the browser draws itself
A browser-drawn button that asks for camera or microphone; the click is the request.
Same power as getUserMedia, but the request starts from a button the site cannot disguise. Aims to cut prompt spam and make recovery after a block possible.
What it can and can't do
What the user does: You click the browser made Use camera or Use microphone button on the page
It can
- Show a browser drawn button that starts the camera or microphone request
- Let you retry after you blocked access earlier, since the click is a clear request
- Open the normal camera or microphone prompt
It cannot
- Change the button's label or icon to look like something else
- Turn the camera or microphone on without your click and approval
- Skip the normal prompt
- Work in Firefox, Safari or iPhone browsers
How it differs between platforms: Only Chrome, Edge and Chrome on Android support it for now.
Browser support
| Browser | Status | First version | Released | Note |
|---|---|---|---|---|
| Chrome | Supported | 151 | 2026-07-28 | Origin trial from 144, announced available 2026-06 |
| Edge | Supported | 151 | 2026-07-31 | None |
| Firefox | Not supported | Not available | Not listed | None |
| Safari | Not supported | Not available | Not listed | None |
| Safari on iPhone | Not supported | Not available | Not listed | None |
| Chrome on Android | Supported | 151 | 2026-07-28 | None |
| Samsung Internet | Not supported | Not available | Not listed | None |
How a site asks for it
| API | <usermedia type="camera microphone" onstream=...>; element.stream; setConstraints() |
| Permission name | camera, microphone |
| Permissions policy | camera; microphone |
| Browser compat keys | api.HTMLUserMediaElement |
| How access is granted | prompt |
| What the user sees | Browser-drawn button with fixed label and icon; click opens the normal camera or microphone prompt. |
| Needs a secure context (HTTPS) | Yes |
| Needs a user gesture | Yes |
| How long it lasts | Same stored permissions as getUserMedia |
| How to take it back | Same as camera and microphone |
| Inside an iframe | Needs allow="camera; microphone" in cross-origin iframes |
Typical flow
- Add <usermedia> to the page
- Person clicks the browser-drawn button
- Browser prompts
- stream event delivers a MediaStream
Data you get
What comes back: MediaStream delivered through an element
Shape: stream
How often: continuous
No individual data fields. The signal is the access itself.
Technical limits
- Cannot be hidden, resized or restyled to deceive
- Chrome only for now
The story
What it is
A browser drawn button that a site cannot fake; clicking it asks for camera or microphone.
For you
You see a normal looking button that says something like Use camera. It is drawn by the browser, so the site cannot change what it says. Clicking it starts the permission request, which is clearer than a surprise pop up.
For makers
Makers get a cleaner way to ask, and fewer people who block by mistake because the pop up appeared too early. If someone has blocked the camera, the button lets them change that in one place. It also reduces spam prompts that hurt trust in all sites.
Where you see it
| Type | Example | Apps |
|---|---|---|
| video | A call site shows a Use camera button in the pre join screen, and a click is the request, so you know exactly why it is asking. | Google Meet, Zoom web |
| security | An ID check page shows a browser drawn camera button so a phisher cannot fake the request to look like your bank. | Onfido, Persona |
| games | A browser game with face control shows a clear Enable camera button on the title screen, and not a prompt at page load. | None named |
| social | A web camera effect page shows a button for the camera and another for the microphone, so you pick one without a pile of pop ups. | Snapchat web, Instagram web |
| shopping | A try on page makes you click Use camera to start the live view, which feels like your choice. | Warby Parker, Sephora |
| enterprise | A telehealth waiting room shows the button, so a patient who blocked the camera before can fix it in one click. | Doxy.me, Teladoc |
Risks
- Still new and not in every browser
- People may click without reading
What the platform says
- W3C WICG: Page Embedded Permission Control. A proposal for a browser built button so permission requests start from a real click, not a pop up the site fakes.
Good uses and abuse
Legitimate uses
- Clearer consent for calls
- Recovery from earlier block
Known abuse
- None beyond getUserMedia
Scores
| Score | Value | Meaning |
|---|---|---|
| Sensitivity | 5 of 5 | How revealing the data is |
| Utility | 4 of 5 | How useful it is to honest apps |
| Friction | 1 of 5 | How much the user has to do |
| Fingerprint bits | Not rated | Rough identifying entropy, when known |
History
- 2025-12, Chrome 144: <permission> style elements, including <usermedia>, enter origin trial
- 2026-06, Chrome 151: <usermedia> announced available (an earlier M149 launch was cancelled)
Related capabilities
Related
- Camera (video capture). Can see and record live video from your camera while the tab is open
- Microphone (audio capture). Can hear and record live audio from your microphone while the tab is open
- HTML <geolocation> element. Can show a browser made button that asks for your location when you tap it
Sources
How well checked: Inferred from related behavior.