1Upload every file you want combined — at least two of them.
2Add the files in the order you want them joined; the first file you add comes first.
3Start the merge; the files are joined one after another into a single file.
4Download the single combined WMA file.
Merge WMA 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.
How does Merge WMA 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.
Anything specific to WMA when merging?
+
Yes — WMA tooling outside the Microsoft stack is thin, which is why browser-side work on it is usually more reliable than a desktop app. That is worth checking when the inputs did not all come from the same source.
What can I upload to Merge WMA?
+
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 WMA?
+
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.
Can I run Merge WMA on several WMA audio files at once?
+
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.
Why does a EPUB site host Merge WMA?
+
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 WMA runs on the same upload and the same account as the conversions because that is where it is needed.
What should I do with the result once Merge WMA is finished?
+
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 WMA means the conversion is made from the version you settled on, not from the one you were still fixing.
Is Merge WMA here the same tool the sibling sites run?
+
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.
Do I need an account, and does anything get kept?
+
No account is needed. Uploads and results are kept for about 24 hours, which leaves time to download the result, and are then deleted automatically; nobody reads, lists or indexes them. Several files in one job need a paid plan.
