Audio Joiner concatenates 2 to 10 browser-decodable audio files in the order shown in its list and exports one gap-free PCM16 WAV — no upload, no installed editor, and no codec configuration required. Every step runs inside the current browser tab: the file picker collects your sources, the Web Audio API decodes each one through one shared AudioContext, and a shared encoder writes a 44-byte little-endian RIFF/WAVE header over interleaved 16-bit samples. Because decoding happens locally, the original files never leave your machine and the joined result is a clean new PCM representation of the decoded buffers. The tool is built for the same task many readers look up under the Audacity name — taking a handful of separate clips and producing a single file in a chosen sequence — but it stops at concatenation. No fade is inserted between tracks, no silence is added, no crossfade happens, and no metadata from the sources is carried into the output. Limits are checked up front rather than silently trimmed.
How Audacity Joins Audio Files
For readers already using Audacity, the standard workflow to concatenate clips looks like this:
- Launch Audacity with a fresh empty project at the project's intended sample rate and channel count.
- File > Open to load the first clip onto the timeline.
- Project > Import Audio (or File > Append Audio on some builds) to bring in the next file at the end of the timeline.
- Repeat the import step for every remaining file until all clips are stacked in the chosen order.
- File > Export > Export as WAV (or MP3) to save the joined result to disk.
Audacity does more than simple concatenation along the way. It can resample each import to the project rate, drop or duplicate channels, insert crossfades at clip boundaries, normalize peak or RMS level, and trim head or tail silence. Those features carry real power, but they cost a 130 MB or larger download, a one-time LAME or FFmpeg setup for MP3 or M4A export, and a project file to keep in sync with your sources. If the goal is strictly "concatenate these files in this order into one WAV," most of that machinery stays idle.
For a guide framed explicitly around avoiding the Audacity install for this exact task, see Join Audio Clips in Audacity Without Installing It.
What a Browser Joiner Adds Over Audacity
The trade-off is simple. Audacity gives you a timeline editor with trimming, fades, normalization, and compressed output, in exchange for installation, encoder setup, and a workspace to manage. Audio Joiner focuses on the narrow path: "concatenate in this order, save as one WAV." Fewer controls, fewer settings to misconfigure, and no installer at all.
Audio Joiner runs entirely in the browser tab through the Web Audio API, so the original files and the joined result never leave your machine. Reordering is a one-click move-up or move-down, not a project-shuffle. Rejected selections — a 60-minute total, a mono file sitting next to stereo clips, a 25.5 MiB source — return a specific message instead of a damaged file. The file input is reset after every selection, so adding the same files twice works the way most people expect.
Combine 2 to 10 Audio Files in Audio Joiner
The happy path is short. Once you open Audio Joiner in a supported browser, every step happens in the same tab.
- Click the file picker and select 2 to 10 audio files together. The picker recognizes common MP3, WAV, M4A, AAC, Ogg, WebM, and FLAC names and MIME types; a recognized extension does not guarantee every codec variant will decode in every browser.
- Wait for each file to decode through one shared AudioContext. The per-file (25 MiB) and total (100 MiB) limits are shown above the picker; per-track sample rate, channel count, and decoded duration appear once each file finishes decoding.
- Use the per-track preview controls to listen to each decoded buffer in isolation. Web Audio may resample sources to one working sample rate, so the rate shown here can differ from what was stored in the original file.
- Use Move up and Move down on each list entry until the visible order matches the sequence you want in the final WAV. Reordering updates the decoded-buffer array and the list together and clears any older result, so a stale preview cannot claim a previous order.
- Click Join in this order. A validation plan checks track count, sample rate, channel count, total frames, duration, channel-sample budget, and the offset at which each track begins. Anything out of bounds is rejected with a specific message before the WAV is written.
- Preview the produced PCM16 WAV with the same playback control.
- Click Download to save the WAV locally.
With 2 to 10 files inside the limits and matching channel counts, the join produces the WAV and matches the join plan exactly; a damaged, encrypted, incomplete, or codec-unsupported file returns a clear error instead of a partial buffer.
Hard Limits, Channel Rules, and Rejection Messages
Limits are advertised up front and enforced in the validation plan. The tool never silently truncates, downmixes, rescales, or resamples a selection to fit. The hard numbers are:
| Constraint | Value |
|---|---|
| Files per join | 2 to 10 |
| Per-file encoded size | 25 MiB (26,214,400 bytes) |
| Total selection size | 100 MiB (104,857,600 bytes) |
| Decoded total duration | 30 minutes |
| Channel count | up to 8 |
| Sample rate | up to 192 kHz |
| Total channel-samples | 30,000,000 |
Several additional rules apply once decoding finishes:
- Channel-count matching. Every file in one selection must decode to the same channel count. A single mono file among stereo files is rejected rather than silently duplicated, dropped, averaged, or remapped.
- Channel-sample budget. A high-rate or multichannel selection can exceed the 30-million channel-sample budget before the 30-minute duration cap arrives. The same shared plan handles both, and the first one reached is the one that triggers rejection.
- Shared sample rate. All decoded tracks in one join carry the AudioContext's working sample rate, not independent source rates. The result does not preserve independent per-track sample rates, and the rate shown for the tracks and result may differ from what was stored in the originals.
- Codec and variant independence. Whether a given M4A, MP3, Ogg, FLAC, or WebM file decodes depends on the codecs exposed by your browser and operating system through BaseAudioContext.decodeAudioData(). There is no codec library or server fallback to lean on.
Inside the Output WAV
The downloaded file is a fresh RIFF/WAVE encoded from the decoded buffers, not a passthrough of the original sources. The specifics:
- Header. A 44-byte little-endian header with 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.
- Sample format. Signed 16-bit interleaved PCM, little-endian. Float samples are clipped to the range from -1 through 1; negative full scale maps to -32768, positive full scale to 32767, and non-finite values are written as silence.
- Channels. Channels are retained in their decoded order and concatenated independently before interleaving. Left stays left, right stays right, across the join, which is verified by stereo fixtures that hold different values in the left and right channels across two tracks.
Because PCM is uncompressed, the WAV will routinely be several times larger than the original compressed files. A worked example makes that concrete: two stereo MP3 sources at 44,100 Hz, totaling 6 minutes of decoded audio, become 6 minutes × 60 seconds × 44,100 samples/sec × 2 channels × 2 bytes/sample = 63,504,000 bytes, roughly 60.6 MB — versus perhaps 10 MB combined at a typical compressed bitrate.
The output also does not preserve the original codec, bitrate, encoder settings, ID3 or Vorbis tags, album art, chapters, cue points, loop points, loudness fields, timestamps, or any other container metadata. It is a new static PCM representation of the browser-decoded samples. Keep the source files until you confirm the downloaded WAV plays the right order, with the right channels, for the right duration, and at the right size.
When Audacity Is Still the Right Choice
A browser joiner is the right tool until the task reaches for something it does not do. Audacity is the better choice when the job needs fades, loudness matching, channel conversion, compressed output such as MP3 or M4A, metadata preservation, sample-level repair, or arbitrary trimming across a timeline. For trimming a time range out of a single audio file without installing anything, Audio Cutter covers the same browser-local workflow with a different shape. The honest framing is that Audio Joiner is a focused tool for one well-defined job; reach for Audacity when the job grows beyond concatenation.