What is the difference between joining and merging audio?

A join concatenates decoded buffers end-to-end in a chosen order with no overlap or layering. A merge can imply parallel layers, such as mixing a voice over a background track, where both inputs play simultaneously in the output.

Can I join audio without uploading the files?

Yes. A local browser-based joiner reads files with the File API, decodes them with the Web Audio API, concatenates the buffers, and writes the WAV, all inside your current browser tab. Nothing is sent to a remote server.

Does joining audio add silence or fades between files?

A pure concatenation tool does not. The last decoded frame of one file is followed directly by the first decoded frame of the next. Only tools that explicitly offer fades, crossfades, or gap insertion will add transitions, and most local browser joiners do not.

Why is my output WAV so much larger than the source MP3?

PCM16 WAV is uncompressed audio. The original MP3, AAC, Opus, Vorbis, or FLAC bitrate is discarded during decoding, and the output stores one 16-bit sample per channel per frame. A 10 MB compressed file can easily expand to 40 MB or more as WAV.

Can I mix mono and stereo files in the same join?

Most local joiners, including the Audio Joiner covered here, reject a mono and stereo mixture instead of silently remixing. All selected files must decode to the same channel count, and a mismatch produces a clear rejection message.

How do I know which approach fits my project?

Match the tool's contract to your actual requirements: pick a command-line tool for automation and codec preservation, a desktop editor when you also need trimming or effects, an upload service when no installation is possible, and a local browser joiner when you want a fast merge without sending files anywhere.

How Do I Choose the Right Approach to Join Audio

Joining audio means concatenating two or more decoded audio files into one continuous track in a specific order, and the right approach depends on whether you need edits, metadata, silence handling, or just a clean merge. At the sample level, a join stitches the last decoded frame of one file directly to the first decoded frame of the next, so the output is exactly as long as the sum of inputs at a shared rate and the channel arrays are interleaved in frame order during the WAV write. What changes between approaches is everything around that core operation: how files are decoded, whether they are uploaded, what edits are applied, how reordering works, and what container and metadata survive the round trip. Some tools add silence, crossfades, or normalization; others refuse to mix mono and stereo files; some preserve tags and album art while others produce a bare PCM stream. Picking the right approach is less about finding the most powerful tool and more about matching the tool's contract to what your project actually requires.

How audio files are joined at the sample level

A pure join concatenates decoded audio buffers in a chosen order. The last sample frame of track A is followed immediately by the first sample frame of track B, with no inserted silence, overlap, crossfade, or normalization unless the tool specifically adds one. This distinction matters because many "merger" tools quietly insert a small gap for safety, or apply automatic loudness matching that you did not ask for. When you evaluate an approach, check whether the merge is a raw concatenation or a processed combination, because the two produce different output even with identical input files.

The second thing to understand is the difference between joining, merging, and combining. In common usage these words are interchangeable, but a join typically means end-to-end concatenation, a merge sometimes implies parallel layers such as mixing a voice over a bed track, and a combine can mean either depending on the tool. The Audio Joiner documented here does pure concatenation: decoded channel arrays are copied in list order into one buffer, and the result is written as interleaved, little-endian, signed 16-bit PCM in a standard RIFF/WAVE container with no inserted effects.

Four common approaches to join audio

There are four practical approaches most people consider when combining audio clips. Each one fits a different situation, and the table below summarizes the trade-offs.

Approach	Requires install	Requires upload	Editing features	Output format	Best fit
Command-line (FFmpeg, SoX)	Yes	No	None by default	Any (preserved or transcoded)	Automation pipelines, codec preservation, batch jobs
Desktop editor (Audacity, Ocenaudio)	Yes	No	Full (fades, gain, effects, repair)	WAV, MP3, FLAC, OGG, others	Projects that also need trimming, noise reduction, or level adjustments
Online upload service (Clideo, Aconvert)	No	Yes	Basic reorder, sometimes trim	WAV, MP3, or service default	Devices where nothing can be installed and upload time is acceptable
Local browser-based joiner	No	No	Reorder only	PCM16 WAV	Fast local merge without uploads, common browser-decodable formats

Command-line tools give you maximum control and let you script batch jobs, but they require learning a syntax and offer no visual preview. Desktop editors provide a waveform view and full editing features, but you pay for that flexibility in install time, project files, and the overhead of opening a full editor for a simple merge. Online upload services work on any device with a browser, but they send your source audio to a remote server and impose their own file size caps. A local browser-based joiner sits between these options: no installation, no upload, but the output is constrained to what your current browser can decode and to the PCM16 WAV format the Web Audio pipeline produces.

When the browser-based Audio Joiner is the right choice

