Settings

1. The recording

MP3, M4A, WAV, OGG, WebM, and FLAC in most browsers. Anything your browser can play, it can cut.

Drop a recording here, or choose one An hour of audio decodes in a few seconds on your own machine.

What this is, and what it is not

It writes WAV. PCM 16-bit, the format everything opens and every editor imports without loss. Writing MP3 would need an encoder library; the WAV is larger and it is exact.

It decodes what the browser plays. MP3, M4A and WAV everywhere; OGG, WebM and FLAC in most browsers. A file the browser cannot play is reported, not silently mangled.

Fades and normalising are applied to the piece, not the file. The recording you opened is never changed. The fade is a straight ramp at each end of the selection; normalising lifts the loudest peak of the selection to just under full scale.

Long recordings need memory. The whole file is decoded to samples: about ten megabytes a minute for stereo at 44.1 kHz. An hour is fine on a computer; a phone may refuse a very long one.

Nothing leaves this tab. Decoding, drawing, playing and writing all happen in browser memory. With a folder connected, the WAV is filed under Sovereign Suite/SNIP.

Questions people ask

Why not MP3?

An MP3 encoder is a substantial library that is not on this origin, and every cut through MP3 loses a little more quality. WAV is lossless, and any player or editor opens it; convert afterwards if a smaller file matters.

Can I join two recordings, or remove the middle?

Not here. It cuts one piece from one file. For a ringtone or a clip that is all you need; for editing, save the pieces and join them in an editor.

How exact is the cut?

To the sample. Type the times to the hundredth of a second, or drag; the fade avoids a click at the edges.

Is anything uploaded?

No. Open the network tab in your browser's developer tools and cut an hour-long recording; nothing goes out.

Related tools