Trim Audio — Cut to Precise Start & End

How Audio Trimming Works

Trimming is the simplest kind of audio edit: you pick a start timestamp and an end timestamp, and everything outside that range is discarded. Under the hood, the tool decodes your uploaded file into raw PCM samples using the Web Audio API, calculates which sample indices correspond to your chosen start and end times, and copies out just that slice. Because it's working directly with the decoded sample data rather than passing the file through a lossy encoder again, there's no generational quality loss — the kept portion sounds identical to the same section in the original file. That's different from re-encoding, where every pass through a lossy codec like MP3 throws away a little more detail.

People reach for a trim tool for very specific reasons: pulling a highlight clip out of a longer podcast episode, cutting a voice memo down to just the useful part, isolating a music sample of a set length, or removing a long lead-in before a recording actually starts. It's a single-range operation by design — you keep one continuous stretch of audio between two points. If what you actually need is to remove scattered pauses and dead air throughout an entire recording rather than cut to one range, that's a different job better handled by Silence Remover, which scans the whole waveform instead of just two endpoints. Many people run trim first to establish rough boundaries, then run silence removal on the trimmed result to tighten pacing inside that range.

Precision matters more than it seems for trimming. Dragging a slider gets you close, but spoken words have sharp attack transients — cut half a frame too early and you clip the first consonant of a sentence. That's why the tool supports typing exact timestamps directly, which lets you nudge a cut point by fractions of a second after previewing the rough selection. The waveform preview player exists specifically so you can confirm the cut sounds clean before committing, rather than discovering a clipped word only after downloading.

The output always exports as WAV regardless of what format you uploaded — MP3, OGG, AAC, and FLAC are all supported as input. Exporting to WAV rather than trying to re-encode back into the original compressed format avoids stacking a second lossy pass on top of whatever compression the source file already had. If you specifically need the trimmed clip in MP3 or another compressed format afterward, run the WAV output through a dedicated converter as a separate step. Since everything runs client-side, there's no server-imposed file size limit — the only constraint is how much audio your device's memory can hold while decoding and processing.