How natural-pause cutting works inside your browser.

When you select an audio or video file, AutoSilenceCut does not upload the file to a remote server. Instead, it reads the file using the browser’s native FileReader API as an ArrayBuffer.

The raw audio data is then passed to an in-memory AudioContext.decodeAudioData() pipeline. The browser’s underlying C++ media engine decompresses the audio stream (whether MP3, AAC, FLAC, Vorbis, or PCM) into planar 32-bit floating-point PCM audio buffers in RAM.

Rather than relying on naive peak amplitude thresholds that misinterpret quiet consonants as silence, AutoSilenceCut computes Root Mean Square (RMS) energy across sliding 20-millisecond audio analysis windows:

The analyzer continuously measures the ambient noise floor of the recording and flags contiguous windows that fall beneath the calibrated threshold. Windows that remain quiet longer than the configured minimum silence duration (e.g. 0.80s) become candidate pause cuts.

Blind silence removers delete 100% of the silence between words, clipping off vocal release bursts and causing speech to sound rushed and breathless.

AutoSilenceCut uses a retained cushion algorithm. When a 2.0-second silence is trimmed, AutoSilenceCut does not delete 2.0 seconds. Instead, in Natural mode it keeps a 0.32-second quiet cushion (0.16s after the preceding word, and 0.16s before the subsequent word). This preserves the natural cadence and breathing rhythm of the human voice.

When two audio segments are spliced together at non-zero voltage points, the instant change in voltage produces a noticeable acoustic "click" or "pop".

During offline audio rendering via OfflineAudioContext, AutoSilenceCut applies an automatic 8-millisecond equal-power cosine crossfade curve across every join boundary. This smoothly interpolates the audio waveforms and ensures completely seamless, click-free listening.

Every detected pause is assigned a unique immutable identifier and tracked in a reactive state store. Your source audio is never modified destructively. Decisions to keep, restore, or adjust thresholds are recorded in an action stack with full undo/redo capabilities.

When you export your file, the browser compiles the edited segments into a pristine 16-bit PCM WAV binary entirely in RAM and triggers a standard browser download. When you close the tab, all memory buffers are revoked and purged.