Free plan: 1 conversion/hour, 1 file at a time
Go Unlimited →

Merge M4A

Combine M4A audio files in Your Own Order

Settle on your files

*Files deleted after 24 hours

Convert up to 1 GB files free, Pro users can convert up to 100 GB files; Sign up now

Uploading

0%

How to Merge M4A Files

1 Upload every file you want combined — at least two of them.
2 Drag the uploaded items into the order you want; the order is taken from the list, not from the filenames.
3 Start the merge, which joins matching inputs without re-encoding them and reconciles mismatched ones exactly once.
4 Download the single combined M4A file.

Merge M4A FAQ

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.
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.
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.
On the free tier a merge accepts two files at a time, which is deliberately higher than the single-file limit on other tools because merging one file is meaningless. A pass removes the cap entirely.
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.
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.
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.
Yes. Upload the set and they process in parallel with the same settings, which is the practical way to handle a podcast series or an album rather than repeating the job by hand.
EPUB.to is built around the open eBook format — XHTML in a zip, reflowable by design, and readable on hardware nobody has thought about the layout for. A book is a zip full of markup, images and fonts, so almost every job people bring to an eBook site is really a job on one of those things. Merge M4A runs on the same upload and the same account as the conversions because that is where it is needed.
The converter on this site moves books between EPUB, MOBI, AZW3, PDF and DOCX, so a title ends up on whatever hardware is actually going to read it. Doing that after Merge M4A means the conversion is made from the version you settled on, not from the one you were still fixing.
The engines are shared — the same toolchain, the same workers, the same limits. What a EPUB site adds is a view on reflow: which of these operations a reflowable book genuinely supports, and which ones only make sense on the fixed-layout media inside it. It also starts from one fact about the format this site is named after: the book is a zip of XHTML with a manifest, so the text costs almost nothing and every decision that matters is about the embedded images and font subsets.
No account, and nothing is kept: uploads are deleted from the workers shortly after the job finishes, nothing is read and nothing is indexed. Free accounts exist for history and batch size, not for access.

Rate this converter

5.0/5 - 0 votes
ns6.com — Buy your domain in minutes. Search, register, launch.
Or leave your files here