Audio Joiner

By Asira Tools Team · Last updated 20 November 2026

Merge several audio files into one — podcast parts, split recordings, or audiobook chapters — free, in your browser, with nothing uploaded.

Advertisement

Audio Joiner

Drop audio files here or click to choose them

No files chosen yet. Choose at least two audio files, in the order you want them joined. Maximum 2 GB total.

Choose at least two audio files to join them
Input files—
Output file—

Your audio never leaves your device — joining runs entirely in your browser. The first join loads the converter (about 30 MB); later joins start right away.

Command used (two files, MP3 output):

ffmpeg −i input0.mp3 −i input1.mp3 −filter_complex "[0:a]aresample=44100[a0];[1:a]aresample=44100[a1];[a0][a1]concat=n=2:v=0:a=1[out]" −map "[out]" −c:a libmp3lame −q:a 2 output.mp3

Each input is resampled to 44,100 Hz first, so files recorded at different sample rates join cleanly.

What Does an Audio Joiner Do?

An audio joiner merges several audio files into one. Two halves of a recorded interview become a single interview. Three podcast segments become one episode. The chapters of an audiobook become one long file you can listen to without stopping. The files are joined end to end, in the order you choose them, and the result is a single MP3 or WAV file with the same sound quality as the inputs.

Joining is different from mixing: the files play one after another, not on top of each other. There is no overlap, no crossfade, and no background music — just the first file, then the second, then the third, exactly as if they had been recorded as one. That simplicity is the point: joining is the tool for putting split recordings back together.

How to Use This Joiner

Drop two or more audio files onto the upload area, or click it and select several files at once (hold Ctrl or Command while clicking to select more than one). The tool accepts MP3, WAV, M4A, OGG, FLAC, AAC, Opus, WMA, and AIFF files, and the files can be in different formats — an M4A intro and a FLAC main recording join just fine. The chosen files are listed in the order they will be joined, so check the list before pressing the button.

Choose the output format — MP3 for compatibility and small files, WAV for editing — then press Join Audio Files. The first join in a session loads the converter (about 30 MB); after that, joins start immediately. When the join finishes, a download button appears with the size of the finished file. The output is named after the first file with "-joined" added, so part1.mp3 and part2.mp3 become part1-joined.mp3.

How Joining Works

This joiner runs entirely in your browser using ffmpeg.wasm, a version of the ffmpeg media toolkit compiled to WebAssembly so it can run inside a web page. When you press Join, your files are loaded into the browser's memory, ffmpeg decodes each one, resamples them all to the same sample rate (44,100 Hz, the CD standard), stitches them together end to end with the concat filter, and encodes the result as a single MP3 or WAV file. Your files are never uploaded to a server, so there is no upload wait and no copy of your recordings on anyone else's computer.

The resampling step matters more than it sounds. Audio files can be recorded at different sample rates — 44,100 Hz, 48,000 Hz, 32,000 Hz — and joining files with mismatched rates either fails or produces glitches at the joins. By resampling everything to 44,100 Hz first, the joiner guarantees the files fit together cleanly regardless of where they came from. Resampling to 44,100 Hz is inaudible in practice: it is the sample rate of every CD ever made.

Worked Example

Take two files from a split interview: part1.mp3 (the first half) and part2.mp3 (the second half). The tool names the output part1-joined.mp3 and joins them with a two-input concat filter, resampling both to 44,100 Hz first. If part1 is 12 minutes and part2 is 9 minutes, the joined file is 21 minutes long — the lengths simply add up, because the files play one after another.

A three-file example: a.wav, b.wav, and c.wav joined as WAV produce a-joined.wav, with a three-input concat filter. If the three files are 5, 7, and 8 minutes long, the result is 20 minutes of uncompressed audio. At CD quality, WAV takes 176,400 bytes per second, so 20 minutes is 176,400 times 1,200, which is 211,680,000 bytes — about 212 MB. The same 20 minutes as an MP3 at about 190 kbps is 190,000 times 1,200 divided by 8, which is 28,500,000 bytes — about 28.5 MB. That is why the MP3 output is the better choice for a long joined file unless you plan to edit it.

When to Join Audio Files

The most common reason is repairing a split recording. Many recorders split long recordings into chunks — a phone that stops at a file size limit, a meeting recorder that starts a new file every hour, a dictaphone with a per-file time limit. Joining puts the pieces back into the single recording they were meant to be, in the right order.

