Skip to content
Processing locally — files never leave your device

Audio Trimmer

Load an audio file, pick start and end times, and trim it to that range. Export as WAV. Runs entirely in your browser via the Web Audio API.

How to use Audio Trimmer

  1. Choose an audio file (MP3, WAV, M4A, OGG, or anything your browser can decode). It loads straight into the page — never uploaded.
  2. Play it back in the built-in player to find the exact moment you want to keep.
  3. Type the start and end points in seconds. The end field shows the file's total length so you know the maximum.
  4. Click "Trim". The tool slices that range out of the decoded audio and re-builds it as a new clip.
  5. Preview the trimmed result and click "Download WAV" to save it — all processing happened in your browser.

Cutting audio in your browser, losslessly and privately

An audio trimmer lets you keep just the part of a clip you care about — the chorus of a song, a single quote from an interview, or the usable take from a long recording. This one runs entirely as a web page, so your file is never uploaded. You load it, pick a start and end, and download a clean cut, all on your own device.

How browser-based trimming works

When you choose a file, the Web Audio API decodes it into raw audio samples in memory. To trim, the tool copies only the samples between your chosen start and end times into a new buffer using an OfflineAudioContext, then writes that buffer out as a WAV file. Because it is copying existing samples rather than re-encoding them, the cut is lossless and sample-accurate — the kept audio is bit-for-bit identical to the original.

Why the export is WAV

There is an asymmetry built into browsers: they can read MP3 and AAC but cannot write them, because the encoders are patent-encumbered and simply are not shipped. Exporting WAV sidesteps that by writing the samples out raw — the result is bit-perfect against the kept region, with no second generation of lossy compression stacked on your source. The cost is bytes: expect a WAV several times larger than the MP3 you fed in. If size matters more than fidelity for the final file, transcode the WAV to MP3 once at the very end of your edit.

Setting accurate start and end points

Play the file first and watch the timecode to find your in and out points, then type them into the start and end fields. Decimals are allowed, so 8.5 means eight and a half seconds. The end field displays the total duration so you never overshoot. If you want a clip that starts at the very beginning, leave start at 0.

Common uses

  • Ringtones and alerts. Cut a few seconds out of a song for a custom tone.
  • Podcast and interview edits. Pull a single answer or remove dead air from the ends.
  • Sample prep. Isolate a loop or one-shot before importing into a DAW.
  • Cleaning recordings. Drop the silence or fumbling before and after your take.

Editing unreleased audio without leaking it

The clips that most need trimming are often the ones you can least afford to hand around: a track that has not dropped yet, a session bounce covered by an NDA, interview tape with a named source. Because decoding and cutting both happen in an OfflineAudioContext inside this tab — and that buffer is freed the instant you leave the page — there is no upload step where the material could be copied or cached. You get a clean cut without your master ever sitting on someone else's disk.

Related media tools

  • Audio Recorder — capture a fresh take, then bring it straight here to top and tail.
  • Text to Speech — generate a spoken line, capture it, then trim it to length.
  • Video Mute — for video, the audio-removal counterpart to this audio cutter.

Frequently asked questions

Why is the output a WAV file?
A browser happily decodes MP3, AAC, M4A, and Opus, yet it has no built-in way to write those compressed formats back out. WAV is the escape hatch: it stores raw samples, so the export is instant, exact, and dependency-free. Need a smaller MP3 in the end? Re-encode the WAV once in any audio editor — but for editing and archiving, lossless WAV is the better master.
Does trimming reduce the audio quality?
No. The trim is a sample-accurate cut of the original decoded audio written out as WAV, which is lossless. There is no re-compression, so the kept portion sounds exactly like the source. The WAV file will be larger than an MP3 simply because it is uncompressed.
Is my audio file uploaded anywhere?
No. Your file is decoded by the Web Audio API and cut inside an OfflineAudioContext, both of which run in this tab. That distinction matters most for the files people actually trim here: unreleased demos, rough mixes under NDA, or interview tape you have promised to keep private. None of it is transmitted, so none of it can leak from a server you do not own.
What input formats can I load?
Anything your browser can decode — commonly MP3, WAV, M4A/AAC, OGG, and FLAC, depending on the browser. If a file fails to load, the browser likely lacks the codec; re-saving it as WAV or MP3 first will resolve that.
How precise can the start and end points be?
The fields accept decimals (steps of 0.1 second), and internally the cut is made at the nearest audio sample, so it is frame-accurate. For tighter precision, type a value like 12.3 rather than relying on whole seconds.
Can I trim a very long file?
Yes, with one caveat: trimming requires decoding the entire file into raw samples up front, and a multi-hour or high-sample-rate recording expands a lot once uncompressed. On a modest laptop or phone, working through such material in a couple of passes avoids pushing the tab’s memory to its limit.
Which browsers are supported?
Wherever the Web Audio API exists — Chrome, Edge, Firefox, and Safari, on both computers and phones — the trimmer runs. There is no permission prompt and no microphone involved; you simply choose a file from your device.
Can I keep stereo, or does it become mono?
Stereo is preserved. The tool copies every channel of the original (mono, stereo, or more) into the trimmed clip at the same sample rate, so the channel layout is unchanged.

More tools you might find useful in the same flow.

Built by Muhammad Tahir · About