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
Does it matter if the inputs are different formats?
+
It does. M4A is an MP4 container holding AAC or ALAC audio — the default for iTunes and Apple Music files. Matching inputs take a fast, lossless path; mismatched ones have to be reconciled to a common format, which is slower and costs one encode.
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.
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.
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.
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 200 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.
Will Merge M4A lower the quality of my M4A audio files?
+
A lossy file has already discarded detail once, and re-encoding discards more — that is generation loss and it does not undo. Wherever the job can be completed by copying the encoded stream rather than re-encoding it, that is what happens, and the audio comes back bit-identical.
Why would a modern-format site run Merge M4A?
+
WEBP.to is built around the modern replacement for both of the old defaults: one format that does lossy, lossless, alpha and animation, and reliably lands smaller than the JPEG or PNG it came from. People arrive here having decided the old defaults are costing them bandwidth, and that decision immediately raises the rest: what size, what quality, what happens to the transparency. Merge M4A is on the same upload and the same account so those questions get answered in one place.
Once Merge M4A has run, what is worth doing next?
+
The converter on this site moves images to and from WebP, PNG, JPG and AVIF, which is where you decide whether a smaller file is worth losing the older browsers. Doing it in that order matters: pick the pixels first and the container afterwards, because the container is the cheap decision and the pixels are the expensive one.
Do the sibling sites run something different?
+
The engines are identical — same libraries, same workers, same caps. What is different is the opinion attached, and the opinion here rests on a property of the format this site is named after: the same .webp extension can hold a lossy VP8 frame, a lossless one, or an animation, so the sensible processing path is decided per file rather than per extension.
What happens to my file, and is an account required?
+
No account, and nothing is retained: uploads are deleted from the workers shortly after the job finishes, and nothing is inspected, listed or indexed. Accounts exist for history and batch size only.
