How MP4 to MP3 Conversion Works in Your Browser

Most converters upload your video to a server. Ours runs FFmpeg in WebAssembly directly in your tab — here's why that matters for your privacy and speed.

The Traditional Approach (and Why It's a Problem)

Most online converters work like this:

You upload your file to their server
Their server runs FFmpeg
They send the result back to you

This means your video file — which might contain personal content — travels to and sits on a stranger's server, even briefly. There's no way to verify it's been deleted.

The WebAssembly Approach

We compile FFmpeg to WebAssembly (Wasm), a low-level binary format that runs in the browser at near-native speed. Your file never leaves your machine.

Your file → FFmpeg.wasm in browser → Output file
                 ↑
         No server involved

What Is FFmpeg?

FFmpeg is the gold standard open-source multimedia framework. It powers YouTube's transcoding pipeline, VLC, and hundreds of professional tools. The same engine that runs on massive servers now runs in your browser tab.

The MP4 Container vs. the Audio Stream

An MP4 file is a container — it holds separate video and audio streams. To get MP3:

FFmpeg reads the MP4 container
It locates the AAC or AC3 audio stream inside
It transcodes (re-encodes) that stream to MP3 at your chosen bitrate

For most use cases, 192 kbps is the sweet spot: transparent quality at a reasonable file size. Go 320 kbps for music production work.

Why Is the First Load Slow?

The FFmpeg Wasm binary is ~30 MB. Your browser downloads and compiles it once, then caches it. Subsequent conversions on the same device are instant.

Browser Requirements

The converter requires:

WebAssembly — supported in all modern browsers since 2017
SharedArrayBuffer — required for multi-threaded Wasm; needs cross-origin isolation

We configure the required Cross-Origin-Opener-Policy and Cross-Origin-Embedder-Policy headers automatically.