About this tool
Trimming audio means cutting off the start, end, or both of an audio clip. The most common use is removing silence and false starts from voice memos, podcasts, or song clips. The result is exported losslessly (no re-encoding) so the audio quality matches the source.
This tool runs in your browser using Web Audio API. The waveform visualizes loud and silent regions so you can find trim points by eye. Start and end markers can be set by dragging or by typing exact timestamps (HH:MM:SS.mmm). Output preserves the source format and codec.
How it works
Open your audio
Drop an MP3 / WAV / AAC / OGG / FLAC file. The waveform renders.
Set the trim points
Drag the start and end markers, or type timestamps in HH:MM:SS.mmm format.
Preview
Play the trimmed region to confirm.
Export
The trimmed audio saves to your device in the same format as the source.
Use cases
Voice memos
Cut the "uhh, recording starts now" preamble and the "click click" stop noise from a 5-minute voice note.
Podcast intros
Trim 3 seconds of dead air at the start of an episode.
Music clips
Cut a 30-second sample from a 4-minute song for a video soundtrack.
Lecture recordings
Trim from "the lecture begins at" timestamp to the end.
Format and spec details
| Source formats | MP3, WAV, AAC, OGG, FLAC, M4A |
|---|---|
| Engine | Web Audio API + browser AudioBuffer |
| Output | Same format as source, lossless trim |
| Resolution | Millisecond-precision |
Tips and best practices
- Cut 0.5-1 second of silence at the start of any voice recording for a snappy listen.
- Use the waveform to find loud peaks (likely false starts) and trim around them.
- For background noise, trim is not enough - apply noise reduction in Audacity / GarageBand.
How browser-based audio/video tools work
Modern browsers ship with Web Codecs API, MediaRecorder, and Web Audio API - enough to decode, manipulate, and re-encode most media formats client-side. This tool uses those APIs (with FFmpeg.wasm as a fallback for less common codecs).
The processing flow
- File is loaded as a binary Uint8Array.
- The codec is detected from the container (MP4 = MPEG-4, MKV = Matroska, WebM = WebM) and the codec atoms.
- Frames are decoded into raw audio samples (PCM) or video frames (YCbCr / RGB).
- The requested transformation (trim, convert, resize) is applied frame-by-frame.
- Frames are re-encoded into the output codec and packaged into the output container.
Common audio/video formats
| Container | Common codecs | Best for |
|---|---|---|
| MP4 | H.264 / H.265 video, AAC audio | Universal compatibility; default for web video |
| WebM | VP9 / AV1 video, Opus audio | Open-source web standard; smaller than MP4 |
| MKV | Any codec (container only) | High-quality archival; not browser-native |
| MOV | ProRes / H.264, PCM / AAC | Apple ecosystem; ProRes for professional editing |
| MP3 | MP3 audio only | Universal audio; lossy |
| WAV | PCM audio (lossless) | Editing source; CD-quality archival |
| FLAC | Lossless compressed audio | Music archival; ~50% of WAV size, perfect quality |
| AAC / M4A | Advanced Audio Coding | iOS default; better quality than MP3 at same bitrate |
Lossy vs lossless
- Lossy (MP3, AAC, Opus, H.264): discards data the human ear/eye can't notice. 80-90% size reduction. Each re-encode loses more quality (generation loss).
- Lossless (FLAC, WAV, ALAC, FFV1): bit-perfect reproduction. ~50% size of raw. Each re-encode is identical to the source.
Bitrate quick reference
| Use case | Audio bitrate | Video bitrate (1080p) |
|---|---|---|
| Voice (phone, podcast) | 32-64 kbps | n/a |
| Music (mid-quality) | 128 kbps MP3 | n/a |
| Music (transparent) | 256-320 kbps MP3 or 128 kbps Opus | n/a |
| Streaming HD | n/a | 5,000-8,000 kbps |
| Streaming 4K | n/a | 15,000-25,000 kbps |
| Archival | FLAC lossless | ProRes 422 or H.265 CRF 18 |
Privacy and offline operation
Every operation in this tool runs client-side using your browser's built-in APIs (Canvas, Web Audio, WebAssembly). No data is uploaded. After the initial page load you can disconnect from the internet and the tool keeps working.
We use Google Analytics and AdSense for the page itself, but neither sees the content of the files you process.
Frequently asked questions
Does trimming re-encode the audio?
No - trimming the boundaries preserves the source codec and bitrate. There is no quality loss.
Can I trim multiple regions?
This tool trims start + end. For multiple cuts (remove a middle section), trim into two parts and use Audio Merge.
Why does the waveform look flat?
Very quiet audio renders as a small waveform. Use the zoom control to amplify visually.
Is my video uploaded anywhere?
No. All processing happens in your browser using Web Codecs / FFmpeg.wasm. Files stay in your tab's memory. Disconnect from the internet after page load and the tool still works.
Why is conversion slow?
Video re-encoding is CPU-intensive. A 1-minute 1080p clip can take 30-90 seconds to encode in the browser - desktop apps with hardware acceleration are 5-10x faster. Use this tool for short clips; for hour-long footage use HandBrake or FFmpeg on your machine.
Will the converted file lose quality?
Yes, slightly, if the source and destination are both lossy formats. Going from H.264 to H.264 at the same bitrate adds a small amount of generation loss. Going from H.264 to a lossless codec preserves the existing quality but doesn't restore what was lost on the first encode.
Can I convert between any two formats?
Most common pairs (MP4 <-> WebM, MP3 <-> AAC, WAV <-> FLAC) work in any modern browser. Exotic codecs (ProRes, FFV1, JPEG 2000) may require FFmpeg.wasm and run slowly.
What's the maximum file size I can process?
Practical limit is your browser's available memory (typically 2-4 GB). 30-minute 1080p videos process fine. 2-hour 4K source files may crash the tab; use a desktop tool for those.
How accurate is the Audio Trim?
It applies the standard formula. Accuracy is limited only by your input precision. For decisions with material consequences (taxes, medical, legal, structural), use the result as a starting point and verify with a qualified professional in the relevant field.
Is the Audio Trim free to use?
Yes. 100% free, no signup, no payment, no API key. The site is funded by display ads around the tool but not inside the calculation flow.
Are my inputs saved anywhere?
No. All inputs stay in your browser tab. Closing the tab discards them. The site uses Google Analytics for traffic measurement (anonymized) but the analytics never see what you type into the form.
Can I use the Audio Trim on my phone?
Yes. The tool is responsive and tested on iOS Safari, Android Chrome, and major desktop browsers. Touch targets meet Apple's 44pt and Google's 48dp minimum.
Does the Audio Trim work offline?
Yes. Once the page has loaded, it works without internet. The calculation runs in JavaScript on your device.
How do I report a bug or suggest improvement to the Audio Trim?
Email hi@3tej.com with the URL of this page and a description of what you saw vs expected. We typically respond within 72 hours.
Can I share results from the Audio Trim?
Take a screenshot or copy the output. The page doesn't generate shareable URLs for specific calculations - inputs stay in your browser only.
Why are the results different from another audio trim tool?
Most likely: different formula assumptions, different default values, different rounding rules, or different applicable rates. Check the methodology if both tools document it. Both can be valid for different scenarios.