FireConvert
5 min read

MP4 to MP3 in your browser — no upload, no watermark

You want to pull the audio out of a video. Every top Google result for "mp4 to mp3" asks you to upload a file. We don't — the conversion runs in your browser. Here's why that matters, and what the quality trade-offs look like.

Why "browser-based" isn't marketing fluff

Most MP4-to-MP3 sites work like this:

  1. You upload your video to their server.
  2. Their ffmpeg extracts the audio.
  3. You download the MP3.
  4. They (hopefully) delete your video.

Step 1 is the problem. A 10-minute 1080p MP4 is typically 100-300 MB. You've just shipped that over the wire to someone you've never met. They have it on disk. Their logs probably contain your IP and filename. Their data retention policy says "30 days" but no one audits that.

Our tool uses ffmpeg.wasm, a WebAssembly port of the same ffmpeg that powers every professional video pipeline. When you drop an MP4:

  1. The ffmpeg code (~25 MB, cached after first load) runs in your browser tab.
  2. Your file is read from your disk — never uploaded.
  3. The audio stream is extracted and re-encoded to MP3 locally.
  4. You download the MP3. We never saw any of it.

Slower on the first visit (because of the ffmpeg download). Faster on every visit after that (browser caches the wasm binary). Private always. Offline after the first load.

The short version

  1. Open MP4 to MP3.
  2. First time only: wait ~10 seconds for the engine to load (one-time; cached after).
  3. Drop your MP4.
  4. Pick a bitrate (192 kbps default — see below).
  5. Click Download.

What the bitrate actually controls

Bitrate measures how many kilobits of audio per second the MP3 stores. Higher bitrate = more data = better fidelity + larger file.

  • 128 kbps — small file, acceptable for spoken-word content (podcasts, lectures). Noticeable compression on music.
  • 192 kbps — our default. Transparent for most listeners on most music. Hits the sweet spot where you can't reliably pick it out in blind A/B tests.
  • 256 kbps — audibly better for trained ears on high-dynamic-range music (classical, well-mixed rock). Most casual listening: indistinguishable from 192.
  • 320 kbps — the MP3 ceiling. Objectively bigger file; subjectively often indistinguishable from 256. Useful for archiving.

Key honesty: you can't add fidelity that wasn't in the source. If your MP4 ships with AAC audio at 128 kbps (common for YouTube downloads and phone recordings), re-encoding to MP3 at 320 doesn't magically upgrade the quality — it just bloats the file while preserving whatever was there. Match the bitrate to the source or go slightly higher if you plan to edit further.

When browser-side doesn't win

ffmpeg.wasm isn't free. Some trade-offs to know about:

  • 25 MB engine download on first visit. Cached by your browser so subsequent conversions start instantly.
  • Single-threaded by default. Our current engine is the single-threaded build because multi-threaded wasm needs special HTTP headers (COOP/COEP) that can break other parts of a site. That's roughly 2-3× slower than a server ffmpeg on the same hardware — but you don't pay the upload-and-download round trip.
  • RAM limit around 2-4 GB depending on browser. For typical MP4s (under 1 GB), fine. For 4K video files over ~2 GB, use a desktop tool instead.

A note on MP4 versus MOV, MKV, WEBM

"MP4" is a container — the outer wrapper around a video stream and an audio stream. MOV, MKV, WEBM, AVI, and 3GP are all different containers. All of them can hold the same audio codecs (AAC, MP3, Opus, etc.). Our tool handles any of those containers — drop a .mov and the audio-extraction path is identical. The output is always MP3.

If your source audio is already MP3 (rare in video containers but possible), we still re-encode to ensure a clean MP3 file with proper frame headers. Slightly wasteful for that one edge case but makes every other path work consistently.

Extracting audio from other formats

Same tool, different inputs:

Common questions

Will this convert YouTube videos?

No. We don't scrape YouTube — that's against their terms of service and most use cases violate copyright. You need an MP4 you already have on disk. Download the video legitimately first (e.g., through YouTube Premium's download feature), then run it through us.

Does this work offline?

Yes, after first load. Visit the tool once to let your browser cache the ffmpeg wasm, then disconnect your wifi and drop a file. The conversion still runs. This is the tangible outcome of "no server in the loop."

How big a file can I convert?

Limited only by your browser's RAM. 2 GB MP4s work on most modern desktops. 4K video files over 2 GB can hit browser memory caps — use a desktop tool (VLC, HandBrake, command-line ffmpeg) if you bump into that.

Does this add a watermark to the MP3?

No. Never. Watermarking audio is a dark pattern, and we don't need to — our business model is paid plans for API + bigger files, not "pay to remove our watermark."

Will the MP3 keep the video's metadata?

We transfer basic ID3 tags when present in the source audio stream (title, artist, album if set). We don't carry over video-specific metadata. If you need rich ID3 tags (album art, lyrics, etc.), run the output through a dedicated tagger like Mp3tag or Kid3 after.

Ready?

MP4 to MP3 →. Your file, your machine, your audio.