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 M4A file.
Merge M4A FAQ
Anything specific to M4A when merging?
+
Yes — an .m4a can hold either AAC or ALAC, so lossy and lossless files share one extension and have to be told apart by inspection. 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 M4A join the files together?
+
Concretely, files that already share a codec, sample rate and channel layout are concatenated by copying the encoded frames, so the join costs nothing in quality; mismatched inputs are decoded and re-encoded once to a common format. 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 M4A cost anything?
+
No. Merge M4A is free without an account and adds no audio watermark or spoken tag to the output. Your upload is deleted from the workers shortly after the job completes.
What can I upload to Merge M4A?
+
MP3, AAC, M4A, OGG, Opus and WMA are the lossy codecs handled directly, and lossless sources (WAV, FLAC, AIFF) can go in the same batch. The codec is probed from the stream, so an incorrectly named file still works.
Is there a file size limit on Merge M4A?
+
Yes: free accounts process audio up to 15 MB per file, which at typical bitrates is several hours of material; ffmpeg does the decoding and encoding, exactly as it would on a desktop. That is the most generous cap on the site after video, and audio work rarely runs into it.
Do tags and cover art survive?
+
Yes. ID3, Vorbis comments and MP4 metadata atoms are carried across, cover art included, so a processed file still sorts correctly in a music library. ReplayGain values are recalculated rather than copied, because a stale one is worse than none.
Why does a MP3 site host Merge M4A?
+
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 M4A 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 M4A 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 M4A rather than before means the encode happens once, on the file you actually settled on, instead of twice.
Is Merge M4A 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.
