The best way to cut audio is to trim one continuous time range from a decoded sample buffer and export the result as a fresh, uncompressed PCM16 WAV file directly in your browser, with no upload to a server. Audio Cutter does exactly this: it uses the Web Audio API to decode your source, rounds your start and end seconds to the nearest decoded sample-frame boundary, and writes a new RIFF/WAVE file containing interleaved signed 16-bit little-endian samples. The start frame is included and the end frame is excluded, so the cut is genuinely frame-accurate rather than an approximation. Every step, including file reading, decoding, frame selection, encoding, previewing, and download, happens in the current browser tab, which means the original file and the working buffer never leave your device.
Most readers searching for the best way to cut audio are trying to extract one clean segment from a song, lecture, voice memo, or podcast. The challenge is that audio tools differ wildly in where they process the file, how precisely they align cut points, and what kind of file they hand back. A few minutes spent on the criteria below will save you from a result with clicks at the wrong edge, a re-encoded MP3 that sounds thinner, or a privacy concern about uploading a recording to a server.
What "Best" Really Means When You Cut Audio
Four qualities separate a reliable cut from a frustrating one: accuracy, privacy, portability of the output, and ease of use. A desktop editor gives you waveform precision but requires an install and a learning curve. A cloud uploader promises convenience but sends your file to someone else's machine. A mobile app is handy, but tiny controls and limited export formats often lead to imprecise cuts. A browser-based trimmer that decodes locally hits all four qualities at once: no upload, frame-aligned boundaries, a clean PCM16 WAV on the way out, and no installation. The table below compares the broad shape of each method.
| Approach | Processing location | Cut precision | Install required | Typical output |
|---|---|---|---|---|
| Browser tool (Audio Cutter) | Local in browser | Frame-accurate at decoded rate | No | PCM16 WAV |
| Desktop editor | Local on computer | Sample-accurate with zoom | Yes | WAV, MP3, FLAC, OGG |
| Cloud uploader | Remote server | Slider-based, often millisecond | No | Usually MP3 or M4A |
| Mobile app | On device | Touch-handle, can drift | Yes (app store) | MP3, M4A, sometimes WAV |
The exact sample rate, channel count, and frame count that the browser tool reports come from Audio Cutter itself and are displayed after you choose a file, so the working numbers are not estimates.
Why a Local Browser Cut Beats Uploading
Uploading a recording to a remote cutter means your audio traverses a network, sits on a third-party disk during processing, and only comes back after a server-side encode. For a private voice memo, an unreleased demo, or anything under NDA, that path is a real concern. Audio Cutter skips the round trip entirely. According to the product contract, file reading, Web Audio decoding, frame selection, WAV encoding, preview, and download all happen in the current browser tab, and temporary local object URLs are released when a file or result is replaced or the page closes.
There is a second benefit hiding in the local-only design: latency. The instant you click a button, you see the result, because nothing is traveling to a data center. That tight feedback loop is also what makes previewing the cut edges practical, since you can nudge a boundary by a fraction of a second and hear the difference without waiting for a remote encoder. Per the MDN decodeAudioData reference, decoding happens on a background thread, which keeps the rest of the page responsive while a long file loads.
How to Cut Audio with Audio Cutter
The full cut happens in three steps, all performed by Audio Cutter in your browser tab. The page shows the decoded duration, sample rate, channel count, and frame count before you cut, so you can confirm the file loaded correctly before choosing any range.
- Choose a browser-decodable audio file within the displayed file and decoded-audio limits. The file picker recognizes common MP3, WAV, M4A, AAC, Ogg, WebM, and FLAC names and MIME types, but actual decoding depends on the codecs your current browser supports. Container and codec support differs across Safari, Chrome, Firefox, operating systems, and browser versions. An unsupported, damaged, mislabeled, encrypted, or incomplete file produces a clear decode error instead of a silent failure, and the tool does not install a codec or send the file to a conversion server.
- Enter a non-negative start time and a later end time that does not exceed the decoded duration. Start cannot be negative or at the end of the audio, end must be greater than start, and a selection that rounds to less than one frame is rejected rather than producing an empty file. The page converts your seconds to the nearest decoded sample-frame boundary using the AudioBuffer sample rate, the start frame is included, and the end frame is excluded.
- Select Cut and export WAV, preview the PCM16 result, then download it. The download is a newly encoded RIFF/WAVE file containing interleaved little-endian signed 16-bit PCM samples. The page also reports the output duration and file size before you commit to the download, so you can sanity-check the cut before the file hits disk.
After the cut, play back the result and listen carefully at both boundaries. Spoken words and percussive transients are the easiest things to mis-cut by a fraction of a second. If the first word of your segment sounds swallowed or the last note is clipped, adjust your start or end by a small amount and cut again. Changing either time field clears the previous WAV, and each fresh cut replaces and releases the prior download URL so old files do not pile up in memory.
What the Output WAV Actually Contains
Every download is a freshly encoded file, not a wrapper around your source. The export uses the AudioBuffer sample rate after any resampling performed by Web Audio while decoding, which means the displayed sample rate describes the decoded working buffer and the exported WAV rather than the source file's encoded rate. Channels remain in their original sequence and are interleaved: a stereo file stays stereo, and a multichannel source keeps its channels up to the eight-channel cap. The exported AudioBuffer data is what the WAV header points at.
Floating-point Web Audio samples are clamped to the PCM range from -1 through 1 before encoding. Negative full scale becomes -32768, positive full scale becomes 32767, and any non-finite value is written as silence. The file begins with a 44-byte RIFF/WAVE header that records PCM format 1, the channel count, the decoded sample rate, the byte rate, block alignment, and 16 bits per sample, followed by the raw sample data. A useful formula for the data portion is:
data bytes = selected frames × channel count × 2 bytes per sample
For example, a 30-second cut at 44.1 kHz in stereo produces 30 × 44,100 × 2 × 2 = 5,292,000 bytes of sample data, plus the 44-byte header for a total of 5,292,044 bytes, which is about 5.05 MB. Because PCM WAV is uncompressed, even short cuts can be larger than a long compressed source such as a 128 kbps MP3. If you need a smaller file, re-encode the WAV with a dedicated tool after the cut.
Hard Limits That Decide Whether the Cut Will Succeed
Before you choose a file, it helps to know the safety limits because over-limit inputs are rejected with a clear message rather than truncated. Audio Cutter enforces all of the following:
| Limit | Maximum | What it controls |
|---|---|---|
| Encoded input file size | 25 MB | File picker byte cap before decoding |
| Decoded duration | 15 minutes | Length of the working AudioBuffer |
| Channel count | 8 | Multichannel layouts up to 7.1 |
| Decoded sample rate | 192 kHz | Highest rate the buffer can carry |
| Total decoded channel-samples | 30,000,000 | Frames × channels combined cap |
The 30 million channel-sample cap is the one that catches people off guard. A stereo file at 48 kHz reaches the cap at about 5 minutes 13 seconds of decoded audio, while a single-channel 48 kHz file can run for about 10 minutes 25 seconds before hitting the same wall. High-rate or multichannel sources can hit the processing boundary before the duration limit does. If your source is rejected, split it with a dedicated editor or downsample it first; Audio Cutter will not shorten a file automatically. Browser decoding necessarily happens before decoded duration and sample count can be inspected, so a highly compressed long file may still consume temporary memory during the decode attempt even if it ends up rejected.
When the Browser Method Is Not Enough
Audio Cutter is built for one job, namely extracting a continuous range cleanly, and the contract makes that scope explicit. It does not offer target resampling, remix, normalize, fade, noise removal, pitch shifting, or compression of the WAV. It also does not preserve tags, album art, cue points, chapters, loudness metadata, encoder settings, or any other container fields from the source. The original compressed codec, bitrate, and metadata are not retained in the export, and the export does not use the same encoding as the source.
For production work, switch to a dedicated editor. Use a desktop DAW if you need waveform-level fades, a multi-band compressor, or mastering. Use a frame-accurate compressed-format editor if you need to cut an MP3 or AAC file without re-encoding every frame. Keep the original file alongside any browser cuts so you always have an untouched source to return to. For readers who want a deeper workflow before they start, the planning guide for cutting audio lays out the decisions that matter.
If the cut fails to play, the boundaries feel off, or the page refuses the file, work through the troubleshooting flow rather than guessing. Decode errors point to an unsupported codec or a damaged file, an empty cut means the selected range rounded to less than one frame, and a rejected file means one of the safety caps above was crossed. Fix the cause, then re-cut. For a complete diagnosis path, the troubleshooting checklist for cutting audio walks through each failure mode.