Convert Video to MP3

Extract MP3 audio from MP4, MOV, MKV, WEBM, AVI, 3GP and MTS video in your browser. Free and private, with no upload and no size limit.

🌐 Español

Drop your file here (.mp4, .m4v, .mov, .mkv, .webm, .avi, .3gp, .mts, .m2ts)

🔒 Private by design: your files are processed locally in your browser and never uploaded to any server.

Whatever the camera wrote, one audio track out

Most “video to MP3” pages accept MP4 and shrug at everything else, which is unhelpful, because real video arrives in whatever format the device that made it preferred. A phone shoots MOV or MP4. A download is often MKV or WEBM. A camera from ten years ago wrote AVI. A camcorder wrote MTS or M2TS. An old handset wrote 3GP.

This page accepts all of those: .mp4, .m4v, .mov, .mkv, .webm, .avi, .3gp, .mts and .m2ts. Anything outside that list is refused by the dropzone with an unsupported-type message before any processing begins, which is better than a failure five minutes into a run.

What happens next is the same regardless of which one you brought. The video stream is discarded, one audio stream is picked by FFmpeg’s own default selection and decoded, and the result is encoded to MP3. Because video is the overwhelming majority of the bytes in any of these files, the output is dramatically smaller than the input, and the page reports both sizes when it finishes.

The extension picks the demuxer FFmpeg reaches for

There is a small design decision inside this tool that the single-format converters on this site do not need. FFmpeg decides how to parse a file partly from its filename, so a converter that only ever sees one format can hand every file over under one fixed name. This one cannot, because naming an MKV as though it were an MP4 would point the wrong parser at it.

So the module keeps a lookup table of the accepted extensions, lowercases whatever you dropped, and writes the file into FFmpeg’s virtual filesystem under a matching name. The table carries an .mp4 default for anything it does not recognise, but nothing ever reaches that branch in practice, because the dropzone has already refused every file whose extension is not on the accepted list.

Pulling the audio out of a video

  1. Drop your video onto the box above, or click Choose a file and pick it. The accepted extensions are printed inside the dropzone itself, in brackets on the Drop your file here line.
  2. Choose an Audio quality. 192 kbps (recommended) is the default and suits nearly everything; take 320 kbps (highest quality) for music.
  3. Click Convert Video to MP3. A progress bar and a Cancel button replace the button while FFmpeg decodes and encodes.
  4. Download the MP3, which keeps the video’s filename with the extension swapped.

A video with no audio track, and what that looks like

The output arguments sent to FFmpeg begin with -vn, which drops every video stream so that only audio reaches the encoder. That is exactly what you want, and it has one consequence worth knowing about: if the file has no audio stream either, there is nothing left to write.

Silent screen recordings, muted phone clips and some exported timelapses fall into that category. The run ends with the page’s generic message, Something went wrong while processing your file. Please check the file is valid and try again., because no output file was ever produced for it to hand back. It is not a bug and no bitrate setting changes it. If a video genuinely should have sound and does not, the problem happened at recording time.

Always a re-encode, never a stream copy

Some videos already carry MP3 audio, particularly older AVI files, and in principle the audio could be copied out untouched. This tool does not do that. It always decodes and re-encodes through libmp3lame at the bitrate you chose.

The honest cost is a second lossy pass. Video audio is almost always AAC or Opus already, so a re-encode is unavoidable in the normal case anyway, and a consistent, predictable output is worth more than saving a generation of quality in the minority of files where a copy would have worked. It does mean that extracting audio at 320 kbps from a video whose soundtrack was 96 kbps AAC produces a large file carrying a small amount of information.

If you want to keep the video as well as the audio, converting the container is a separate job: MKV to MP4 tries a stream copy first and falls back to an H.264 and AAC re-encode when the copy fails or when you pick that mode yourself, and the video converter and compression tools guide covers the rest of that side.

MTS, M2TS and the camcorder cases

The two extensions people least expect to work are the AVCHD ones. Consumer camcorders from roughly 2007 onwards wrote MPEG transport streams to their internal cards, split across numbered files in a BDMV or AVCHD folder structure, usually with Dolby Digital audio alongside H.264 video.

Those files are supported here directly, which matters because they are frequently the last surviving copy of a wedding, a recital or a family holiday, and the software bundled with the camera stopped running several operating systems ago. The audio comes out as a normal MP3 that anything will play.

Transport streams are also large, and the whole file has to be read into the tab before decoding starts. If a long recording fails partway, memory is almost always the reason, and nothing here trims an MTS directly: Trim Video takes MP4, MOV, M4V and WEBM only. MTS to MP4 rewraps the stream into a container that trimmer accepts, usually with a stream copy rather than a re-encode.

Bitrate for a lecture against a concert recording

The three rungs map to one FFmpeg argument each. 128 kbps (smaller file) is right for speech: lectures, meetings, webinars, interviews, anything where the content is a person talking and the file is going to a phone or a transcription service. 192 kbps (recommended) is the default and handles mixed material without thinking about it.

320 kbps (highest quality) is worth it when the soundtrack is music you intend to listen to properly, such as a concert recording or a music video, and it is wasted when the source audio was heavily compressed to begin with. If your file happens to be an MP4 and you landed here by accident, MP4 to MP3 does exactly the same thing from a page written for that one case, and the wider audio tools handle trimming and levelling once you have the MP3.

Frequently asked questions

My screen recording has no sound and the extraction fails. Why not an empty MP3?

Because there is nothing to write. The command asks for audio only, so a video with no audio stream leaves FFmpeg with no output to produce, and the page reports its generic processing failure rather than handing you a zero-length file. Silent screen recordings and muted phone clips are the usual causes, and there is no setting that changes it.

I have a .flv, .wmv or .vob file. Can I use this page?

Not directly. The accepted list is fixed, and anything outside it is refused with an unsupported-type message before any work starts, because the module needs to name the file correctly for FFmpeg to choose the right parser. No page here converts those three either, so making an MP4 first needs desktop software such as VLC or HandBrake.

Does the whole video have to fit in memory just to get the audio out?

Yes, and it is the main practical limit here. The file is written into FFmpeg's virtual filesystem inside the tab before decoding starts, so a multi-gigabyte film needs room for itself and for the MP3 alongside it. Trimming the section you want first is the usual fix when a long file fails partway.

The video has two audio tracks, a commentary and the original. Which one do I get?

Whichever one FFmpeg's automatic stream selection picks, which is the track with the most channels rather than simply the first, and there is no picker on this page to choose otherwise. If the wrong language or commentary comes out, deleting the unwanted track in a container editor before extracting is the workaround.

Is this any different from the dedicated MP4 to MP3 page?

For an MP4 the result is identical, since both run the same encoder with the same arguments. The difference is only in what each page will accept, since this one takes a much wider list of containers so that a MOV from a phone or an MTS from a camcorder works without hunting for the right converter first.

Related tools