Audio Merger

Joins several audio files end to end into one. Useful for combining recorded segments, chapters or takes into a single file.

Live demo · real result from this tool

Drop audio files here

or paste with Ctrl+V · nothing is uploaded

10–50 ms hides a seam in speech; music usually wants longer.
Evens out recordings made on different days so the volume does not jump at the joins.
Loaded from cdn.jsdelivr.net only when needed; FFmpeg is GPL-licensed. Your audio still never leaves your device.

Your result appears here — processed on your device.

Processed on your device — nothing is uploaded.

How to use Audio Merger

  1. Add your audio files in the order you want them.
  2. Check they share sample rate and channel count.
  3. Merge and listen through the joins.
  4. Mismatched sample rates or channel counts require resampling, which costs quality.
  5. Normalise levels before merging or the volume will jump at each join.
  6. Files are processed in your browser and never uploaded.

Match the files before joining

Clips with different sample rates or channel counts have to be resampled to a common format, which costs quality and occasionally produces artefacts at the joins. Mono and stereo files joined together give inconsistent output. Check that your files match before merging — and if they came from different devices or sessions, they very likely do not.

Level differences are the audible problem

Two recordings made on different days will differ in volume, and the jump between them is obvious to a listener in a way it is not to someone watching a waveform. Normalise the levels before merging, or the result sounds like what it is: separate recordings stuck together. Loudness normalisation to a target LUFS level is the professional approach; matching peaks by eye is the quick one.

Crossfades hide the seam

A hard cut between two clips is audible whenever the room tone differs even slightly. A short crossfade — anywhere from 10 milliseconds to half a second depending on the material — blends the transition so it passes unnoticed. For music the fade usually needs to be longer and placed musically; for speech, short is better, since a long fade on dialogue sounds like a mistake.

Frequently asked questions

Can I mix files with different sample rates?
Yes. Each file is scheduled into a single offline rendering context, and the browser's resampler converts every clip to the highest sample rate found among your files, so mismatched inputs still line up correctly.
Is there a limit on how many files I can join?
There is no fixed limit, but everything is held in memory as raw audio, so very long combined tracks can run out of RAM on low-end devices. Joining a handful of songs or a dozen voice clips is comfortable on most machines.
Are the files uploaded to merge them?
No. All decoding, joining and WAV writing happens locally with the Web Audio API. Nothing is transmitted, which is why merging works even if you go offline after the page loads.
Why does the volume jump between my merged clips?
Because the source recordings were made at different levels. Normalise them to a common loudness before merging — the jump is far more obvious to a listener than it looks on a waveform.
Do the files need to be the same format?
They need matching sample rate and channel count for a clean join. Mismatched files are resampled, which costs a little quality and can produce artefacts at the transitions.
How do I avoid a click between clips?
Use a short crossfade — 10 milliseconds is enough for speech, longer for music. A hard cut is audible whenever the room tone differs between recordings.

Written by the ToolsRift team · Last updated

Pages are drafted with AI assistance and checked by automated tests. How we write and check pages.

Was this tool useful?

Report a problem

Start typing to search every tool.

↑ ↓ to moveEnter to openEsc to close