Record from your microphone and download the result. Pause and resume, pick which input to use, and watch a level meter that shows the peak of each frame rather than a sliding average — because an average is too slow to warn you that you are clipping, which is the one thing a meter is for. The recording stays in your browser: nothing is uploaded, and navigating away discards it. Download it as WebM, which is what was actually recorded, or as WAV if something downstream insists on it.
| Format | Size | What it is |
|---|---|---|
| WebM / Opus | ~1 MB per minute | What was actually recorded |
| WAV 16-bit | ~10 MB per minute | Decoded and rewritten as PCM |
| Clipping | — | Not recoverable — watch the meter |
No. It exists as a blob in the page and as whatever you choose to download. Navigate away and it is gone — there is nowhere for it to have been stored.
Because there is no way to record without it, and the browser requires your explicit consent. It is requested when you press record rather than on page load, and the stream is released when you stop, so the browser's recording indicator goes out.
WebM is what was actually recorded — compressed with Opus, small and good quality. WAV is that recording decoded back and rewritten as uncompressed PCM, so it is much larger and not better; it exists because some tools accept nothing else.
Yes. Above the top the waveform is being clipped, which sounds like distortion and cannot be undone afterwards. Move further from the microphone, or turn down the input gain in your system settings. The meter shows peaks rather than an average so that this is visible before the recording is ruined.
Yes, where the browser supports it. Pausing keeps everything recorded so far and resumes into the same file rather than starting a new one.
Long. Data is collected in timed chunks rather than as one growing allocation, so length is limited by available memory rather than by a fixed cap. Very long recordings are still worth downloading promptly.
Browsers only reveal device names after permission is granted, so the list fills in once you have allowed access. If a device is still missing, it is not reaching the browser — check the system sound settings.
No. Microphone access requires a secure context, so the page must be on HTTPS or localhost. That is a browser rule, not one here.
Recording is MediaRecorder over a getUserMedia stream, and the container is probed rather than assumed: the supported types differ by browser and platform, and asking MediaRecorder for one it does not support throws rather than falling back, so the preference list is tested in order and the first that works is used. WebM with Opus is preferred because it is small and widely supported; Safari gets MP4. The level meter runs off an AnalyserNode on the same stream and reports the peak of each frame rather than the average, because an average moves too slowly to show you that you are clipping, which is the one thing a meter exists to tell you before rather than after. Data is collected in timed chunks rather than in one lump at the end, so a long recording is not a single growing allocation and a crash loses a second rather than everything. The WAV conversion decodes the recorded blob back to raw samples and re-encodes them as PCM — worth being clear about, since that means WAV output is a decode of Opus rather than a lossless original: it is larger than the WebM and not better than it, and it exists because some tools will not accept anything else. The microphone permission is explained before it is requested rather than prompting on page load, and the stream's tracks are stopped when recording ends so the browser's recording indicator goes out rather than staying lit. Nothing is uploaded — the recording exists as a blob in the page and as whatever you download, and navigating away discards it.