1Upload every file you want combined — at least two of them.
2Drag the uploaded items into the order you want; the order is taken from the list, not from the filenames.
3Start the merge, which joins matching inputs without re-encoding them and reconciles mismatched ones exactly once.
4Download the single combined Audio file.
Merge Audio FAQ
Anything specific to Audio when merging?
+
Yes — the codec is detected from the stream, so a mislabelled extension does not derail the job. That is worth checking when the inputs did not all come from the same source.
Is the merge lossless?
+
It is whenever the inputs already agree — the encoded data is copied straight through. It stops being lossless only when the inputs disagree and something has to be re-encoded to make them compatible, and even then it is one pass, not one per file.
How does Merge Audio join the files together?
+
Concretely, matching inputs are concatenated by copying encoded frames and mismatched ones are normalised once, so the join is as cheap as the source material allows. Upload everything you want combined and the result comes back as a single file.
Can I control the order things are joined in?
+
Yes — drag the uploaded items into the order you want before starting. Order is taken from the list, not from the filenames, so "IMG_2.jpg" sorting after "IMG_10.jpg" is not a problem you have to solve first.
Does Merge Audio cost anything?
+
No. Merge Audio is free with no account, and nothing is added to the audio. Uploads are deleted from the workers shortly after the job completes.
Which audio formats does Merge Audio accept?
+
MP3, WAV, AAC, M4A, FLAC, OGG, Opus, WMA and AIFF. Codecs are detected from the stream rather than the extension, so a mislabelled file still works and a mixed batch is handled per file.
Is there a file size limit on Merge Audio?
+
Yes: free accounts process audio up to 15 MB per file whichever codec you brought; ffmpeg handles the decode and encode. In practice that limit only bites on uncompressed WAV; a compressed file of the same length is nowhere near it.
Do tags and cover art survive?
+
Yes — ID3, Vorbis comments and MP4 atoms are carried across along with embedded artwork, so processed files still sort correctly in a music library.
Why does a MP3 site host Merge Audio?
+
MP3.to is built around the format that made portable audio ordinary: universally playable, small enough to ignore, and lossy in a way that only matters if you keep re-encoding it. Audio jobs cluster: the same person who needs a format changed usually needs the file cut, levelled or made smaller in the same sitting. Putting Merge Audio behind the same upload, the same caps and the same account is what turns three tabs into one.
What should I do with the result once Merge Audio is finished?
+
The converter on this site moves audio between MP3, WAV, FLAC, M4A, OGG and Opus, so the output format is a decision you can leave until the end rather than commit to at the start. Doing that after Merge Audio rather than before means the encode happens once, on the file you actually settled on, instead of twice.
Is Merge Audio here the same tool the sibling sites run?
+
The engines are shared — the same ffmpeg build, the same workers, the same limits. What a MP3 site adds is a point of view about bitrates, about what survives an encode and about when a lossless intermediate is worth the upload time. It also starts from one fact about the format this site is named after: MP3 frames are fixed-size blocks, so a cut lands on a frame boundary and gapless playback markers do not survive a re-encode.
Do I need an account, and does anything get kept?
+
No account, and nothing is kept: uploads are deleted from the workers shortly after the job finishes, nothing is listened to and nothing is indexed. Free accounts exist for history and batch size, not for access.
