Why this is fast
Native server ffmpeg with real SIMD, multi-threading, and disk I/O is roughly 4–8x the throughput of browser WebAssembly on the same job. Uploads land at the nearest Backblaze B2 point of presence via a presigned URL, so a viewer in São Paulo is not pushing bytes to US-east, and the finished MP3 is delivered through Bunny CDN from the same edge. Even a multi-hour FLAC archive usually finishes inside the time the upload took.
What this tool does, exactly
We run ffmpeg -i input -vn -c:a libmp3lame -q:a 2 -f mp3 output.mp3 on the server. -vn drops any video stream (some inputs carry album art), the LAME encoder re-encodes at VBR quality 2 (~190 kbps average), and the output is a standard MP3 every player understands. The accepted MIME list covers MP3, MP4/M4A, AAC, WAV/WAVE, OGG, FLAC, Opus, WMA, AIFF, and even webm-container audio — if ffmpeg can decode it, this tool accepts it.
Why the output is MP3
audio-converter writes MP3, the format every player understands. It accepts a wider range of inputs than the MP3 converter, and both pages produce the same byte-for-byte output.
Sister tools
Specifically converting an Apple file? M4A to MP3 converter. Pulling audio out of a video? Video to audio converter and MP4 to MP3 converter. Trim the MP3 down? MP3 cutter. Make it smaller for email or Discord? Compress audio. Clean up hiss and fan noise? Remove background noise.