Back to all tools
Free · runs in your browser

Audio trimmer

Drop in a recording, drag the handles across a real waveform and export just the part you want. This audio trimmer decodes the file inside your browser tab, so nothing is uploaded to anybody.

Your file is never uploaded.

It is read straight off your disk with the browser’s own file API and decoded by the browser’s own audio decoder, inside this tab. There is no server call in this page at any point — you can watch the network panel and see it. Export writes a WAV file, because a lossless container needs no encoder and adds no second generation of compression.

Drag an audio or video file here, or choose one below. File support depends on your browser, operating system and the codec inside the file. MP3 and WAV are useful starting points.

Your file is decoded by your own browser. It is never uploaded, and nothing is written to disk unless you click download.

What an online audio trimmer usually does with your file

It uploads it. Of the sites ranking for this search, around four in ten POST your recording to a server, cut it there and hand back a download link. The page rarely says so — you infer it from the progress bar that appears before anything is visible. Your audio then sits on someone else’s disk for as long as their retention policy says, which for a free tool is usually a number nobody there can tell you.

For a podcast intro that does not matter. For a client call, a medical note, an unreleased track or an interview with a source it matters, and it is the reason this page exists. Everything here happens in the tab: the file is read off your disk, decoded by your browser, drawn to a canvas, cut in memory and written back out as a WAV you save yourself. You do not have to take that on trust — open the network panel, load a file, export a clip, and watch the request list stay empty.

How this audio cutter works online without uploading anything

Worth stating plainly, because “private” is a claim and this is a description.

  • Reading. File.arrayBuffer() pulls the bytes off your disk into the tab’s memory. No part of that involves the network.
  • Decoding. The browser turns your file into audio samples. Support depends on the codec and container as well as your browser and operating system. MP3 and PCM WAV are broadly supported; newer Safari versions also support more Ogg formats. If a file cannot be decoded, try another current browser or convert it in an audio editor.
  • Drawing. Three minutes of audio is roughly eight million samples and your screen is eight hundred pixels wide, so the waveform is one minimum and maximum per column. That scan runs in a Web Worker, and the result is cached so a resize costs nothing.
  • Cutting. A trim is a slice of a typed array between two sample indices. What comes out is what went in, unless you asked for a fade, a downmix or a rate change.
  • Writing. The clip becomes 16-bit integers, interleaved, behind a hand-written 44-byte RIFF header. That is the whole WAV format, which is why this page carries no audio library.

Using it as an audio file cutter online, step by step

  • Drag the file onto the drop zone, or use the file picker.
  • Drag across the waveform to rough in a selection, then drag either handle. Or tab to a handle: an arrow key moves 100 milliseconds, shift and an arrow moves a second.
  • Press space to hear exactly what you selected before committing to it.
  • Type into the start and end fields when you know the timecode. They read and write mm:ss.mmm and accept plain seconds too.
  • Choose keep or delete. Delete is the one people forget exists, and it is the right tool for taking a cough out of the middle of a take.
  • Export. The WAV lands in your downloads folder.

Why you cannot trim an MP3 online without losing a generation

An MP3 is not a recording; it is a description of a recording that was already thrown away. To cut it, something must decode it back to samples. If the tool then writes another MP3, that second encoder makes its own decisions about what to discard, on audio that has already lost material once. One round trip is usually inaudible on speech and audible on cymbals; four are audible on everything.

There is a way to trim an MP3 with no loss — rewriting the container on frame boundaries without touching the audio data — but it only lands cuts every 26 milliseconds or so, and doing it correctly means parsing frame headers, LAME gapless tags and ID3 chunks. That is a real piece of software, not a page feature.

So this tool decodes once, cuts, and writes WAV. Nothing is compounded, and if you need an MP3 at the end you make it once, from the WAV, at a bitrate you chose rather than one a web page never disclosed.

Clicks at the cut, and what the fade control actually fixes

