Camera Recorder

Web

Record video and audio from your webcam using MediaRecorder with WebM or MP4 output. Switch device and frame rate, then save clips locally. Save clips locally.

Idle
CAMLive preview
Click "Start camera" to begin

About Camera Recorder

This tool uses getUserMedia and MediaRecorder to capture your camera and microphone into a WebM video - entirely on your device. You can choose the camera, toggle audio and preview live. Nothing is uploaded, so there is no server and no watermark. It suits demo clips, tutorial snippets and device self-checks, with no screen recorder to install. The relation between permission and user gesture is the first trap: browsers require recording to start inside the call stack of a user action such as a click or keypress, and otherwise reject the request outright, often without a readable error. It cannot start on page load or from a timer. Where advance preparation is needed, request permission first but do not start until the user clicks. Codec support is decided by browser and hardware together, so recording options need a fallback. The same container has different supported encoders across devices and some environments lack common ones, where specifying directly yields an unsupported error. Query available capabilities first, choose by priority, and keep a generally supported option so the feature works on most devices. Estimate duration and size in advance: resolution times bitrate times duration gives the rough volume, and long recordings hold memory and encoder resources continuously while background tabs may be throttled. Split long recordings, release the previous segment promptly, and you avoid both dropped frames and crashes near the memory ceiling. Against system screen recording, the browser advantage is coupling to application state: UI actions and parameters can be captured alongside for correlated material. The cost is confinement to the page, with other applications out of reach. It suits demonstrating operations inside this tool rather than general screen capture, so decide by whether the subject is inside the page. Finally, delivery: recordings are large, so confirm the format plays in the recipient player. When unsure, converting once to a common format is less work than leaving it to them, and putting resolution and bitrate in the filename or a note lets them judge sufficiency without a round trip about sharpness. One more premise is the device gap between recording and playback: resolution and frame rate the recording device handles may not play smoothly elsewhere, and older hardware struggles to decode high resolutions. For a broad audience, offer a lower-resolution version alongside or state the original parameters so the recipient can choose rather than transcode.

How It Works Internally

In-browser recording depends on two things: device permission and codec support. Permission must be requested inside a user gesture or it is silently denied, and the encoding format is decided jointly by browser and hardware, with some environments lacking a particular encoder such as H.264 in certain containers, so recording options need a fallback rather than assuming one works. Automated tests must grant media permission explicitly.

InputCalling the recording API without a user gesture
OutputThe request is denied outright and may not raise a readable error — it must start inside a gesture such as a click, or the test framework must grant permission explicitly

Measured on This Page

Permission-denied pathAfter clicking Start the error area shows "Unable to access the camera: Requested device not found" — the error is caught, translated into plain language and the page stays up
Error attributionNotAllowedError (user denied) and NotFoundError (no device) both flow into the same error branch with the raw message appended for distinguishing
Preview elementThe <video> preview and MediaRecorder support detection (preferring webm vp9/opus) are ready
Recording outputWebM (vp9+opus preferred, vp8 fallback), a local Blob download, no uploads

Capability boundaries: real camera/microphone recording cannot be verified in a headless test environment (no devices), so what was verified is the permission-denied path and the UI state machine — errors are caught and the page stays stable. Recordings are WebM containers; Safari's MediaRecorder support is limited (iOS 14.3+). All media stays in local memory and downloading is the only way out — nothing is uploaded. To retry after a denial, reset the site permission in browser settings.

How this was measured: A headless environment has no camera: clicking Start makes getUserMedia execute and get denied, which exercises the error path (error message, <video> preview element, no uncaught exceptions). Real camera recording cannot be verified headless — recorded here as a limitation. · Measured 2026-10-30

How to Use

  1. Open "Camera Recorder"
  2. Grant camera access and pick the device to use
  3. Click record; the preview and timer start
  4. Click stop, then review the recorded clip
  5. Download the WebM file when you need to keep it

Use Cases

  • Record demos — Quickly record a talking-head explainer or product demo without installing screen-record software.
  • Device self-check — Test that the camera and mic work and confirm permissions and a clear picture.
  • Video feedback — Let users record a video note in the page and attach the download to a support ticket.
  • Prototype check — Quickly validate the permission and recording flow for a web app that needs video capture.
  • Quick samples — Grab a short clip for local test editing or pre-processing before upload.
  • Device compatibility check — Quickly verify that the user's browser and OS support camera recording across different devices before deploying.
  • Tutorial creation — Record short step-by-step tutorial clips for internal knowledge base articles without needing screen recording software.

FAQ

Is the recorded video uploaded to a server?

No. Camera data enters the page via getUserMedia, MediaRecorder encodes it locally, and the resulting file saves straight to your device — no audio or video is sent to any server.

Why won't the camera open?

Common causes: camera permission not granted, the page is not on HTTPS (or localhost), or another app holds the device. For security, getUserMedia only works in a secure context.

What format is the exported video?

Most browsers output WebM (VP8/VP9 or Opus) via MediaRecorder; Safari support varies. For MP4, transcode the recording with a local tool afterward.

Can I record audio only?

Yes — disable the video track and keep audio for sound only; likewise you can record silent video, depending on which tracks you grant and select.

Is there a recording length limit?

No fixed limit, but the video accumulates in memory and grows with duration, so for long sessions record in segments to avoid heavy tab memory pressure.

The recording has no audio — why?

Allow the microphone in the browser permission prompt first, then check the OS volume mixer for a muted browser. Screen capture does not include system audio by default — enable audio sharing in both browser and OS where supported.

The recording drops frames or stutters?

Resolution and frame rate beyond the device's encoding capability cause drops: 4K is heavy on CPU/GPU. 1080p at 30fps is usually smooth. Also close other apps holding the camera — video-meeting software can monopolise the device and cause black frames.

A long recording will not play or is corrupted?

The browser buffers capture data in memory and very long sessions hit that limit, truncating the file. Record in segments (about 10 minutes each) or lower the resolution and bitrate. Save immediately after recording instead of re-previewing large files.