Skip to content
FileKit
Audio And VideoRuns in your browser5 min read

Audio Merger

This audio merger joins several audio files together into a single WAV file in the order you arrange them, entirely inside your browser. Add a silent gap between clips, blend them together with a crossfade, or join them back to back with nothing in between, then download one combined file.

Loading the tool interface
Files never leave your deviceNo upload wait and no queueNo signup, watermark or file limit

Merging audio comes up more often than it might seem. Voice memos recorded in several short takes need to become one continuous track, a set of sound effects needs to play back in sequence as a single cue, and a playlist of short clips often needs to become one file for a device that only accepts a single track. All of these are the same underlying operation: take several files and lay them end to end into one.

Every file stays on your device throughout. Each clip is decoded locally, joined locally and written out as a single WAV file locally, so a set of private recordings never has to be uploaded just to combine them.

When to use an audio merger

Choosing to merge audio online rather than in a desktop app is the right call whenever the goal is genuinely one continuous track rather than several separate ones. A podcast recorded as an intro clip, a main segment and an outro clip is a common example, as is a set of short voice memos that together form one longer recording, or several sound effect takes that need to play in a fixed sequence.

It is a different job from mixing, which layers sounds on top of each other at the same time, such as adding background music under narration. An audio merger lays files one after another along the timeline instead, so the second file only begins once the first has finished, or once its crossfade with the first has completed.

  • Combine audio files that were recorded as separate takes into one continuous track.
  • Join mp3 files or clips of other formats that need to play back in a fixed sequence.
  • Add a gap between clips when a clear pause is wanted between them.
  • Use a crossfade when clips should blend smoothly rather than cut abruptly.

Choosing between a gap and a crossfade

A gap inserts a fixed length of silence between each pair of clips, which suits spoken word content where a clean pause reads as intentional and natural, such as between chapters of an audiobook or separate announcements in a sequence.

A crossfade instead overlaps the end of one clip with the start of the next, fading one out while fading the other in across that overlap. This avoids an abrupt cut and suits music or ambient sound where a hard edge would be jarring, at the cost of the two clips briefly playing on top of each other during the overlap window rather than one strictly following the other.

What happens when files have different sample rates

Audio files rarely all share exactly the same sample rate and channel count, especially when they come from different recording sources. Before joining, every file is resampled to match the highest sample rate and channel count found across the whole set, so the merged output has one consistent format throughout rather than an inconsistent mix that would play back incorrectly in places.

This resampling step is why a merge involving files recorded at very different quality levels can take a moment longer than joining files that already match, since each mismatched file has to be rendered through an audio context before it can be laid into the final timeline.

How this audio crossfade tool builds the joined file

Once every clip has been decoded and resampled to a common format, the tool calculates the total length of the output, accounting for any gap or crossfade overlap, and allocates one buffer of that length. Each clip is then written into its position along that buffer in order, and where a crossfade is requested, the overlapping samples from the outgoing and incoming clips are blended with a linear fade rather than simply added on top of each other.

The finished buffer is exported as a 16 bit PCM WAV file, since that is the format a browser can reliably write without a licensed codec. No part of decoding, resampling, joining or encoding involves a server at any point.

How to merge audio files

  1. 1

    Add your audio files

    Drag two or more audio files onto the drop area, or click it to browse. They join in the order you add them.

  2. 2

    Reorder or remove clips

    Arrange the list into the order you want the final track to play, and remove any file you no longer need.

  3. 3

    Choose a gap or a crossfade

    Pick a silent gap length for a clean pause, or a crossfade duration for a smooth blend between clips.

  4. 4

    Merge and download

    Press merge, wait for the combined track to render, then download the result as a single WAV file.

Related tools worth bookmarking

Sources and further reading

Frequently asked questions

Common questions about the audio merger.

There is no fixed limit imposed by the tool, though the practical ceiling is your device's available memory, since every file has to be decoded and held in memory while it is joined. Merging a handful of typical voice memos or short clips together works comfortably on most laptops and phones.

This audio merger does not care about format, only the decoded sample rate and channel count matter. The tool decodes every file regardless of whether it started as MP3, OGG, FLAC, M4A, AAC or WAV, then resamples anything that does not already match the highest sample rate and channel count in the set before joining.

During the overlap window, the outgoing clip's volume ramps down linearly from full to silent while the incoming clip's volume ramps up linearly from silent to full, so the two fades sum back to a roughly constant overall level across the transition rather than dipping or spiking.

Yes, files are combined in the exact order shown in the list, which you can rearrange before merging. The final WAV plays each clip in that order, separated by whatever gap or crossfade setting you chose.

The result downloads as a single 16 bit PCM WAV file regardless of what formats the source clips used. Browsers cannot reliably re encode a compressed format like MP3 without a licensed codec, so WAV is the honest output for a merge performed entirely with web technology.

No. Decoding, resampling, joining and the final WAV export all happen locally using the Web Audio API. None of the files are transmitted to a server, so a set of private recordings stays private throughout the entire process.