Cut a waveform at an arbitrary point and the sample value there is almost never zero — it might be at 0.6 of full scale. The audio before the join ends at 0.6, the audio after starts at 0, and that instantaneous step is, in frequency terms, energy smeared across the whole spectrum. You hear it as a click.

Editors normally solve this by snapping cuts to zero crossings. This tool uses a short linear fade, the same fix from the other direction: ramp the first and last few milliseconds from silence and there is no step left to reproduce. Ten milliseconds is the default because it kills the click and is far too short to perceive as a fade. Set it to zero when you cut into silence and want the samples untouched; raise it to 500 or 1000 for a fade you can hear.

Sample rate, bit depth, and what this audio trimmer’s WAV export contains

Sample rate is how many times per second the waveform was measured — 44,100 for CD audio, 48,000 for video — and it sets the highest frequency the file can hold, at half the rate. Bit depth is how finely each measurement is stored. This page writes 16-bit: about 96 dB of dynamic range, more than any speech recording needs, and half the size of 24-bit.

One wrinkle most tools hide: the Web Audio API decodes at the sample rate of your sound hardware, not the file’s. Load a 44.1 kHz MP3 on a machine whose output runs at 48 kHz and the browser resamples during decoding, before this page sees a single sample. So the tool reports the rate it actually got rather than the one written in the file. That is browser behaviour no in-page trimmer can avoid, and you should know about it rather than wonder later.

Why 16 kHz mono is the right preset for speech-to-text

Speech recognition models are overwhelmingly trained on 16 kHz mono. That rate holds everything up to 8 kHz, which covers the intelligible range of the human voice, consonants included, and discards the octave above it, where speech carries almost nothing. A second channel is redundancy when one person talks into one microphone. Hand an engine a 48 kHz stereo file and it downmixes and resamples anyway, usually less carefully than you would.

The payoff is size: ten minutes at 48 kHz stereo is about 110 MB, and about 19 MB at 16 kHz mono. When you downsample here, every input sample inside an output sample is averaged rather than discarded — a crude low-pass, but a real one, because naive decimation folds high frequencies back into the speech band as a metallic buzz. To clean up the text that comes back, use the transcript cleaner.

What this tool deliberately does not do

  • It exports WAV only. No MP3, no M4A, no Ogg. An encoder means a megabyte of JavaScript and a second lossy generation.
  • It is single-track. One file, one selection, one cut — no timeline, no crossfades, no joining two recordings.
  • There are no effects. No noise reduction, normalisation, compression or EQ. Fade, mono downmix and resample are the whole list, because each is arithmetic simple enough not to go wrong.
  • Large files are bounded by your browser, not by us. Decoding expands audio to 32-bit floating-point samples, so an hour of 44.1 kHz stereo is roughly 1.2 GB in memory whatever it weighs on disk. This page estimates that before decoding, warns above 50 MB and refuses above 200 MB — a refusal you can act on beats a tab that dies silently.
  • It does not transcribe. There is no speech recognition here at all; it cuts audio. For dictation in the browser, that is the voice typing tool.
  • It is not a video editor. A video file loads and its audio track decodes, but the export is audio only.

Where VoiceSnap Pro fits

VoiceSnap Pro is a voice-to-text dictation and voice-notes app for macOS and Windows. Hold one keyboard shortcut, speak, and punctuated text appears in whatever field your cursor is already in: an email, a ticket, a document, a chat. Your personal vocabulary helps the app recognize names and jargon, and a second shortcut saves what you say as a voice note in your account, where you can tag it, file it in a folder, rework it with AI actions or have it remind you later. Nothing you dictate is used to train AI models.

The connection to an audio trimmer is narrow but honest: if you are here because you recorded something and want the useful minute out of it, dictation is the thing that means you never make that recording at all. The microphone test tells you whether the input you are about to record with is the one you think it is.

Start with 5,000 transcribed words across dictation and voice notes, plus 50 manual AI actions, given once with no expiry, every feature and no card. Pro is $9 a month, subject to fair use. Download free for Mac or Windows. The tool on this page stays free either way, with no account.

Questions people ask