The right approach to cut audio depends on four practical factors: the format of your source file, the precision required at the cut boundary, whether the source can leave your device, and the format you want for the output. Each factor narrows the available tools, and matching the tool to the factor is what produces reliable results without re-encoding surprises. A browser-based PCM16 WAV cutter such as Audio Cutter fits situations where the source stays local, only one continuous slice is needed, and an uncompressed WAV is acceptable. A desktop digital audio workstation fits situations where you need fades, multi-region cuts, normalization, or sample-accurate compressed-frame editing.
Cutting, in practice, covers a wider range of operations than the word suggests. It can mean trimming dead air from a podcast, extracting a single verse from a song, slicing an interview highlight, saving a sound effect from a longer field recording, or producing a short clip for a presentation. The mechanics differ across those cases. Frame-accurate cuts in PCM data align to specific sample positions, while cuts in compressed formats such as MP3, AAC, or Ogg usually need to land near a frame boundary, which is why lossy editors often snap cuts to the nearest valid decode point. The output also matters: a WAV keeps every sample uncompressed while an MP3 re-encodes the slice with new compression artifacts. Choosing the wrong combination produces audible clicks at boundaries, lost metadata, or a file that is unexpectedly large.
What "Cutting Audio" Actually Means
In a strict audio-engineering sense, cutting audio means defining a start frame and an end frame inside decoded samples and writing the slice between those frames as a new file. The end frame is excluded so the cut lands exactly on the boundary the editor chose. Floating-point samples in the slice are clamped to the PCM range of −1 through 1, signed 16-bit values are written in little-endian byte order, and a 44-byte RIFF/WAVE header records the format. Every commercial WAV cutter, whether it runs in a browser tab or as a desktop app, performs that same mechanical operation once the audio has been decoded.
What changes between tools is everything that surrounds that core operation. Some tools decode a file, cut, and re-encode on a server, which uploads the source. Some tools run inside the browser using the Web Audio API, which keeps the file local. Some tools preserve the original compressed encoding by trimming at codec frame boundaries, while others always re-encode the slice as uncompressed PCM. Some tools offer fades, gain changes, or normalization before or after the cut; others do not. Those surrounding choices are what determine which approach fits a given task.
Decision Factors: Format, Privacy, Precision, and Output
Before picking a tool, four questions usually resolve the choice:
- What is the source format? Lossless sources such as WAV or FLAC can be cut and re-exported without quality loss. Lossy sources such as MP3 or AAC are already missing information; cutting and re-encoding creates a second generation of compression.
- Can the source be uploaded? Confidential recordings, unreleased music, voice memos, and licensed material should not leave the device. A local browser tool or an offline desktop tool is the safer choice.
- What precision is required at the boundary? A podcast intro that starts on a strong beat needs only approximate timing. A drum hit used as a sample needs sample-accurate alignment.
- What output format is the destination expecting? Video editors and DAWs often expect WAV. Messaging apps, ringtones, and web embeds often accept MP3 or AAC.
Once those four questions are answered, the available tools shrink dramatically. A task that combines a single slice, a need for local processing, and a WAV destination points directly at a browser-based PCM16 cutter. A task that combines multiple slices, fades, and metadata preservation points at a desktop editor.
The Browser-Based PCM16 WAV Approach
Browser audio tools rely on the BaseAudioContext.decodeAudioData method to turn a file into an AudioBuffer, which is a JavaScript object holding the decoded samples in memory. Once decoded, the tool picks start and end times, rounds those times to the nearest sample frame at the decoded sample rate, and copies the frames into a new interleaved buffer. That buffer is encoded as a PCM16 WAV and offered as a download through a temporary local URL. Nothing is sent to a remote server.
Audio Cutter follows exactly that pattern. The page validates the chosen file name and byte size, calls Web Audio to decode it, displays the decoded duration, sample rate, channel count, and frame count, accepts start and end times in seconds, snaps them to sample-frame boundaries, and exports the slice as a freshly encoded RIFF/WAVE file. The previous result is cleared when a new cut is made or a new file is loaded, and audio contexts are closed after decoding to release resources. Because every step happens in the current tab, the source file never travels beyond the device.
How to Cut a Precise Time Range with Audio Cutter
- Open Audio Cutter in your browser and choose a file the page can decode. The file picker matches common MP3, WAV, M4A, AAC, Ogg, WebM, and FLAC names and MIME types, and the file must be 25 MB or smaller.
- Wait for Web Audio to finish decoding the file. The page then shows the decoded duration, sample rate, channel count, and total frame count. If the decoder rejects the file, a clear decode error appears and nothing else happens.
- Enter a non-negative start time in moments and a later end time almost instantly. Both times are rounded to the nearest sample frame at the decoded rate, the start frame is included, and the end frame is excluded. A selection that rounds to fewer than one frame is rejected.
- Select the option to cut and export WAV. The page reports the output duration and the resulting file size before the download begins.
- Preview the PCM16 result to confirm the spoken word or musical transient at both boundaries, then download the WAV. The previous result and its download URL are released when a new cut replaces them or when a new file is loaded.
Because both the visible duration on the page and the actual cut are calculated from the same frame range, the times you enter match the times you hear in the preview. That consistency is the main reason the production exporter and the preview share the same frame-range function rather than a separate timer estimate.
Limits, Trade-Offs, and When to Pick Another Approach
Audio Cutter applies four explicit decoding limits that determine whether a file can be processed at all. The encoded input file must be 25 MB or smaller, the decoded audio must be 15 minutes or shorter, it must use no more than eight channels, and it must run at no more than 192 kHz. A combined sample budget of 30 million channel-samples caps total decoded size across all channels. High sample rates or multi-channel files can hit that 30-million-sample boundary before the 15-minute duration boundary, and the page refuses over-limit files rather than truncating them.
Two further trade-offs follow from the PCM16 WAV output. First, the original MP3, AAC, Vorbis, Opus, or FLAC encoding is not preserved in the download; every result is a freshly encoded uncompressed file with no tags, album art, cue points, chapters, loudness metadata, or encoder settings carried over. Second, the output file can be much larger than the source because PCM WAV stores two bytes for every sample in every channel, plus the 44-byte header. A 10-second stereo selection at 48 kHz produces roughly 1.92 MB of audio data; the same selection from a 128 kbps MP3 source is closer to 160 KB. Re-encoding the WAV to MP3 afterwards is a separate step.
The tool also does not provide fades, gain changes, normalization, pitch shifting, resampling controls, or noise reduction. If the task requires any of those, a dedicated desktop editor is the correct choice. Likewise, if the task needs multiple disjoint ranges stitched together, the Audio Joiner produces a single WAV from already-cut slices rather than attempting several cuts inside one tool.
Choosing by Scenario
The table below matches common tasks to the approach that handles them most reliably. The numeric limits in the third and fourth rows are the documented boundaries of Audio Cutter rather than estimates.
| Scenario | Best approach | Why it fits |
|---|---|---|
| Single slice from a local file, WAV output is acceptable | Browser-based PCM16 WAV cutter | Decoding, frame selection, and encoding all run in the tab; no upload |
| Multiple disjoint ranges from the same source | Desktop editor, or cut twice and join with Audio Joiner | Browser cutter exports a single range per operation |
| Source is at or above 25 MB, 15 minutes, 8 channels, 192 kHz, or 30 million channel-samples | Desktop editor or command-line tool | Audio Cutter rejects over-limit files with a message rather than truncating |
| Output must remain a compressed codec such as MP3 or AAC | Cut as WAV first, then re-encode to MP3 or AAC in a second step | Browser cutter does not retain the source codec |
| Source cannot leave the device for privacy or licensing reasons | Local browser cutter or offline desktop tool | File reading, decoding, frame selection, and encoding happen in the current tab |
Verifying the Cut and Keeping Your Source Safe
A reliable cut is a verified cut. After the WAV is rendered, listen to the first and last half-second at both boundaries. The start should land on the intended word, beat, or transient, and the end should not clip the tail of a sustained note or the room tone of a recording. If the boundary sounds wrong, enter a slightly earlier start or slightly later end, regenerate the WAV, and listen again. Because the previous download is replaced and its local URL released on the next cut, repeating this loop is cheap.
Keep the original source file until the new WAV has been confirmed. Browser-based cutters overwrite the working buffer and the temporary download URL when a new file is loaded or when the tab closes, so the only copy that survives across sessions is the file on disk. For fades, lossless compressed-frame cutting, metadata preservation, or production mastering, hand the work to a dedicated editor rather than pushing a single-purpose browser tool past its design. Picking the right approach up front is faster than recovering from a poor cut.