Cut any audio file by start and end timestamp: MP3, WAV, OGG and more, processed locally in your browser, never uploaded.
Your audio is processed locally with FFmpeg running in your browser. Nothing is
uploaded; the file never leaves your device. First use downloads the ~31 MB
engine once. Files up to 200 MB.
Times accept seconds (90), MM:SS (01:30), or HH:MM:SS (00:01:30.5), decimals allowed.
Leave start empty to cut from the beginning. The end time is required and must be
later than the start.
Cutting audio is routine work: trimming silence off the start of a voice memo, keeping
the best 30 seconds of an interview, splitting a long recording into sections. This
tool cuts precisely between the two timestamps you type; the start defaults to the
beginning of the file when left empty. Because the seek happens before decoding (a
fast seek straight to the start point), even long files begin processing immediately.
The kept segment is re-encoded rather than copied, and that is deliberate. Compressed
audio stores sound in frames, so a stream-copied cut must land on frame boundaries and
can begin or end with a partial frame that plays as a click or glitch. Re-encoding
lands exactly on your timestamps: sample-accurate boundaries, no artifacts. At MP3
quality 2 or Opus 128 kbps the re-encode is transparent to most listeners, WAV
involves no loss at all, and audio encoding is fast even in the browser.
Cutting runs locally with FFmpeg compiled to WebAssembly, so your audio never leaves
your device. Related jobs: trimming video files with the
Video Trimmer,
pulling the track out of a video first with the
Audio Extractor,
or changing the format of the cut with the
Audio Converter.
How to Cut Audio
Select your audio file (MP3, WAV, OGG, M4A, FLAC, and more, up to 200 MB).
Enter the start time, or leave it empty to cut from the beginning.
Enter the end time, for example 90, 01:30, or 00:01:30.5.
Choose the output format and click Cut Audio. The engine loads once, then the segment is cut locally.
Check the cut duration in the result summary, preview it on the page, then click Download Cut Audio.
Audio Cutter FAQs
Why does the tool re-encode instead of cutting losslessly?
Precision. Compressed audio is stored in frames, and a stream-copied cut can only land on frame boundaries, typically every 20 to 26 milliseconds. That sounds small, but a cut that starts mid-frame plays as an audible click or pop. Re-encoding decodes the audio and rebuilds it from your exact timestamps, so the boundaries are sample-accurate and artifact-free. At these settings the re-encode itself is transparent.
What timestamp formats are accepted?
Plain seconds (90), MM:SS (01:30), and HH:MM:SS (00:01:30), each with optional decimals (1:23.5). The start time is optional and defaults to 0; the end time is required. The end must be later than the start, and both should fall inside the track; otherwise you get a clear error instead of a broken file.
Will cutting reduce audio quality?
The kept segment passes through one re-encode. MP3 at variable bitrate quality 2 (~190 kbps) and Opus at 128 kbps are transparent for most listeners and most material; WAV output involves no encoding loss at all. If the source is already a compressed file, the extra generation of loss is inaudible in practice.
Can I cut without any re-encoding at all?
Not with this tool, by design. Lossless audio cutting requires frame-aligned cut points and careful handling of bit reservoirs, and even then it frequently produces glitched edges. This tool always re-encodes the segment to guarantee exact, clean boundaries. If you need a truly bit-exact cut, a dedicated desktop audio editor can do it manually.
What happens if my end time is past the end of the file?
FFmpeg stops decoding at the actual end of the track, so the output contains everything from your start time to the final sample. If the timestamps are so far out that nothing is produced (for example a start time beyond the track length), the tool stops with a clear error instead of downloading an empty file.
We use cookies to enhance your experience, analyze website traffic, and provide personalized content.
You can choose which cookies to accept. Essential cookies are required for basic site functionality.
Learn more in our Privacy Policy
Cookie Preferences
Essential CookiesRequired
Site functionality, theme preference, and consent storage. These cannot be disabled.
Help us understand how visitors use our site to improve the experience.
Enable Google AdSense ads based on your consent settings.