MP3 Joiner — Merge MP3 Files

The naive approach to joining MP3 files — concatenating the raw bytes — actually works for some players but breaks others. Because each MP3 file has its own ID3 header, simply appending the bytes produces a file with embedded headers mid-stream that confuse decoders and cause seek-bar problems, incorrect duration reporting, and playback glitches on some players.

This tool avoids all of that by using FFmpeg's concat filter with full re-encoding. Each input file is decoded to PCM, the raw audio data is concatenated in order, and then the combined audio is re-encoded to a single clean MP3 at 192 kbps with one correct header. The output is a well-formed MP3 that plays correctly in every decoder.

Since MP3 is a lossy format, any join operation requires a re-encode, which introduces one transcoding pass per joined segment. At 192 kbps, this transcoding pass is essentially inaudible — the frequency and dynamic information discarded is below the perceptible threshold on typical headphones and speakers.

The worst case is joining MP3s that were already at a low bitrate (64 or 96 kbps). Re-encoding at 192 kbps doesn't recover the lost quality from the original encode, and the additional pass can add very subtle artifacts at the lowest bitrates. For everyday content (podcasts, voice recordings, music at 128+ kbps source), the join quality is indistinguishable from the source on any standard playback device.

Online joining tools typically upload all your MP3 files to a server — which can be slow, depends on your upload speed, and puts your audio on a third-party server temporarily. This tool uses FFmpeg compiled to WebAssembly to run the entire join locally in your browser. Nothing is uploaded. The browser downloads the WASM bundle once (cached for future visits), reads your MP3 files from local memory, processes them, and returns a Blob for download. This matters for client recordings, pre-release music, NDA-covered content, and anything you'd rather not hand to a stranger's server.