AudioCutLabAUDIO EDITOR

Trim · Fade in and out · Peak normalize · WAV export

Cut audio to the millisecond without sending it anywhere

Load a WAV, MP3, M4A, OGG or WebM file, or generate a four-second test tone, then drag the selection over the waveform, type the start and end to the millisecond, add fades, normalize the peak to -1, -3 or 0 dBFS and download a 16-bit or 24-bit WAV at 44.1 kHz, 48 kHz or the rate the file already had.

In short

AudioCutLab trims, fades and peak-normalizes an audio file inside the browser tab. The file is decoded with the Web Audio API on your own device, the waveform is drawn on a canvas with a handle for each edge, and the result is written as 16-bit or 24-bit PCM WAV by a small encoder that ships with the page. No audio is uploaded and no audio library is loaded from a CDN.

Edits Trim · Fade · NormalizeReads Whatever the browser decodesWrites WAV PCM, 16 or 24-bitServer uploads 0 bytes, 0 requests

Audio editor

Waveform

No file loaded

Load an audio file or generate a test tone

0:00.000
Four seconds of 440 Hz + 660 Hz, generated locally.
Length
-
Rate
-
Channels
-
File
-

Read in this tab only. No upload, no account.

Trim

Set both edges to the millisecond, or drag on the waveform.

0:00.000 → 0:00.000

Selection: -

Fades and level

Fades are linear ramps inside the selection.

-

-

Export

Only WAV is written: an MP3 or OGG encoder would have to come from a CDN.

Features

What the editor does

Six things that happen in the tab, not on a server.

TRIM

Two edges, one millisecond at a time

Each edge has a slider across the whole file and a seconds plus milliseconds pair, so 1 s 250 ms is typed rather than nudged towards. The selection length is printed beside them and both edges are repeated as minutes, seconds and milliseconds.

WAVEFORM

The waveform is the selection control

The canvas draws the real peak envelope of the file, dims everything outside the selection and marks the two fades as dashed ramps. Pressing and dragging on the waveform moves the nearest edge, which is quicker than reaching for a number field on a phone.

FADE

Linear ramps with an exact endpoint

Fade in and fade out are set in seconds and applied frame by frame as a straight line from silence to full gain, so the first and the last frame of the selection are exactly zero. If both fades are longer than the selection they are shortened together so that they meet instead of overlapping.

NORMALIZE

Peak normalize, with the gain shown

The tool scans the trimmed selection for its loudest frame and applies one gain so that peak lands on the target you chose: -1, -3 or 0 dBFS. The multiplier (for example x1.41, +3.01 dB) is printed before you export, and the peak of the finished file is measured again and shown in the output panel.

EXPORT

16-bit or 24-bit PCM WAV

Choose the bit depth, the sample rate (original, 44.1 kHz or 48 kHz) and the channels (as in the file, mono, or stereo). The RIFF header, the byte count and the frame count are written by the page itself, and the file opens in any editor or player.

LOCAL

Nothing leaves the tab

There is no upload, no fetch, no websocket and no analytics. The only external request on the page is the Google AdSense loader; the audio path is the browser's own decoder plus the PCM writer in this page.

How to use it

Four steps, one download

The whole edit is set before anything is written, so nothing is rendered twice.

01

Load or generate

Drop an audio file on the stage, choose one with the file button, or press the test tone button for four seconds of 440 Hz plus 660 Hz to try the controls with.

02

Set the selection

Drag on the waveform or type the start and end. Both edges are held to the millisecond, and the end can never sit closer than 10 ms to the start.

03

Shape the edges and the level

Set the fades in seconds and pick a normalize target. The selection's current peak and the gain that will be applied are shown before anything is written.

04

Render and download

Press the download button: the selection is trimmed, faded, gained and, if you asked, resampled and mixed, then written as WAV. The output panel repeats the frame count, rate, channels, depth, peak and file size read from the file itself.

Formats

What comes in, what goes out

The input list belongs to the browser; the output list belongs to this page. Both are stated plainly rather than promised.

InputHow it is readOutputNote
WAV (PCM 8/16/24/32-bit, float)Browser decoderWAV 16/24-bitInteger PCM is copied frame for frame; a float source is converted to the depth you pick.
MP3Browser decoderWAVDecoded once when the file is opened; the WAV adds no second lossy step.
M4A / AACBrowser decoderWAVWorks wherever the browser carries an AAC decoder, which is most of them.
OGG / OpusBrowser decoderWAVChrome and Firefox decode it; Safari generally does not.
WebM (audio track)Browser decoderWAVCommon for recordings made in a browser.
FLACBrowser decoderWAVDepends on the browser build. When decoding fails the message names the file.
MP3, OGG or M4A file outNot offered—An encoder for those formats would have to be loaded from a CDN, so the page does not pretend to offer them.

