Voice recorder
Record from your microphone in this tab and save it as MP3 or WAV. No app, no account, and the audio never leaves the machine.
How to record audio in the browser
- 1
Allow microphone access
The browser asks once. The level bar starts moving straight away, so you can check you are audible before recording anything.
- 2
Click Record, then Stop when done
Pause and resume as often as you like. Play the take back before you commit to it.
- 3
Pick a format and download
MP3 for something you will send, WAV for something you will edit further.
The level bar is there before you press Record
The single most common way a recording is wasted is not noise or clipping. It is discovering afterwards that the wrong input was selected and the file is forty minutes of silence. So the meter starts as soon as access is granted, before anything is being captured. Say something; if the bar does not move, the microphone in the selector is not the one you are talking into. The bar is on a logarithmic scale, because ordinary speech sits around −25 to −15 dBFS and a linear meter would spend its whole life pinned near zero.
Why the recording is always mono
A single microphone produces one signal. Saving it as stereo does not add anything — it writes the same waveform into two channels and doubles the size of the file for no gain whatsoever. Everything recorded here is saved as one channel, which is also what every transcription tool and every voice-note player expects.
MP3 or WAV
WAV is the raw samples with a 44-byte header: nothing is thrown away, the file is large, and the browser can write it on its own without downloading anything. MP3 is roughly a tenth of the size at 128 kbps, which is more than enough for speech, but it needs the audio engine, about 8 MB, fetched once and cached afterwards. If you are going to edit or transcribe the recording, take the WAV. If you are going to send it to somebody, take the MP3.
HTTPS is not optional
Browsers only expose microphone access on a secure origin, over HTTPS or on localhost during development. On a plain HTTP page the interface that would ask for permission does not exist at all, which is a deliberate decision by browser vendors rather than a limitation here: a page that can silently listen has to be one you can at least verify the identity of.
Where the recording goes
Nowhere. The audio is captured into memory in this tab, encoded in this tab, and handed to you as a download. There is no upload step, no server-side processing and no copy left behind. Closing the tab discards everything that was not saved. The one-hour limit on a single take comes from memory, not policy: uncompressed audio is about 10 MB per minute, and an hour is already close to what a phone browser will hold.
Recorded and encoded in your browser
The microphone stream is recorded, metered and encoded to MP3 or WAV inside this tab, with echo cancellation and noise suppression done by your browser itself. Nothing is sent anywhere until you save the file yourself: there is no account, no queue and no copy on a server, and closing the tab clears everything.
Frequently asked questions
Do I need to be online while recording?
Only to load the page, and to fetch the audio engine once if you save as MP3. Recording itself and saving as WAV work with the network switched off.
Where does my recording go?
It stays in this tab until you download it. Nothing is uploaded, and closing the tab discards whatever was not saved.
Why does this need HTTPS?
Browsers only expose the microphone on a secure origin. On a plain HTTP page the permission interface does not exist at all.
Can I pause a recording?
Yes. Pause and resume as often as you like; the timer stops and starts with it.
Should I choose MP3 or WAV?
WAV if you will edit or transcribe it, since nothing is thrown away. MP3 if you will send it, at about a tenth of the size.
Why is the recording mono?
One microphone produces one signal. Writing it into two channels doubles the file without adding a single new sound.
My microphone is not listed. What now?
Device names only appear after you grant access, so allow the microphone first. If the list is still empty, the browser found no input device at all.