Cutting audio in a browser starts with three actions: choose a file your browser can decode, enter two time markers measured in seconds, and click a button to export the selected range as an uncompressed WAV. The whole process runs locally, so the source file and the trimmed result never leave your current tab, with no upload step and no conversion server involved. New users often assume cutting requires installing a desktop editor or creating an account, but the practical path for a one-off trim is to open a browser page, point it at a local audio file, and read the decoded duration, sample rate, channel count, and frame count that the tool displays before the cut is made. Once those numbers are visible, the cut itself comes down to typing a start time and an end time and confirming that the end is later than the start and does not exceed the exact decoded duration. What separates a beginner-friendly session from a frustrating one usually comes down to checking format support and size limits before clicking the cut button.
What Getting Started With Audio Cutting Actually Means
People who need to cut audio typically have one goal in mind: keep a single section of a longer file and discard the rest. The reasons tend to be small and practical, such as a phone recording that picked up background noise, a song where only the chorus matters, a podcast snippet to send to a colleague, or a clip that has to fit a video timeline. Cutting is the simplest form of audio editing because it does not change pitch, add effects, normalize volume, or remix channels. It only selects a continuous range of samples and writes that range to a new file.
The reason getting started feels uncertain for newcomers is that audio tools split into two very different worlds. Desktop editors like Audacity, Adobe Audition, or GarageBand install locally and operate on waveform views. In-browser tools work on the same sample data but never install anything, and they run the entire decode-and-encode loop on the current page. For a one-off trim with a known start and end, the in-browser path is usually faster because there is no install step, no account, and no upload of the source file. The Audio Cutter page is built around that exact task: pick a file, read the decoded numbers, set two time markers, and export a WAV.
Three Things to Confirm Before You Open the Tool
Before opening any browser-based cutter, three checks save time and prevent mid-task errors:
- The file is one your browser can decode. The file picker recognizes common MP3, WAV, M4A, AAC, Ogg, WebM, and FLAC names and MIME types, but actual decoding depends on the codecs built into the current browser. Safari, Chrome, Firefox, and different operating systems ship different decoder sets, so an Ogg or FLAC file that decodes in Firefox may not decode in Safari. A mislabeled, encrypted, or damaged file produces a clear decode error rather than a silent failure, and the tool does not install a codec, send the file to a conversion server, or substitute another source.
- The encoded file is at most 25 MB. The browser rejects anything larger before decoding starts. Long podcasts encoded at low bitrate are usually the easiest way to stay under this limit, while high-bitrate music files and long lossless tracks are more likely to exceed it.
- The decoded audio stays inside the working limits. After decoding, the tool checks for a 15-minute duration, eight channels, a 192 kHz sample rate, and a 30 million-sample total across all channels. High-rate or multichannel files may reach the sample boundary before the duration boundary, because the sample count multiplies across all channels. Nothing is shortened automatically, so an over-limit file is rejected with a message rather than truncated.
For readers who want a deeper look at the privacy side of these checks, the walkthrough on whether audio files are uploaded during an in-browser cut covers the local-only processing model in detail.
Cut Audio in Your Browser in Three Steps
The cut itself is short. After opening the page and choosing a file, the rest is just three actions.
- Choose a browser-decodable audio file. Click the file picker and select an audio file from your device. Stay under the 25 MB encoded-file limit and prefer formats your current browser actually decodes. Wait for the page to display the decoded duration, sample rate, channel count, and frame count before continuing. These numbers describe the decoded working buffer, not necessarily the source file's encoded rate.
- Enter a start time and an end time. The start must be a non-negative number and must come before the end. The end must be later than the start and must not exceed the exact decoded duration shown on the page. Both values are rounded to the nearest decoded sample-frame boundary at the AudioBuffer sample rate, the start frame is included and the end frame is excluded, and a selection that rounds to less than one full frame is rejected rather than producing an empty file.
- Select Cut and export WAV, preview, then download. Click the cut action. The page encodes a new RIFF/WAVE file from the selected frame range, shows the output duration and file size, plays the result, and offers a download. Changing either time field clears the previous WAV and releases the prior download URL, and choosing another file clears the old decoded buffer, players, errors, and result.
How the Cut Boundaries Are Calculated
The tool does not cut by a visible waveform guess or by a wall-clock timer. It converts the start and end seconds to the nearest frame indices using the decoded AudioBuffer sample rate, includes the start frame, and excludes the end frame. The production exporter and the isolated tests share the same frame-range function, so the duration displayed after cutting equals the selected frame count divided by the decoded sample rate, not an unrelated timer estimate.
Web Audio may resample the source to the AudioContext sample rate while decoding, which means the displayed sample rate describes the decoded working buffer and the exported WAV, not necessarily the source file's encoded rate. A 48 kHz FLAC decoded in a 44.1 kHz AudioContext becomes a 44.1 kHz buffer, and the cut WAV inherits that 44.1 kHz rate. The audio documentation on AudioBuffer and on decodeAudioData describes how the sample rate is reported on the buffer object and how resampling happens during decode.
Floating-point Web Audio samples are clamped to the PCM range from -1 through 1 before encoding. Negative full scale becomes -32768 in the WAV, positive full scale becomes 32767, and non-finite values are written as silence. Multiple channels remain separate and are interleaved in their original channel order, so a stereo source stays stereo up to the eight-channel working limit.
What the WAV Download Actually Contains
Every download is a newly encoded file, not a slice of the original. The result is always a RIFF/WAVE container with format code 1 (PCM), the channel count and sample rate from the decoded buffer, 16 bits per sample, little-endian signed integer samples, and a 44-byte header followed by the audio data. This produces three predictable consequences for first-time users:
- The original compressed encoding is gone. An MP3, AAC, Ogg, WebM, or FLAC source becomes an uncompressed PCM16 WAV. Tags, album art, cue points, chapters, loudness metadata, and encoder settings are not preserved.
- The output can be much larger than the source. PCM16 WAV stores two bytes per selected frame per channel, plus a 44-byte header. A 60-second stereo clip at a 44.1 kHz decoded sample rate produces 60 × 44,100 × 2 channels × 2 bytes = 10,584,000 bytes of audio data, plus 44 bytes for the header, for a total of 10,584,044 bytes (about 10.1 MB).
- The channel layout is preserved. A stereo source stays stereo, and sources with more channels retain them up to the eight-channel limit. Playback software must support the resulting channel layout.
For a clear comparison, the table below shows the input handling and the output you can expect.
| Property | Input file | Output WAV |
|---|---|---|
| Encoding | Compressed (MP3, AAC, Ogg, WebM, FLAC, etc.) when the browser can decode it | Uncompressed PCM16, little-endian, signed |
| Container | Source container and codec | RIFF/WAVE, format code 1 |
| Sample rate | Source encoded rate (not directly used) | Decoded buffer rate after any Web Audio resampling |
| Channels | Up to 8 (decoded) | Same as decoded, up to 8 |
| Metadata | Tags, album art, chapters, cue points | None preserved |
| File size | Depends on codec and bitrate | Frames × channels × 2 bytes + 44-byte header |
Verify the Cut Before You Use the File
Because the WAV is built from frame indices rather than a visible waveform, it is worth previewing the result before treating it as final. The page plays the encoded WAV back through the same browser tab, which makes it easy to listen for the actual content at the start and end boundaries. If the goal is to capture spoken words, confirm the first syllable lands inside the selection. If the cut targets a musical transient, confirm the downbeat or note onset is not clipped on either side.
The page also displays the output duration and the file size before download, which serves as a sanity check against the time markers you typed. A discrepancy between the displayed output duration and the duration implied by the start and end times is a signal that frame rounding pushed the boundaries inward, and the cut is still valid but slightly shorter than the typed numbers. Audio contexts are closed after decoding and during cleanup, and in-flight reads and decodes are guarded so an older job cannot overwrite a newer selection. For a step-by-step approach to this check, the guide on verifying a result after an in-browser cut walks through the same boundary checks.
When a Browser Cut Is Not Enough
A browser cut produces a clean, frame-accurate WAV with no fades and no metadata, which is the right shape for most one-off tasks. There are a few cases where a dedicated editor is the better tool. The cut needs a fade-in, fade-out, or crossfade so the boundary does not click. The output must preserve ID3 tags, album art, or chapter markers from the source. The cut has to happen inside a compressed container without re-encoding, which is a different operation from a sample-accurate PCM re-export. The audio needs noise reduction, EQ, normalization, or mastering after the trim. The source exceeds the 25 MB file limit or the 15-minute decoded duration, in which case the tool rejects it outright rather than truncating it.
In all of these cases, keeping the original file is the safest path: the browser cut can be a fast first pass, and a desktop editor can refine the result later. 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 dedicated editor when the task needs waveform-level fades, lossless compressed-frame cutting, metadata preservation, or production mastering.