Convert MP4 to MP3
FFmpeg Online — Run FFmpegin Your Browser
Convert your MP4 file to MP3 right in your browser. Nothing is uploaded, nothing is installed, and your files never leave your device.
Convert, compress, trim, and process video & audio locally. Files never leave your device. No signup. The real FFmpeg.- 100% private — nothing is uploaded
- Free, no account
- Real FFmpeg — any command runs
Convert MP4 to MP3 — tool
Loading the tool…
What this does
This tool converts MP4 files to MP3 in your browser. It runs the real FFmpeg, compiled to WebAssembly, right inside your browser — nothing is installed, no account is needed, and your files are never uploaded to a server. Add a MP4 file, press Run, and download the MP3 — the output matches what you would get from FFmpeg on the command line.
About the formats
MP4 is the most widely used video format.
The result is a 192 kbps MP3 that plays on practically any device.
The FFmpeg command
This is the exact command the tool runs for you. Copy it to run the same conversion with FFmpeg on your own machine.
ffmpeg -i input.mp4 -vn -c:a libmp3lame -b:a 192k output.mp3 What happens to your MP4
The tool reads the sound track inside your MP4, leaves the video out, and encodes the audio as MP3. Your original file is not changed, and nothing is uploaded: the conversion runs in your browser tab.
The whole file is converted, start to finish. If the MP4 has no sound track (some screen recordings don't), the tool tells you instead of making an empty MP3.
Choosing a bitrate
Bitrate sets the quality and the size of the MP3. 192 kbps is the default and sounds good for music; for talks and voice, 96–128 kbps is plenty and makes much smaller files. A higher bitrate can't add quality the MP4's audio didn't have, so going above the source rarely helps.
| Bitrate | Size per minute | Good for |
|---|---|---|
| 96 kbps | ≈ 0.7 MB | Speech, voice notes |
| 128 kbps | ≈ 1 MB | Podcasts, lectures |
| 192 kbps (default) | ≈ 1.4 MB | Music, most uses |
| 256 kbps | ≈ 1.9 MB | Music from a high-quality source |
MP3 here is constant bitrate, so size depends only on bitrate and length.
Same commands. No limits.
Test in your browser free — run at scale on Rendi's FFmpeg API. n8n, Zapier & Make integrations.
Frequently asked
Will the MP3 sound as good as the MP4?
Very close. The audio in an MP4 is usually already compressed (often AAC), so converting to MP3 is a second compression step. At 192 kbps or higher, most people can't hear a difference.
How big will the MP3 be?
About 1.4 MB per minute at the default 192 kbps: a 4-minute song is around 6 MB and a one-hour recording around 86 MB. Lower the bitrate for smaller files.
Can I convert a long MP4, like a full lecture or podcast?
Yes. Pulling out the audio is far lighter than processing video, and the result is small. Very large files are limited by your browser's memory, which is lower on phones.
My MP4 has no sound. What happens?
If the file has no audio track, there is nothing to convert, and the tool says so instead of creating a silent MP3.
Is it really private?
Yes. FFmpeg runs entirely in your browser via WebAssembly. Your files are never uploaded, streamed, or seen by any server — including ours.
What's the file size limit?
Around 2 GB, and it's a browser limit rather than ours. WebAssembly can only address so much memory, so the whole job has to fit in the tab. Lightweight operations that copy streams instead of re-encoding (trimming, remuxing, stripping the audio track) work on files right up near that ceiling, because the file is read in place instead of being copied into memory. Full re-encodes need room for the input, the output, and working memory at once, so their practical ceiling is lower — lower still on phones. For anything bigger, the exact same command runs with no size limit on the Rendi API.
Does it work on my phone?
Yes. It's a web page, so it opens in Safari or Chrome on a phone the same way it does on a laptop: nothing to install, and your files still never leave the device. The layout is built for touch, and the Run button stays pinned to the bottom of the screen while you work. What changes on a phone is memory — there's much less of it, so the size limits are halved: the tool stops at files over about 1 GB, and it refuses re-encodes over 500 MB instead of letting the tab crash mid-run. Trimming, remuxing and extracting audio stay cheap, so those are the jobs a phone handles best. For a long video or a heavy encode, send the same command to the Rendi API; that works from a phone just as well.