If your task is "combine 2 to 10 audio files in a specific order and get one WAV back without sending them anywhere," the Audio Joiner is built for exactly that. It reads common audio formats including MP3, WAV, M4A, AAC, Ogg, WebM, and FLAC by name and MIME type, decodes them locally with the Web Audio API, lets you reorder them with Move up and Move down controls, and concatenates the decoded channels directly in list order. There is no uploaded copy, no server-side fallback, and no installed codec library; the entire merge is computed inside your current browser tab on local object URLs that are released when replaced or when the page closes.

The tool is also the right choice when you want explicit budgets instead of silent truncations. It refuses to mix a mono and stereo file, refuses rates above 192 kHz, refuses selections larger than 100 MiB total or 25 MiB per file, refuses more than eight channels, and refuses totals beyond 30 minutes or 30 million channel-samples. Each rejection comes with a specific message rather than a truncated result, so you can fix the selection instead of guessing why the output is shorter than expected.

If your project requires fades, normalization, loudness matching, channel conversion, time-range trimming, sample-level repair, or compressed output with preserved metadata, the Audio Joiner is not the right tool. Those are editor features, and the documented guidance is to switch to a dedicated editor such as Audacity, or to the Audio Cutter when you need a time range rather than a full track. For related decisions you may also want to compare approaches for other audio tasks; the same decision framework applies.

How to join 2 to 10 audio files in your browser

Open the Audio Joiner in your current browser tab and click the file picker.
Choose 2 to 10 audio files together. The picker recognizes MP3, WAV, M4A, AAC, Ogg, WebM, and FLAC by name and MIME type, but a recognized extension does not guarantee that every codec variant can be decoded in your specific browser and operating system.
Wait for browser decoding. Every file in one selection is decoded through the same AudioContext, which may resample sources to that context's working rate, so the displayed rate can differ from the rate stored in the original file.
Preview each decoded track to confirm the right files loaded and that they decoded correctly in your browser.
Use Move up or Move down until the list is in the required order. Reordering updates the decoded-buffer array and the visible list together, and clears any older WAV so a stale result cannot claim a previous order.
Confirm that all selected files decoded to the same channel count. A mono and stereo mixture is rejected rather than silently remixed, duplicated, dropped, or averaged.
Select Join in this order and preview the resulting PCM16 WAV to verify order, joins, and duration.
Download the file. The download is a newly encoded RIFF/WAVE file with interleaved, little-endian, signed 16-bit PCM samples and a 44-byte header that records the channel count, decoded sample rate, and exact data byte length.

Limits and requirements before you start

The Audio Joiner has explicit, testable limits and you should check them against your selection before clicking join. The numbers below are the exact values the picker and shared plan validate against.

Limit	Value
File count per selection	2 to 10
Per-file encoded size	25 MiB (26,214,400 bytes)
Total selection size	100 MiB (104,857,600 bytes)
Total decoded duration	30 minutes
Channel count	up to 8
Sample rate	up to 192 kHz
Total channel-samples	30 million across all channels

A high-rate or multichannel selection can reach the sample budget before the duration limit, so a 5-minute selection at 192 kHz with 8 channels may be rejected even though 5 minutes is well under the 30-minute ceiling. Nothing is shortened, downmixed, downsampled, or omitted to fit a limit; the selection is rejected with a specific message so you can adjust it. Damaged, encrypted, incomplete, mislabeled, or unsupported files also produce a clear error rather than a silent failure, which is one of the main reasons to prefer a tool with explicit budgets over one that hides truncation behind a "success" message.

What the output WAV will and won't contain

The downloaded file is a new static PCM representation of the browser-decoded samples. It preserves the decoded sample rate, the channel count of the decoded selection (only matching channels are kept, in their decoded order), the sample values, and the sequence of tracks in the order you joined them. What it does not preserve is the original codec, the original bitrate, encoder settings, ID3 or Vorbis tags, album art, chapters, cue points, loop points, loudness fields, timestamps, or any other container metadata. The WAV simply has none of those by definition.

Two practical consequences follow. First, the output file can be much larger than the inputs: PCM16 WAV is uncompressed, so a 10 MB MP3 can expand to 40 MB or more once decoded at 44.1 kHz stereo. Second, the output rate may differ from the rate of your source files if the browser resampled during decoding, so if your downstream tool requires a specific rate you should verify the downloaded WAV matches it before deleting the originals.

Float samples are clipped to the range from -1 through 1 during the WAV write, with -1 mapped to -32768, +1 mapped to 32767, and any non-finite values written as silence. The shared encoder writes the RIFF size, WAVE and fmt identifiers, PCM format tag, channel count, decoded sample rate, byte rate, block alignment, 16-bit depth, data identifier, and exact data byte length into the header, and tests inspect those header bytes together with the complete stereo sample sequence. Keep the source files and confirm the downloaded duration, order, joins, channel playback, and file size before deleting any original.