Which formats can it read?

Anything the browser can play, which in practice means MP3, WAV, M4A (AAC), OGG and often FLAC. If a file cannot be read, the page says so. To take the audio out of a video first, run it through the file converter (/file/convert) and load the result here.

How long a file can it handle?

Up to 20 minutes and 100MB per file. Decoded audio sits in memory uncompressed — about 23MB per minute in 48000 Hz stereo — so the size of the file tells you very little about what it will cost to open. A 9MB podcast MP3 is routinely 45 minutes. Anything over the limit is reported rather than loaded.

Can it also fix the level or the sound?

No. This tool only cuts and joins; it leaves level and tone exactly as they were, apart from the fades at the ends. For loudness and polish there is the mastering tool (/audio/master), for separating vocals and instruments the stem separator (/audio/separate), for key and tempo the key & tempo changer (/audio/pitch-tempo), and for changing file format the file converter (/file/convert).

Is the audio stored anywhere?

No. Everything happens in the browser and nothing is sent to a server. Closing or reloading the page discards both the audio and the range you had set.

Does it work on a phone?

Yes. The handles are wide enough for a finger, and the range can also be typed into the number fields. Memory use scales with length, though, so start with a few minutes rather than a long recording — long exports are steadier on a computer.

WAV is uncompressed, so nothing is lost. It is the right choice for material you will keep editing or take back into a DAW, at the cost of size — roughly 16MB per stereo minute. MP3 is much smaller and is what you want for something you are handing over or putting on a phone. Note that exporting an MP3 source back to MP3 compresses it twice, which costs a little detail; choose WAV if that matters. On length: a WAV comes out exactly as long as you asked, while an MP3 runs 25–50 ms longer — the format pads every encode, and the measured amount shifts with the length, even between two selections a tenth of a second apart. Pick WAV when the duration has to be exact.

How long should the fades be?

To take the abruptness off a cut that starts mid-phrase, 0.1–0.3 seconds is plenty. To close an ending naturally, 1–3 seconds is usual, and a piece with a long tail can take five. Fades are applied inside the selected range, so a long one eats into the part you meant to keep. Set the range first, then add the fades as an edge treatment.

Should there be silence between joined files?

For a continuous medley, leave it at 0. For spoken word, meeting recordings or a set of takes, 0.3–1 second makes each change of source obvious to the ear. The same gap goes between every pair, so if you need different gaps in different places, export in twos and then join those results.

What happens to the sample rate?

Trimming a single WAV keeps that file’s own sample rate: decoding runs at whatever rate the browser audio engine uses — 48000 Hz or 44100 Hz on most machines — but a trim needs no resampling, so the file is re-read at its own rate before it is written. Joining is the exception: every clip has to share one rate, so joined output uses the engine’s rate, and a 22050 Hz source can come out at 48000 Hz. Raising the rate adds no information, only bytes — and it is the reason joined files always line up. The rate that will be written is shown under the export panel.

Back to all tools／ Music & audio

Audio cut and join

Runs in your browserNothing is uploaded

Drag the handles on the waveform, or type start and end times, to keep just the part you need. Several files can be joined end to end instead. Add fades and export as WAV or MP3.

Input

What to do

Load an audio file and the waveform and range handles appear here.

Fades

Fade in（sec）

Fade out（sec）

Even at 0 both ends get a 3 ms taper, which is what stops a cut from clicking. Fades are applied inside the exported range.

Export

Format

WAV is 24-bit and uncompressed, so nothing is lost. Output is two channels; a mono source is written as two identical channels. For a mono 16-bit source those two together make the file about three times larger.

Output

The trimmed or joined audio lands here, with its length and size.

The handles move from the keyboard too — 0.1s with the arrow keys, 1s with Shift, 0.01s with Alt — so the precision of an edit point is not limited by the mouse or the screen width.

All tools

Highlights

