An online webcam recorder with nothing to sign up for
Record your camera and microphone in the browser, review the result, and save it to your own disk. No account, no watermark, and nothing uploaded — with the option of replacing your background while you record.
Camera access is requested there, not here.
The three things people usually check first
No account
There is no sign-up because there is no server holding one. Nothing is gated behind an email address.
No watermark
The recorded frames are the composited frames, with nothing drawn on top. There is no paid tier that removes anything.
No upload
The recording accumulates in memory in your tab and goes to your filesystem when you save it. It has no other destination.
Recording, step by step
Open the studio and allow access
Camera and microphone are requested together, once, on a button press. Declining the microphone is fine — the camera still works and you can record silently.
Check your devices and resolution
Switch camera or microphone from the control bar, watch the live audio meter to confirm the right input is live, and pick 720p or 1080p. 1080p is offered only when your camera reports that it can do it.
Record
A timer runs from the wall clock rather than from a frame count, so it stays accurate even if your machine is briefly busy. You can mute, switch the camera off, or change background without stopping.
Review, then save
The camera and microphone are released the moment you stop, so the hardware light goes out while you watch the playback. Save writes the file to a location you choose.
What the file contains
The recorder is fed the processed canvas — the same pixels on screen in front of you — rather than the raw camera. That is a deliberate structural choice: because there is only one rendering path, there is no way for the preview and the saved file to disagree, and no export step in which the background could come out different from what you approved.
Audio is a separate track from your microphone, mixed in by the container rather than re-encoded. Muting during a recording genuinely disables the track feeding the recorder — the file contains silence for that stretch, not audio that something later chose to hide.
Output dimensions are forced to even numbers, because H.264 rejects odd ones and a Safari recording would otherwise fail at the last moment. Small detail, but it is the kind of thing that turns a finished take into a lost one.
What it does not do
Stated plainly, so you can rule it out quickly if it is the wrong tool.
No screen recording, no window capture and no picture-in-picture layout. Camera and microphone only.
No editing. No trimming, no titles, no timeline. You get one continuous take with the background already in it.
No cloud library. Nothing is stored for you, which is the point, but it does mean a recording you close without saving is gone. There is no copy anywhere to recover it from.
No virtual camera. It cannot feed a processed image into Zoom, Teams or OBS — that needs a device driver, which a web page cannot install.
Which browsers can record
Recording needs a secure connection, getUserMedia, MediaRecorder, canvas capture and a 2D canvas context. Each is probed at runtime, so if one is missing the studio names it rather than failing quietly.
| Browser | Status | Detail |
|---|---|---|
| Chrome and Edge (desktop) | Full support | Records VP9 WebM. GPU edge refinement runs. The combination this is developed against. |
| Firefox (desktop) | Full support | Records VP8 or VP9 WebM depending on version. |
| Safari 16.4 and later | Supported | Records H.264 MP4, because Safari cannot record WebM. Edge refinement runs. |
| Safari before 16.4 | Recording unavailable | Missing canvas.captureStream. The studio says so instead of failing part-way through. |
| Browsers without WebGL2 | Works, softer edges | Falls back to 2D-canvas compositing: correct output, but a visibly softer boundary. |
| Phones and tablets | Works, but demanding | The interface is responsive. Sustained realtime segmentation is heavy on mobile hardware and battery. |
Frequently asked questions
- Do I need to install anything?
- No — no application, no browser extension and no plugin. It uses the recording APIs that are already part of your browser.
- What format is the recording?
- Whatever your browser can actually produce, negotiated rather than assumed. Chrome, Edge and Firefox give a WebM file with VP9 video and Opus audio; VP8 is used where VP9 is not available. Safari cannot record WebM at all, so there it is an MP4 with H.264 video and AAC audio. In every case the file plays in the browser that made it, with no conversion step.
- What resolution and bitrate do I get?
- 720p by default and 1080p where your camera supports it, at roughly 4.5 and 8 Mbit/s respectively, with audio at 128 kbit/s. 720p is the default deliberately: it is the resolution realtime background replacement holds a steady frame rate at on ordinary hardware.
- How long can I record?
- There is no imposed limit. The real one is your own machine: the video is written in one-second chunks that are kept in memory until you save, so a very long session is bounded by available RAM rather than by a rule. For anything past a few tens of minutes, saving in parts is the safer habit.
- Can I record my screen too?
- No. This records your camera, with an optional microphone — screen capture and picture-in-picture layouts are a different tool. If your reason for wanting the screen is a presentation or a demo, a dedicated screen recorder is the right choice; if it is that your room looks bad behind you, that is what the background changer is for.
- Does the recording stop if I switch tabs?
- No. Browsers suspend the animation callback that normally drives the rendering when a tab is hidden, which would leave a recording as a frozen picture over live audio. While a recording is running, a worker-based timer — which browsers do not throttle the same way — keeps the frames coming, so the file keeps its cadence while you are elsewhere.
- Why does my player say the video has no duration?
- It should not, and this is worth explaining because it is a common complaint about browser recordings. A browser records as a live stream, so it writes a file whose end it does not yet know and leaves the duration field empty — which makes scrubbing unreliable and stalls some desktop players. The real length is measured from the clock and written into the file before you save it. Seeking is still approximate, because a browser recording carries no index of keyframe positions; that would need a full re-mux.
- Where exactly does the file go?
- Where you tell it. In browsers with the File System Access API you get a real "save as" dialog and the file is streamed to the location you pick. Elsewhere it falls back to an ordinary download into your downloads folder. Both write straight from memory to your disk.
Related
- Webcam background changerSwap your background for a studio, office or plain backdrop while the camera runs.
- Webcam background removerWhat removing a webcam background can and cannot mean in a browser, and what to use instead.
- Interview video recorderRecord a self-tape or remote interview answer with a background that will not distract.
- How to record a webcam videoFraming, audio, file formats, and the settings worth changing before you hit record.
Record something
Grant camera access once, hit record, and save the file. That is the whole flow.
Open the studio