How to combine MP3 files into one

By Filewhisk Team Published

The quick ways to join MP3s, what copy /b gets wrong with some files, and what to do about the tiny gaps.

Audiobook chapters, a lecture recorded in parts, a voice memo that stopped halfway, a playlist you want as one file for the car: sooner or later you have a folder of MP3s that should be a single MP3. It's one of the few audio jobs that can be done with no quality loss at all, because an MP3 is just a long run of small, separate frames. Done carelessly, though, the joined file can show the wrong length, carry the old song titles in the middle of the sound, or click at every join.

We tested the common ways on 13 October 2026 on Windows 11 with Chrome 154, using a 20-second test recording split into three MP3s (7, 6 and 7 seconds), once at a constant bitrate and once at a variable bitrate. The Mac and phone steps come from Apple's apps and user reports, not from our own devices, and we say so where that's the case.

The quick answer

Where you areEasiest wayWatch out for
Any device with a browserMerge MP3: drop the files, check the order, downloadNothing to install; files aren't uploaded
Windows, from the command linecopy /b part1.mp3+part2.mp3 all.mp3Wrong length on variable-bitrate files; tags left in the middle
Mac, from Terminalcat part1.mp3 part2.mp3 > all.mp3The same file as copy /b, so the same problems
Mac, QuickTime PlayerOpen the first file, Edit > Add Clip to End, then File > Export As > Audio OnlyGives an M4A, not an MP3; not tested by us
iPhone or AndroidThe browser tool above, in Safari or ChromePhones have no built-in way to join audio files

What copy /b really does, and where it goes wrong

The old Windows trick is to glue the files together byte for byte from a Command Prompt opened in the folder:

copy /b part1.mp3+part2.mp3+part3.mp3 all.mp3

It works because players simply read one MP3 frame after another. We ran it on both sets of test files and checked what Windows and Chrome made of the results:

Joined with copy /bReal lengthFile Explorer "Length"Chrome's player
Three constant-bitrate (128 kbps) MP3s20 s00:00:2020.15 s
Three variable-bitrate MP3s20 s00:00:0718.34 s

With constant-bitrate files nothing visible goes wrong. With variable-bitrate files, which many encoders and most audiobook rips use, Windows showed only the first part's length, and Chrome guessed 18 seconds for a 20-second file. The cause is a small information block at the start of every MP3 that states how long it is. After a plain join the first file's block is still at the front, describing only the first file. Players that trust it show the wrong length, and the progress bar no longer matches what you hear.

Two smaller leftovers come along too. Each file's title, artist and cover picture are stored at its start, so the tags of parts two and three now sit in the middle of the sound; most players skip them, but they add to the size, and a big cover picture repeated per chapter can add megabytes. And every join keeps a short stretch of encoder silence, which we come to below.

How to tell which kind you have: right-click the file in File Explorer, open Properties > Details and look at Bit rate. If parts of the same recording show different, odd-looking rates (48, 45, 43 kbps in our test), they are variable-bitrate files, and copy /b will give them the wrong length.

Joining them properly

A proper join does the same byte-for-byte copy of the sound, but drops the old information blocks and the tags of the later files, then writes one new block for the whole file. That's what Merge MP3 does in its default mode. Our variable-bitrate test files, joined that way, showed 00:00:20 in File Explorer and 20.06 seconds in Chrome. The audio frames are copied unchanged (we checked them byte for byte on the constant-bitrate set) and nothing is encoded again, so the quality is exactly what you started with.

  1. Open Merge MP3 and drop all the files at once.
  2. Check the order. Files are sorted by name the way people count, so chapter 2 comes before chapter 10, which plain alphabetical sorting gets wrong. Drag a file to move it.
  3. Download the joined MP3. It keeps the first file's title, artist and cover.

Everything happens in the browser, so it works the same on Windows, a Mac, a Chromebook, an iPhone or an Android phone, and private recordings don't leave the device.

The tiny gap at each join

Every MP3 encoder adds a few dozen milliseconds of near-silence at the start and end of a file, and notes how much so that players can skip it. Players only skip it at the very start and end of the file they're playing. When files are joined without re-encoding, the silence at each join stays: in our test the two joins were 27 and 35 milliseconds long.

Between audiobook chapters, songs or lecture parts nobody hears that; a narrator pauses longer between sentences. It matters when one continuous recording was cut into pieces, such as a live concert, a DJ mix or an interview that the recorder split every hour: then the gap can be heard as a tiny hiccup in the middle of a sound. For that case, choose Seamless in the tool. Each part is decoded without its encoder silence, the parts are laid end to end, and the whole is encoded once. In our test both joins then landed on exactly the right sample and the file was 20.00 seconds long. The cost is one re-encode, which at the same bitrate is very hard to hear.

On a Mac without extra apps

Terminal's cat part1.mp3 part2.mp3 part3.mp3 > all.mp3 produces exactly the same bytes as copy /b (we compared the two on Windows), so it has the same length problem with variable-bitrate files.

QuickTime Player can join audio too: open the first file, choose View > Show Clips, then Edit > Add Clip to End for each next file, and finish with File > Export As > Audio Only. That last step saves an M4A file, not an MP3, and re-encodes it. This route comes from Apple Community answers rather than our own Mac, and one user there reported that a clip added this way lost its sound, so play the result through before deleting the parts.

Audiobooks: one file or chapters?

Many people join audiobook chapters so that a car stereo or an old player doesn't jump to the next file, or so a phone app remembers one position instead of fifteen. A single MP3 does that, but MP3 has no widely supported chapter markers, so the chapter breaks are gone. If you listen in Apple Books or another app that reads chapters, keep the separate files, or look for an M4B, the audiobook format that stores chapters inside one file.

A long audiobook also gets big. If the joined file is too large for a phone or an upload, the MP3 compressor can bring it to 64 kbps mono, which is clear for a single voice and takes about 0.48 MB per minute. Many audiobook rips also carry a cover picture in every chapter; the joined file keeps only one, and the compressor can shrink that one without touching the sound.

Common questions

Will joining MP3s lower the quality? Not if they are joined without re-encoding, which works whenever the files share a sample rate and are all mono or all stereo. Different bitrates are fine.

Can I join MP3s with different sample rates, such as a voice memo and a song? Only by re-encoding, because a single MP3 stream can't change its sample rate halfway. The merge tool does that automatically and says why.

How do I cut a part out before joining? Use Trim audio on that file first. It trims MP3s without re-encoding as well, so the join stays lossless.

Tools used in this guide