Why this matters
Editing audio should not require installing a multi-gigabyte DAW just to trim ten seconds off a podcast intro. Most people who need to cut audio — podcasters removing dead air, video editors isolating a sound bite, musicians trimming a rehearsal recording — are doing a single operation: select a range and export. A lightweight, purpose-built audio trimmer that decodes the file in the browser, lets you drag sliders to the exact start and end points, and exports a sample-accurate WAV fills that gap without the overhead of a full editing suite.
The waveform visualization is drawn from the actual audio samples in the selected region, so you can see silence gaps, speech patterns, and musical phrases before committing to the cut. The trim operates at exact sample boundaries — roughly 22 microseconds of precision at 44.1 kHz — which means there are no millisecond-level gaps or clicks at the cut points that you get with less precise tools.
1. Click the drop zone — pick an audio file (MP3, WAV, M4A).
Key capabilities
| Feature | Detail |
|---|---|
| Input formats | Any browser-decodable audio or video |
| Precision | 1/sampleRate seconds (sample-accurate) |
| Output format | 16-bit PCM WAV |
| Waveform | Canvas-drawn min/max envelope |
| Sliders | Start and end time selection |
| File size limit | Browser memory (typically hundreds of MB) |
How to use it
Drop an audio file onto the upload zone — you can also drop a video file and the tool will extract its audio track.
The browser decodes the file using the Web Audio API and displays the waveform.
Drag the Start slider to where you want the clip to begin and the End slider to where it should end.
The waveform updates to show only the selected region so you can visually confirm the selection.
Click 'Trim selection to WAV' to download the trimmed clip as a 16-bit PCM WAV file.
Testing your result
After exporting, open the WAV file in any audio player or editor and verify that it starts and ends exactly where you intended. Check that there are no audible clicks, pops, or silence gaps at the cut boundaries — sample-accurate slicing should produce clean joins. If you trimmed a known segment (for example, the first 30 seconds of a song), compare the output duration against the expected length. You can also re-import the trimmed WAV into the tool and confirm that the waveform matches the selection you originally made.
Common mistakes
Dragging the end slider before the start slider, which produces an invalid zero-length or negative-length selection.
Dropping a very large audio file that exceeds available browser memory, which causes the decode step to fail silently.
Expecting MP3 output — the tool exports WAV because browsers do not include a built-in MP3 encoder.
Not accounting for the fact that video files are decoded to audio only, so the exported WAV contains no video track.
Overlooking the selection length display and accidentally exporting a much longer or shorter clip than intended.
Edge cases and options
The tool accepts any file format the browser can decode, which includes MP3, WAV, OGG, FLAC, AAC, M4A, and even video files like MP4 and WebM (the audio track is extracted automatically). Output is always 16-bit PCM WAV, which is lossless and universally compatible. The waveform canvas draws a min/max envelope per pixel column, so you see the true shape of the audio dynamics rather than a smoothed approximation. Browser memory is the practical limit — files that decode to several hundred megabytes of PCM data may cause performance issues, so for hour-long recordings a native editor like Audacity is more appropriate.
Real-world use cases
Trimming the silence from the beginning and end of a podcast recording before publishing.
Isolating a specific sound effect or voice line from a longer audio take.
Cutting a short audio clip from a video file for use as a notification sound or social media post.
Removing a false start or flubbed section from a music rehearsal recording.
Preparing audio samples for a presentation or e-learning module by extracting the relevant segments.
Frequently asked questions
Q: Is the trim sample-accurate?
A: Yes. The tool slices the underlying AudioBuffer at exact sample boundaries, so the cut is precise to within 1/sampleRate seconds — approximately 22 microseconds at 44.1 kHz.
Q: Can I trim MP3 files directly?
A: The tool decodes the MP3 to PCM first and exports as WAV. If you specifically need MP3 output, use a native editor like Audacity or ffmpeg, because browsers do not ship an MP3 encoder.
Q: What does the waveform show?
A: The waveform displays only the selected region. Each pixel column represents a min/max envelope of the underlying audio samples in that time bucket, so you see the actual dynamics of the part you will keep.
Q: Can I preview the selection before exporting?
A: The waveform shows the shape and length of your selection. A full audio preview player is planned for a future update — for now, export the WAV and play it to verify.
Q: What is the maximum file size I can load?
A: Browser memory is the practical limit, typically a few hundred megabytes of decoded audio. For files longer than an hour, a native desktop editor is recommended.
Start using it now
Try the Audio Trimmer tool. See also Extract Audio and Mute Video for related audio and video tools.
