The result after cutting audio is a freshly encoded uncompressed PCM16 WAV file, and the standard way to check it is to preview the trimmed clip in the browser before downloading. Audio Cutter exposes exactly that step: after you set start and end times, the page lets you select "Cut and export WAV," play back the preview, and only then trigger a local download. Before you commit, you can read four numbers directly on the page — decoded duration, sample rate, channel count, and frame count — and the displayed cut duration is computed from the actual frame count at the decoded sample rate rather than from an unrelated timer. This means the preview you hear and the file you save describe the same range to the nearest decoded sample frame. That built-in preview step is the difference between guessing at your cut and confirming it, because the boundaries are exact and the source audio never leaves your machine during decode, frame selection, encoding, preview, or download.
Why Previewing the Cut Belongs in the Workflow
Cutting audio without checking it means trusting the math. The preview step in Audio Cutter exists because the export happens on the nearest decoded sample-frame boundary, not on the raw seconds you typed. If your typed value lands between two frames, the tool rounds to the nearest one, and the preview reflects that exact frame range. Listening to it before download is the only reliable way to confirm the spoken word, breath, or musical transient sits cleanly inside the kept range rather than getting clipped off at the edge.
The displayed cut duration is the selected frame count divided by the decoded sample rate. Because that same frame-range function powers both the production exporter and the isolated tests, the previewed duration and the saved duration agree exactly — they are not two independent estimates that could drift apart. This is what "checking the result" really means here: listening to the file the way it will actually play back, with the same frame indices that will be written into the PCM16 WAV header and sample block.
Limits That Affect What You Can Check
Before you can preview a cut, the source file has to clear several limits. Audio Cutter reports them on the page so you can verify them before cutting:
| Limit | Maximum | Why it matters for the result |
|---|---|---|
| Encoded input file size | 25 MB | Larger files are rejected before decode starts. |
| Decoded duration | 15 minutes | Longer clips are rejected after decode. |
| Decoded sample rate | 192 kHz | Higher rates are rejected. |
| Channel count | 8 | Surround layouts up to eight channels are retained in the WAV. |
| Total channel-samples | 30,000,000 | High-rate or multichannel files may reach this bound before the duration limit. |
The 30-million-sample limit interacts with the rate and channel count: a stereo file at 48 kHz can run to about 5 minutes 12 seconds before that bound kicks in, while a mono file at 16 kHz can run far longer. The tool does not shorten anything automatically — over-limit files are rejected with a clear message — so checking the page-displayed numbers first is itself part of the verification workflow.
Cut and Verify the Result: The Exact Steps
- Open Audio Cutter in your browser and choose a file from the picker. MP3, WAV, M4A, AAC, Ogg, WebM, and FLAC names and MIME types are recognized; actual decoding depends on your browser's Web Audio support.
- Wait for the Web Audio decode to complete. The page then shows the decoded duration, sample rate, channel count, and frame count — read them and confirm the file is what you expected before you set any times.
- Enter a non-negative start time in seconds and a later end time in moments. End must be greater than start, start cannot be negative or at the very end, and end cannot exceed the exact decoded duration.
- Select "Cut and export WAV." The tool rounds your times to the nearest decoded sample-frame boundary using the AudioBuffer sample rate — the start frame is included and the end frame is excluded.
- Preview the resulting PCM16 clip in the page's player. Listen for the boundary words or transients; if they sit cleanly inside the kept range, proceed.
- Download the WAV. The displayed output duration and file size on the page let you confirm what is about to be saved. Changing either time field clears the previous WAV; cutting again replaces and releases the prior download URL.
After download, you can open the file in any standard audio player to double-check, but the in-page preview already plays the same sample buffer that will be encoded, so a clean preview is a strong signal the saved file will match. For a walkthrough that goes deeper into the initial cut step, see how to cut an audio recording in your browser.
What the Cut WAV Actually Contains
Knowing what is and is not preserved is itself a check you can do before download. The cut file is a freshly built RIFF/WAVE container, written as interleaved little-endian signed 16-bit PCM samples in the original channel order. The 44-byte header records PCM format 1, channel count, decoded sample rate, byte rate, block alignment, and 16 bits per sample, plus the exact data size.
What is preserved: the selected frames, the channel count and order, and the decoded sample rate — meaning if your source decoded to stereo at 44.1 kHz, the WAV is stereo at 44.1 kHz.
What is not preserved: the original MP3, AAC, Vorbis, Opus, or FLAC encoding; tags; album art; cue points; chapters; loudness metadata; encoder settings; or any other container field. Web Audio may resample the source to the AudioContext sample rate while decoding, so the rate on the page — and in the WAV — describes the decoded working buffer, not necessarily the source file's encoded rate.
Floating-point Web Audio samples are clamped to the PCM range of -1 through 1. Negative full scale becomes -32768, positive full scale becomes 32767, and non-finite values are written as silence. Because PCM16 is uncompressed, the WAV can be far larger than a short compressed source.
A Concrete File-Size Example
If the cut range is 10 seconds long, the source decoded to stereo (2 channels), and the decoded sample rate is 44,100 Hz, the math is:
- frames = 44,100 × 10 = 441,000
- data bytes = 441,000 × 2 channels × 2 bytes per sample = 1,764,000 bytes
- header = 44 bytes
- total = 1,764,044 bytes (about 1.68 MB)
The page reports this output duration and file size before you download, so you can sanity-check that the saved file matches the previewed range without opening a separate tool. If the displayed size looks wildly different from what the formula predicts, that itself is a signal to re-check the entered times before saving.
When a Browser Cut Is Not Enough
For most quick verification jobs — confirming an interview answer sits cleanly in the kept range, trimming a song intro for a test clip, pulling a single sentence from a longer recording — previewing the cut WAV in the browser is enough. The decoded sample rate, the exact frame range, and the in-page preview all describe the same file the download button produces.
Reach for a dedicated editor instead if you need waveform-level fades on the cut boundaries, lossless compressed-frame cutting without a decode step, full metadata and tag preservation, batch processing of many files at once, or production mastering with normalization, EQ, and loudness targets. Audio Cutter does not offer resampling control, remix, fade, normalize, denoise, pitch shift, or compression of the WAV — those are intentional omissions, not hidden toggles. The in-page preview answers the everyday "did this cut land where I wanted?" question; a full digital audio workstation answers the deeper "is this master production-ready?" question.
Recap
The result after cutting audio is a clean PCM16 WAV, and the most reliable way to check it is the in-page preview step that plays back the exact frame range about to be written to disk. Read the four displayed values (decoded duration, sample rate, channel count, frame count), set the start and end times, cut, preview, then download — and if anything sounds off at the boundaries, adjust and re-cut. For dependable work, preview the cut WAV, confirm the spoken words or musical transient at both boundaries, keep the original file, and reach for a heavier editor only when you need waveform-level fades, lossless compressed-frame cutting, metadata preservation, or production mastering.