The same file may decode in one browser and not in another; that limit is the browser's, not the page's. The WAV writer is the page's own and behaves the same everywhere.

Inside the page

The arithmetic behind the buttons

Every step is a few lines of JavaScript applied to the channel data of the decoded file.

decodetrimfadepeak scangainresamplePCM 16/24RIFF header
i0 round(start x sampleRate)n i1 - i0 framesfade up out[i] x= i / (N-1)gain 10^(target dBFS / 20) / peak16-bit round(s x 32767)24-bit round(s x 8388607)

Trimming copies the frames between round(start x sampleRate) and round(end x sampleRate) of every channel into a new buffer. Nothing is re-encoded at that point: the frames are the decoder's own, and no frame inside the cut is dropped or doubled.

Fades multiply each frame by a straight line. In a fade of N frames the i-th frame is multiplied by i/(N-1) on the way in and by (N-1-i)/(N-1) on the way out, so the outer frame is exactly zero and the inner frame is untouched. When both fades together are longer than the selection they are scaled down until they meet exactly.

Normalization finds the largest absolute frame in the faded selection and multiplies every channel by the same factor, 10^(target/20) divided by that peak. One factor for all channels keeps the stereo image where it was. The target is a peak ceiling, not a loudness.

A change of sample rate or channel count goes to the browser's OfflineAudioContext, which resamples the buffer and mixes stereo to mono as (L+R)/2. When the rate and the channels already match, that stage is skipped so the samples stay exactly the ones the decoder produced.

The WAV writer builds the 44-byte RIFF header (PCM, 16 or 24 bits, the chosen rate and channels) and writes the samples little-endian, clamped at full scale. Frames x channels x bytes per sample is the data size, so the header length and the file length always agree.

The decoder is opened at the rate the file declares, read from the container header (RIFF/WAVE, AIFF, FLAC, Ogg, MP3 frame header or the MP4 mdhd box), so loading a 48 kHz file does not quietly resample it to 44.1 kHz. When that declaration cannot be read - a WebM or a stream with no header the page understands - the browser's default rate is used and the message above the waveform says so; "original rate" then means the rate the file was decoded at, which the source line shows.

Questions

Questions people ask first

Is my audio uploaded?

No. The file is read with the File API into the tab's memory and decoded there; the page makes no request that carries it. Opening the network panel while trimming and exporting shows only the AdSense loader.

Which formats can I open?

Anything this browser can decode: WAV, MP3, M4A/AAC, OGG/Opus and WebM in the common browsers, and FLAC in some builds. When a file cannot be decoded the message names it and suggests WAV or MP3.

Why is there no MP3 export?

An MP3 encoder is a sizeable library that would have to be loaded from a CDN, which this page does not do. Rather than ship a button that fails, only WAV output is offered, in 16-bit and 24-bit PCM.

Does normalize make a file as loud as a streaming release?

No. It moves the peak to a ceiling such as -1 dBFS, which prevents clipping, but it does not equalize perceived loudness. Two files normalized to the same peak can still sound very different, because loudness follows the average level, not the peak.

Is the trim sample-accurate?

The cut happens at the frame nearest the millisecond you type, so it is accurate to one frame of the source rate: 1/44100 s at 44.1 kHz. The fields cannot express anything finer than a millisecond, but no frame inside the cut is dropped or duplicated.

Does exporting twice lose quality?

The output is PCM WAV, so exporting from a decoded buffer adds no further lossy step. Decoding a compressed source was the single lossy step, and it happened when the file was opened. Rendering the same selection twice produces byte-identical files.

How long a file can it handle?

The limit is the tab's memory, not a set number: a decoded minute of stereo audio at 44.1 kHz takes about 21 MB. Files longer than ten minutes still load, but the page says that the tab may become slow.

Does it work offline?

Yes, once the page has loaded. The decoder, the waveform drawing, the processing and the WAV writer are all inside the page, so disconnecting the network and pressing the download button still produces a file.

Limits

What this tool does not do

Peak, not loudness

The normalize targets are peak ceilings. The page does not measure LUFS or RMS and does not claim to.

No MP3, OGG or AAC output

Those formats are read when the browser can decode them and are never written: an encoder in the page would mean a CDN library.

Resampling is the browser's

Turning 44.1 kHz into 48 kHz goes through OfflineAudioContext. It is a good resampler, but it is not a mastering-grade sample-rate converter.

One file at a time

There is no batch queue and no project file. One audio file is open in the tab, and reloading the page clears it.

What the page touches

  • Reads — The audio file you choose, in the tab only
  • Writes — One WAV download for each press of the button
  • Stores — Only the theme choice, in localStorage
  • Sends — Nothing that carries your audio