Account

What new tool do you want?

Video & Audio

Audio Converter & Video to MP3

Convert audio to MP3 or WAV — M4A, OGG, FLAC, WAV, AAC — and extract MP3 audio from MP4, MOV and WebM videos. Batch convert in your browser.

How to use

  1. 1Add audio or video files.
  2. 2Choose MP3 (and bitrate) or WAV, then press Convert.

Frequently asked questions

Can I extract audio from a video?

Yes — add MP4, MOV or WebM videos and the soundtrack is saved as MP3 or WAV.

Which bitrate should I pick?

192 kbps is great for music; 128 kbps is fine for speech; 320 kbps is the MP3 maximum.

Is there a file size limit?

Only your device's memory. Long videos (over an hour) may be slow on older computers.

How this actually converts audio, without a server

Each file is decoded with the browser's native decodeAudioData (the same engine behind the HTML5 <audio> tag), which is why it accepts almost anything your browser can already play — MP3, WAV, M4A, OGG, FLAC, and the audio track inside MP4/MOV/WebM video files. The decoded samples are then re-encoded with the LAME MP3 encoder running in-browser (loaded on demand only when you pick MP3) or written out as a plain 16-bit WAV. Nothing is uploaded anywhere, which matters if the 'audio' you're converting is actually the soundtrack of an unreleased video.

Why bitrate choice depends on content, not just quality

The bitrate options (96–320 kbps) trade file size against fidelity, but the right choice depends on what's in the recording: 320 kbps is worth it for music with wide dynamic range and cymbals or strings, but a 128 kbps voice memo or podcast episode sounds indistinguishable from 320 kbps to most ears while taking less than half the space. The Mono checkbox goes further for speech-only content — halving the file size again by averaging left and right channels into one, which is invisible for a single speaker but destroys stereo separation in music.

Worked example: pulling MP3 audio out of a phone-recorded MP4

A 4-minute MP4 video recorded on a phone, used only for its interview audio: dropping it in and choosing MP3 at 128 kbps mono produces a file around 4 min × 60s × 128 kbps ÷ 8 ÷ 1000 ≈ 3.8 MB — versus roughly 9.2 MB at stereo 192 kbps for the same clip — with no audible difference for a single voice track, since there was never a stereo image to lose in the first place.

Where this differs from a desktop tool

Because conversion runs in the tab rather than shelling out to a native encoder, very long source files (an hour-plus lecture recording, for instance) are decoded entirely into memory before encoding starts, so older or memory-constrained devices will be slower than the same job in Audacity or ffmpeg on the command line. For typical clips under 10–15 minutes the difference isn't noticeable, and batch conversion still works — the trade-off only shows up at the long-form end.

Mono here means averaged, not a channel dropped

Some converters make 'mono' by simply discarding the right channel and keeping only the left — which loses anything mixed exclusively to the dropped side, a real risk with two-person interviews recorded on separate hard-panned mics. This tool instead averages every sample pair, (left + right) / 2, so content unique to either channel survives in the combined signal rather than being thrown away. It's still a real mono file at half the stereo size, but nothing recorded on the 'wrong' channel goes missing.

WAV's size is predictable — and that's the trade-off

WAV here is uncompressed 16-bit PCM, so its size is just sample rate × channels × 2 bytes × duration: a 4-minute stereo 44.1 kHz recording comes out to roughly 40 MB, against about 5.5 MB for the same clip at 192 kbps MP3 — a 7x difference for audio most listeners can't tell apart. WAV earns its size when the file is headed into further editing (no generational loss from repeated decode/encode passes) or an archive; MP3 is the right default for anything just going to a phone, a podcast feed, or cloud storage where space costs something.

Related tools

More: Video & Audio