Video to MP3

ffmpeg.wasm encodes the audio track to MP3 inside your browser — no upload, no server.

How Video to MP3 works

Extract a real MP3 audio file from any video. ffmpeg.wasm encodes the audio track to MP3 inside your browser — no upload, no server. Everything happens inside this page: the tool reads your input, runs the calculation or conversion locally, and hands the result back to you. Nothing is transmitted, because there is no backend to transmit it to.

That design choice is deliberate. Most free tool sites upload your files to a server, process them there, and quietly keep a copy. Toolcin cannot do that — the site is a set of static files. If your connection dropped the moment the page finished loading, every tool would still work.

What the encoder is doing

The tool runs ffmpeg compiled to WebAssembly inside the page, with the LAME MP3 encoder built in. It reads your video, discards every video stream, and encodes the audio to MP3 at variable bitrate quality level 4 — roughly 165 kbps for typical speech and music, which is transparent for most listening.

Because nothing is uploaded, the file size limit is your device's memory rather than a server quota. A 200 MB video is fine on a desktop and risky in a mobile browser tab.

The first run downloads the engine

Encoding needs about 31 MB of WebAssembly before it can start: the ffmpeg core, the worker and the codec bundle. That download happens once per browser profile and is then cached, so the second conversion starts almost immediately.

The progress line reports the engine download separately from the encode. If it appears stuck at the start, that is the download, not the encode — on a slow connection it can take a minute.

Speed, heat and battery

WebAssembly runs on your CPU, not on a GPU and not on a server. A one-minute clip typically encodes in well under a minute on a laptop; a one-hour lecture can take longer than listening to it. The tab must stay open, and a phone will get warm.

If the tab is backgrounded, browsers throttle timers and the encode may slow down or stall. Keep the tab visible until the download starts.

When the audio track is the problem

Not every video contains audio. A screen recording with the microphone muted, or a clip whose audio track uses an unusual codec, will produce an MP3 that is either silent or fails outright. The status line reports the failure rather than handing back a broken file.

Multi-track videos — a film with several language tracks — expose only the default track to this command, because no stream mapping option is passed. Choose the track in a desktop editor if you need a specific one.

Good to know

  • Works offline once loaded, including on flights and in locked-down networks.
  • No file size limit beyond your device's own memory.
  • Free to use, with no account and no usage counter.
  • Results are produced locally, so they are not logged or shared with anyone.

Questions

Is my video uploaded?

No. ffmpeg.wasm downloads once (about 31 MB) and then converts the file inside your browser.

Why is the first conversion slow?

The engine and its WebAssembly core must download before encoding starts. Later runs use the browser cache.

Does it keep the original audio quality?

It re-encodes, so it is not lossless. Quality level 4 is high enough that the difference from the source is hard to hear, but a second re-encode of the same file will degrade further.

Why is the MP3 sometimes larger than the video?

A short, heavily compressed video can carry a high-bitrate audio track. MP3 at fixed-ish quality does not know the source was already small.

Video and audio tools

Keep going

More files tools