Set the point by eye or by number: Drag the handles across the waveform to get close, then tighten the start and end in the number fields. The handles also take arrow keys — 0.1s a press, or 1s with Shift held — so the precision of an edit is not limited by the precision of a mouse.
Cuts that do not click: Slicing where the waveform is not near zero leaves a step, and a step is an audible click. Both ends get a 3 ms taper even when the fades are set to zero. It is far too short to hear as a fade, and short enough that nothing about the material changes.
The audio never leaves the browser: Reading, cutting, joining and encoding all happen in the page. Unreleased music, interview recordings and meeting audio are all fine to work with here.

How to use it

Choose Cut or Join, then load the audio
Pick Cut or Join at the top, then put your audio into the box below it. Cut takes one file; Join takes as many as you like at once.
Set the range, or the order
For a cut, drag the two handles on the waveform or type times into the start and end fields. For a join, use the arrows in the list to reorder the files, and set how much silence to insert between them.
Preview and export
Add fade in and fade out times if you want them, and press Preview to hear the result. Choose WAV or MP3 and press Export to save the file.

Choosing the settings

WAV or MP3?: WAV is uncompressed, so nothing is lost. It is the right choice for material you will keep editing or take back into a DAW, at the cost of size — roughly 16MB per stereo minute. MP3 is much smaller and is what you want for something you are handing over or putting on a phone. Note that exporting an MP3 source back to MP3 compresses it twice, which costs a little detail; choose WAV if that matters. On length: a WAV comes out exactly as long as you asked, while an MP3 runs 25–50 ms longer — the format pads every encode, and the measured amount shifts with the length, even between two selections a tenth of a second apart. Pick WAV when the duration has to be exact.
How long should the fades be?: To take the abruptness off a cut that starts mid-phrase, 0.1–0.3 seconds is plenty. To close an ending naturally, 1–3 seconds is usual, and a piece with a long tail can take five. Fades are applied inside the selected range, so a long one eats into the part you meant to keep. Set the range first, then add the fades as an edge treatment.
Should there be silence between joined files?: For a continuous medley, leave it at 0. For spoken word, meeting recordings or a set of takes, 0.3–1 second makes each change of source obvious to the ear. The same gap goes between every pair, so if you need different gaps in different places, export in twos and then join those results.
What happens to the sample rate?: Trimming a single WAV keeps that file’s own sample rate: decoding runs at whatever rate the browser audio engine uses — 48000 Hz or 44100 Hz on most machines — but a trim needs no resampling, so the file is re-read at its own rate before it is written. Joining is the exception: every clip has to share one rate, so joined output uses the engine’s rate, and a 22050 Hz source can come out at 48000 Hz. Raising the rate adds no information, only bytes — and it is the reason joined files always line up. The rate that will be written is shown under the export panel.

Questions

Which formats can it read?: Anything the browser can play, which in practice means MP3, WAV, M4A (AAC), OGG and often FLAC. If a file cannot be read, the page says so. To take the audio out of a video first, run it through the file converter (/file/convert) and load the result here.
How long a file can it handle?: Up to 20 minutes and 100MB per file. Decoded audio sits in memory uncompressed — about 23MB per minute in 48000 Hz stereo — so the size of the file tells you very little about what it will cost to open. A 9MB podcast MP3 is routinely 45 minutes. Anything over the limit is reported rather than loaded.
Can it also fix the level or the sound?: No. This tool only cuts and joins; it leaves level and tone exactly as they were, apart from the fades at the ends. For loudness and polish there is the mastering tool (/audio/master), for separating vocals and instruments the stem separator (/audio/separate), for key and tempo the key & tempo changer (/audio/pitch-tempo), and for changing file format the file converter (/file/convert).
Is the audio stored anywhere?: No. Everything happens in the browser and nothing is sent to a server. Closing or reloading the page discards both the audio and the range you had set.
Does it work on a phone?: Yes. The handles are wide enough for a finger, and the range can also be typed into the number fields. Memory use scales with length, though, so start with a few minutes rather than a long recording — long exports are steadier on a computer.

Input

Fades

Export

Output

Related tools

Highlights

How to use it

Choose Cut or Join, then load the audio

Set the range, or the order

Preview and export

Choosing the settings

Questions