Tool guide
An hour of WAV weighs around 600 MB, which is awkward to send and worse to keep on a phone. AAC squeezes that down by an order of magnitude while staying close to transparent by ear, and it plays on iPhones, Android, car head units and nearly every player. The encoding here is done by MediaRecorder, the recorder built into the browser, so there is nothing to install and nothing to upload. The catch: each browser ships its own codec set. See also: the same AAC inside an M4A container for Apple devices, plain MP3 when AAC will not play everywhere, listen back through your speakers and headphones.
Because MediaRecorder does the encoding, and its codec list depends on the browser, the operating system and licensing. Firefox on Linux usually has no AAC track at all, so the page warns you instead of handing over a broken file. Chrome, Edge and Safari on Windows, macOS and Android handle it in the vast majority of cases.
That is how browser recorders work: the AAC track is wrapped in an MP4 container, whose usual extensions are .m4a and .mp4. The audio inside is identical. Players, phones and editing software all accept it, while a bare .aac elementary stream is rarely useful today.
There is no bitrate control on the page: the recorder applies its own default, typically around 128 kbps for stereo. That is comfortable for speech, lectures and podcasts and borderline for demanding music. When a specific bitrate matters, encode with a desktop tool instead.
The capture happens in real time — the browser literally plays the track into the recorder, so a forty-minute WAV takes about forty minutes. Nothing can speed that up while MediaRecorder is used. Keep the tab in the foreground, since background tabs often have their timers throttled.
AAC is lossy, and what it drops cannot be recovered later. Coming from a clean WAV this is a single encoding generation, so the result normally sounds close to the source on consumer gear. Keep the original WAV: any future format or bitrate should be encoded from it rather than from the AAC.
Entirely. The chosen WAV is read from your file system, playback and capture happen inside the tab, and the finished file appears as a link to an in-memory object. Neither the source nor the result travels anywhere, so private recordings can pass through the page safely.
Before: lecture.wav, 55 minutes, stereo, 580 MB
After: lecture.m4a with an AAC track — about 25 MB, small enough to email or message
Before: demo.wav, 4 minutes, 44.1 kHz, 16-bit
After: an AAC track around 4 MB — plays on an iPhone with no further conversion
Your rating and feedback help decide what to improve next.