Audio Merger
Combine multiple audio files into one — drag to reorder them, choose a hard cut, silence gap or crossfade between clips, normalize volume so nothing sounds mismatched, and export as MP3, WAV or OGG. Nothing you upload ever leaves your browser.
Quick Tips for a Clean Merge
Features
Getting the Order Right
The order files merge in is entirely under your control, and it's meant to be easy to get wrong on the first try and fix immediately rather than requiring a re-upload. Every file that decodes successfully shows up as its own row with a small waveform preview and a play button, so you can actually listen to confirm which file is which before deciding where it belongs — file names alone, especially auto-generated ones from a phone or recorder, aren't always a reliable guide.
Dragging a row to a new position handles most reordering in one motion, and the up and down arrows exist specifically for the cases where drag-and-drop is more fiddly than it's worth — nudging one file back a single position, or reordering carefully on a touchscreen where a precise drag is harder to land.
Three Ways to Join Two Clips
A hard cut is the right choice more often than it might seem — if two recordings were always meant to be one continuous piece, like a conversation split across two files by an app's recording length limit, joining them with nothing added or blended is exactly correct. A silence gap does real work for anything meant to read as separate segments — different songs, different spoken topics, different speakers — where a small pause helps a listener mentally separate one part from the next rather than everything blurring together.
Crossfade is the one that takes actual signal processing rather than just placement: the last portion of one clip and the first portion of the next genuinely overlap and play simultaneously, one fading out as the other fades in, rather than one simply starting the instant the other stops. It's the standard technique behind smooth transitions in DJ mixes and album track sequencing, and it's worth reaching for whenever an abrupt cut between two pieces of music would otherwise feel jarring.
Matching Loudness Before Merging
Two recordings rarely arrive at the same volume — different microphones, different recording apps, different distances from the source all affect how loud a file actually is, independent of anything about the content itself. Normalize Volume measures each clip's peak level and scales it to a shared target before merging, which is a meaningfully different (and generally better) approach than only adjusting the overall output volume afterward, since that wouldn't fix an imbalance between individual clips at all — it would just make the whole uneven file louder or quieter as one block.
Bringing Different Files Into One Format
A single continuous audio buffer can only have one sample rate and one channel count at a time, which is a real constraint when the files being merged don't already match — an MP3 at 44.1kHz stereo and a voice memo at 48kHz mono, say, can't simply be concatenated sample for sample. Every clip after the first is automatically resampled to match the first file's format before joining, using the same rendering technique this site's Audio Converter uses for format conversion, so mixing formats in one merge just works without asking you to convert anything first.
What Actually Happens Behind the Merge Button
Every file in the queue is decoded independently the moment it's added, into raw audio samples the same way any of this site's other audio tools work — nothing waits until you click Merge to start reading the files. Clicking Merge itself is comparatively fast: resampling mismatched files, scaling levels if normalization is on, and stitching everything together according to the chosen transition are all plain numeric operations on already-decoded data, not a full re-encode. The slow part, if there is one, is always the export step afterward — specifically OGG, for the reasons above — not the merge itself.
That decoding-on-add approach is also why a bad file gets flagged immediately rather than only after you've arranged an entire queue and clicked Merge. A file your browser can't decode shows an error status right in its row the moment it's added, so it's obvious which one needs to be swapped out or removed before it costs you a wasted merge attempt.
Who Actually Needs to Merge Audio Files
Podcasters join a recorded intro, the main conversation and a closing segment recorded separately into one publishable episode. Musicians stitch together several short voice-memo ideas into one file to review as a whole. Teachers combine a handful of short audio clips into one lesson recording. And plenty of people just have two halves of a long voice memo, split by a recording app's length limit, that need to become one file again.
A podcaster assembling an episode adds the intro music, the recorded conversation and a short outro, orders them with drag-and-drop, sets a 1-second crossfade specifically between the music and the spoken segments so the transition doesn't feel abrupt, and exports the result as MP3 — trimming a rough edge off the conversation first with the Audio Trimmer & Cutter before adding it to the merge. A musician instead merges four short phone-recorded riff ideas with a Silence Gap between each, keeping them as clearly separate takes within one reference file rather than blending them together.
Where a Browser Merger Reaches Its Limit
This tool joins clips end to end — it doesn't mix or layer audio simultaneously, so two files playing at the same time, like a music bed under narration, isn't what a merge produces; that's a mixing job, not a merging one. It's also capped at 15 files and whatever a browser tab can comfortably hold in memory at once, which is a real, sensible boundary rather than a design accident, given everything is happening locally rather than on a server built for heavier workloads.
For the much more common job it's actually built for — taking several separate recordings and turning them into one properly ordered, evenly balanced file — it handles that cleanly and holds up well against paid desktop tools doing the same basic task.
One more practical limit worth knowing: because every file gets decoded and held in memory at once, a merge of many very long files — several hour-long recordings, for instance — can genuinely strain a browser tab's available memory before it strains the 15-file count limit. For that kind of heavy, long-form batch work, splitting it into a couple of smaller merges tends to be more reliable than pushing one browser tab to its practical ceiling.