Planning the steps needed to join audio means mapping four short stages — gather and verify inputs, decode them in the browser, set the playback order, and encode the result — before you click anything. The whole join runs locally in your tab, decodes 2 to 10 common audio files through one shared AudioContext, and produces a single gap-free PCM16 WAV file that you download. Because the join is direct, with no fades, silence, overlap, normalization, transition, or automatic trimming inserted between tracks, your on-screen plan is also the order that survives into the output. Setting aside ten minutes to plan the workflow prevents almost every mistake: file-size rejections, channel mismatches, unsupported codecs, and a downloaded WAV that does not match your expected order. The plan below walks through what to check, what to confirm, and what to expect at each stage, ending with a step-by-step run using the Audio Joiner.
What planning an audio join actually covers
Planning an audio join is more than a task list — it is a contract between your source files and the strict decoding and encoding rules of the joiner. The plan should answer four questions before you start: which files to combine, whether they will all decode under the same rules, in what order they should appear, and what the output should look like.
The Audio Joiner combines 2 to 10 browser-decodable audio files into one local WAV without uploading anything. The plan therefore lives entirely in your tab: the files you select, the order you arrange, the decoded PCM samples the browser produces, and the WAV you download are all produced from data that never leaves your device. Knowing this lets you build a planning checklist around visible limits rather than guesswork.
The four stages below cover the planning decisions. The fifth section is the actual execution order; the sixth describes the expected output; the last section covers cases where your plan should point to a different tool, such as the Audio Cutter when you only need a time range instead of full tracks.
Stage 1: gather and verify your source files
Begin by collecting the files you intend to combine and checking each one against three constraints: count, per-file size, and total size. The joiner accepts between 2 and 10 files in one selection. Each encoded file may not exceed 25 MiB (26,214,400 bytes) and the entire selection may not exceed 100 MiB (104,857,600 bytes). Files outside those limits are rejected with a specific message rather than silently trimmed.
Plan your file list with the per-file cap of 25 MiB and the total cap of 100 MiB in mind. A simple arithmetic check tells you whether your selection fits: 100 MiB ÷ 25 MiB per file = 4 files at the per-file cap. Adding a fifth 25 MiB file would push the total to 125 MiB, which the joiner rejects with a specific message. If you plan to combine larger recordings, decide in advance whether to convert them to a smaller compressed format or split them into shorter pieces.
The recognized file types are MP3, WAV, M4A, AAC, Ogg, WebM, and FLAC, identified by extension or MIME type. A recognized extension does not guarantee decoding, because actual decoding depends on the codecs installed in your browser and operating system. Plan to test one source file through the joiner first if you are using an unusual codec, an encrypted file, or a recording you are not certain is intact. Damaged, encrypted, incomplete, mislabeled, or unsupported files produce a clear error and the join stops.
The table below summarizes the explicit limits you should plan around.
| Limit | Value |
|---|---|
| Minimum files | 2 |
| Maximum files | 10 |
| Per-file size | 25 MiB (26,214,400 bytes) |
| Total selection size | 100 MiB (104,857,600 bytes) |
| Total decoded duration | 30 minutes |
| Maximum channels per file | 8 |
| Maximum decoded sample rate | 192 kHz |
| Total channel-samples | 30,000,000 |
Stage 2: confirm channel and rate compatibility
After gathering, the next planning step is to confirm that every decoded file will land on the same channel count and an acceptable sample rate. Web Audio decoding uses one AudioContext, and that shared context may resample your sources to a working sample rate. The displayed rate for the result can therefore differ from the rates stored in your original files. The output does not preserve independent source sample rates, so plan for that consequence rather than discovering it after the download.
Channels are a stricter constraint. Every decoded track must share the same channel count. A mono and stereo mixture is rejected rather than silently duplicated, dropped, averaged, or remapped. Plan to either match them at the source (export both as stereo or both as mono) or split the work into two separate joins. If your inputs are voice memos captured on different hardware — phone calls as mono alongside video audio as stereo — convert in advance so the join runs in one pass.
Channels are kept in their decoded order, with each channel concatenated independently across files before the WAV is interleaved. In stereo, the left channel of track 1 is followed by the left channel of track 2; the right channel of track 1 is followed by the right channel of track 2; the two streams are then interleaved into the final WAV. This is why stereo fixtures with different left and right values can prove, after the join, that the order and channel identity survived intact.
The decoding work runs through the Web Audio API, which decodes supported files through BaseAudioContext.decodeAudioData into an AudioBuffer. Knowing where the audio data lives after decoding helps explain why the join is gap-free and why some validation happens on the decoded buffer rather than on the source file.
Stage 3: set the order before you join
Once the files are ready, plan the playback order before opening the joiner. The order you see in the list is the order that ends up in the WAV: the last sample frame of one decoded track is followed immediately by the first sample frame of the next track in the output channel arrays, with no inserted silence, overlap, crossfade, normalization, transition, or automatic trimming.
Two practical planning notes make ordering easier. First, build a numbered list outside the tool — on paper or in a text file — before you load any files, especially when the sequence matters for a video timeline, a meeting recording, or a multi-part narration. Second, expect the joiner to clear any older WAV preview the moment the order changes, so a stale result cannot claim a previous order. If you reorder mid-plan, listen to the preview again from the top before you download.
Reordering also reorders the decoded-buffer array and the visible list together. The move-up and move-down controls act on the already-decoded buffers, so iterating on order does not pay a decode cost.
Run the join workflow in this order
- Open the Audio Joiner in your browser tab. No account, install, or upload is needed.
- Select 2 to 10 audio files in a single pick. Each file must fit under the per-file and total size limits listed above. The picker accepts MP3, WAV, M4A, AAC, Ogg, WebM, and FLAC by name or MIME type; unsupported files fail with a clear error.
- Wait for the browser to decode each file through the shared AudioContext. The decoded duration, sample rate, and channel count appear in the per-track preview as each buffer is ready.
- Listen to each track preview. If any track sounds wrong, fails to decode, or reports a different channel count than the rest, stop and fix that source before continuing.
- Use Move up or Move down until the list reads in the exact order you planned. The decoded buffers reorder at the same time, and any older WAV preview is cleared.
- Select Join in this order. The joiner concatenates each channel independently in the planned order, validates the result against the budgets, and writes a fresh 44-byte little-endian RIFF/WAVE header.
- Preview the resulting PCM16 WAV in the browser. Listen from start to end, paying attention to the joins between tracks: there should be no gap, click, fade, or extra silence.
- Download the WAV to your machine. Keep your source files until you have confirmed the downloaded duration, order, joins, channel playback, and file size.
This sequence is the execution half of the plan. A more click-by-click version is covered in how to get started joining audio files locally; the steps above show the planning-order view, and the linked guide walks through the same controls one click at a time.
What the output WAV will and will not contain
Planning ahead also means knowing what survives the encoding and what is dropped, so you do not lose anything you still need. The output is a newly encoded RIFF/WAVE file with interleaved, little-endian, signed 16-bit PCM samples. The header written by the encoder contains 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 the exact data byte length. Float samples are clipped to the range -1 through 1, with -1 mapping to -32768, +1 mapping to +32767, and any non-finite values written as silence.
The output does not preserve: the original codec, bitrate, encoder settings, ID3 or Vorbis comment tags, chapters, loop points, cue points, loudness metadata, timestamps, or other container fields. It also does not preserve independent source sample rates, since one working rate is used for the whole join. Plan to keep your originals if you still need any of those properties; the downloaded WAV is a new static PCM representation of the browser-decoded samples, not a re-wrapped container.
A practical size consequence: PCM16 WAV is uncompressed and can be substantially larger than the MP3, AAC, Opus, Vorbis, or FLAC files you selected. Plan your download folder and any downstream upload step accordingly, especially when the consumer also accepts compressed formats.
When your plan calls for a different tool
If your plan is for the joiner but the actual job is something else, pick a different tool. The table below summarizes the common decision points.
| Your plan | Right tool |
|---|---|
| Combine 2–10 full tracks into one WAV | Audio Joiner |
| Extract a specific time range from one track | Audio Cutter |
| Need a fade-in, fade-out, crossfade, or loudness matching | Dedicated audio editor |
| Need compressed output that preserves metadata | Dedicated audio editor with tag support |
| Need to convert mono and stereo to one channel layout | Dedicated audio editor with channel conversion |
| Need sample-level repair or rate conversion at a specific target | Dedicated audio editor with sample-accurate tools |
The general rule is: if every input is a full track, every track shares a channel count, you accept PCM16 WAV as the output, and you do not need fades, transitions, or metadata, the Audio Joiner handles the whole plan. The moment your plan asks for any property not listed above — normalization, dynamic compression, EQ, time stretching that preserves pitch, ID3 tags, or compressed formats — step out of the joiner workflow and into a full audio editor.
The decision to upload your files is also part of the plan. With the Audio Joiner, file reading, Web Audio decoding, channel concatenation, WAV encoding, preview, and download happen in your current browser tab; nothing is sent to a server. Selected files and the finished WAV use temporary local object URLs that are released when replaced or when the page closes. If your plan requires server-side processing for any reason — long-form mastering, AI noise reduction, or large-format delivery — the joiner is the wrong choice and you should plan around a tool designed for that workload.
If you're weighing options, Repeat the Same Result When You Join Audio Files covers this in detail.