Record Video in the Browser, No App: How It Works and Browser Support

When someone clicks "record" on a web page and their camera light turns on, two standard, long-established web APIs are behind it. getUserMedia (part of the WebRTC family of APIs) asks the browser for permission to access the camera and microphone, and hands back a live media stream if the person grants it. MediaRecorder then takes that stream and encodes it into a video file as it records, which can be uploaded once the person stops.

Neither of these requires installing anything. They are built into the browser itself, the same way a browser already knows how to play a video or submit a form — which is the whole reason a shared link can turn into a working recorder without asking anyone to download an app first.

• They open a link, on desktop or mobile, in whatever browser they already have installed.
• The browser asks, once, for permission to use the camera and microphone for that specific site.
• If they allow it, they see a live preview and a record button — no account, no install, no plugin.
• When they stop recording, the clip is available to review and, usually, re-record before it's submitted.

getUserMedia and MediaRecorder are broadly supported in modern browsers — current versions of Chrome, Safari, Firefox and Edge on both desktop and mobile all support camera and microphone capture in the browser. Exact capability can vary by specific browser version, operating system, and whether the browser is the default one or embedded inside another app (such as an in-app browser within Instagram or LinkedIn, which sometimes restrict camera access). For the current, specific state of support across browser versions, check caniuse.com rather than relying on a table that will inevitably go out of date.

One practical catch worth flagging: some in-app browsers (opening a link from inside a social or messaging app rather than a standalone browser) handle camera permissions inconsistently. If a contributor reports that recording isn't working, asking them to open the link in their regular browser app rather than an embedded one resolves the issue in most cases.

Every modern browser requires a secure connection (HTTPS, not HTTP) before it will grant camera or microphone access through getUserMedia, as a basic protection against a malicious or compromised page silently accessing someone's camera. This is enforced by the browser itself, not by the site — there's no way around it, and no reason to want one.

Because the recording happens inside the browser the person already has, a single link works the same way whether someone opens it on a work laptop, a personal phone, or a tablet — nothing to install, nothing version-specific to manage on your end beyond keeping the page itself up to date. For the privacy and consent side of what happens once that footage exists, see the GDPR employee video checklist.

Frequently asked questions