Podcasters join segments: an intro, the main discussion, and an outro, recorded separately and assembled into one episode. Audiobook listeners join chapters into a single file so playback does not stop between chapters. Musicians join takes and movements. Teachers join the parts of a lesson recorded across several sessions. In all of these cases, the alternative — playing the files one by one and hoping the order is right — is fragile, and a single joined file is simply easier to share, back up, and listen to.

MP3 or WAV Output?

Choose MP3 when the joined file is for listening or sharing. MP3 plays on every device, and at about 190 kbps it sounds the same as the originals to most listeners, in a file roughly one-seventh the size of WAV. A joined podcast episode, a merged interview, or a combined audiobook is almost always best as an MP3.

Choose WAV when you plan to edit the joined file. WAV is uncompressed, so an audio editor can cut, fade, and process it without any further quality loss, and you export to MP3 only once, at the very end. The cost is size — about 10.6 MB per minute at CD quality — so a long joined file as WAV can be very large. If you are joining just to listen, MP3 is the answer; if you are joining as a step toward editing, WAV is worth the size.

One honest note about MP3 joins: MP3 files carry a tiny amount of encoder delay at the start, which can produce a very short gap — a fraction of a second — between segments in some players. Most modern players handle this correctly and the join sounds seamless, but if perfectly gapless playback matters to you, WAV output has no such issue at all, because WAV has no encoder delay.

Privacy and Limits

Your audio is processed entirely in your browser and never uploaded to any server. That is not a privacy promise — it is how the tool is built. There is no upload step, no account, and no server-side processing, so interviews, recordings, and private audio stay on your own device.

The limits are practical ones. The files you join must total under 2 GB, a limit of the WebAssembly runtime that runs the converter — for audio, that is generous, holding many hours of recordings. The first join in a session downloads about 30 MB of converter code, so the first run needs an internet connection. The tool works in current versions of Chrome, Edge, Firefox, and Safari on desktop and mobile.

Tips for Better Results

Check the order before joining. The files are joined in the order shown in the list, which is the order you selected them. If the list looks wrong, choose the files again in the right order — it is much easier than fixing a joined file.

Match the volume if you can. If one recording is much louder than another, the join will be jarring. Normalizing the volume in an audio editor before joining gives a smoother result, though for casual listening it rarely matters.

Trim first, join second. If the individual files have silence or mistakes at the start or end, cut them with the MP3 Cutter before joining. It is easier to trim a short file than to fix a long joined one.

Convert odd formats first if a join fails. The joiner accepts most audio formats, but a file with an unusual codec can still fail. Converting it to MP3 or WAV with the Audio Converter first almost always fixes the problem.

Common Mistakes to Avoid

The most common mistake is joining files in the wrong order. File pickers do not always return files in the order you expect, especially when you select a whole folder, so always read the list before pressing Join. A joined file in the wrong order has to be redone from the originals.

The second mistake is joining files that should be mixed, not joined. If you want background music under a voiceover, or two people talking at the same time, joining will not do it — joining plays files one after another. Mixing needs an audio editor.

Finally, do not delete the originals after joining. The joined file is a re-encoded copy, and if you later want a different order, a different format, or one segment removed, you need the original files. Storage is cheap; keep the parts and the joined file together.

Advertisement

Frequently Asked Questions

Can I join files in different formats, like an MP3 and a WAV?

Yes. The joiner decodes each file and resamples everything to 44,100 Hz before joining, so an M4A intro, a WAV main recording, and an MP3 outro join into one file without any problem.

How do I control the order of the joined files?

Files are joined in the order shown in the list above the Join button, which follows the order you selected them. Check the list before joining — if it looks wrong, choose the files again in the right order.

Will there be a gap between the joined files?

In most players, no — the join sounds seamless. MP3 files carry a tiny encoder delay that can produce a fraction-of-a-second gap in some older players; WAV output has no gap at all, so choose WAV if perfectly gapless playback matters.

Should I choose MP3 or WAV output?

MP3 for listening and sharing — it plays everywhere and is roughly one-seventh the size of WAV. WAV only when you plan to edit the joined file, because it is uncompressed and loses nothing through further editing.

Is my audio uploaded to a server?

No. Joining runs entirely in your browser using ffmpeg.wasm, and your files never leave your device. The 2 GB total size limit comes from the WebAssembly runtime, not from any server rule.