Skip to main content

Silence Cutter — Auto-Trim Silent Regions Online

Detect and remove silent regions from any audio recording with the Silero Voice Activity Detector. Long pauses get trimmed automatically; the kept regions glue together with optional crossfades.

Coming Soon

Silence Cutter is under active development. We're building browser-based audio tools powered by FFmpeg WebAssembly. Check back soon!

About Silence Cutter

Silence Cutter is a free, in-browser audio tool. Detect and remove silent regions from any audio recording with the Silero Voice Activity Detector. Long pauses get trimmed automatically; the kept regions glue together with optional crossfades. The page exposes a small surface — input, controls, output — so a first-time visitor can complete the job without reading documentation.

The right moment to reach for Silence Cutter is when you have a focused audio editing and conversion job that fits inside a browser tab. Open the page, drop in the file or paste your input, choose the options that matter, and the tool returns the result.

Silence Cutter is a static page plus a client-side engine. The browser does the work; there is no separate backend in the loop for the actual processing. That architecture is why the tool starts immediately, why it does not depend on the load on a remote service, and why running multiple jobs in a row does not slow it down.

Architecturally, Silence Cutter is a single-page client. The processing layer is the Silero Voice Activity Detector model running on ONNX Runtime Web (WebAssembly); the UI is a thin React shell on top. MP3, WAV, OGG, FLAC, M4A, and AAC inputs flow through the engine and the output is returned to the browser as a Blob you can save or copy. The 200 MB cap is the only hard limit and it exists to keep memory usage stable on every device.

The only practical limit is the 200 MB per-file ceiling, which keeps the tool responsive across a wide range of devices. Run the tool ten times in a row, run it ten thousand times — it behaves the same way and produces the same quality of result.

The heaviest users of Silence Cutter tend to be students preparing oral submissions, musicians sharing demos and voice-over artists exporting takes. Each group brings slightly different expectations to the tool, but the same single-page architecture serves every one of them with the same response time.

The download is delivered as `{name}-cut.wav` the moment processing completes — no email link, no "your result will be ready in 5 minutes" queue, no expiry timer. The file is generated in your browser and saved by your browser's normal download flow.

As a workflow component, Silence Cutter is the part you reach for when a single, well-defined audio editing and conversion step needs to happen. It performs that step and returns a standard file you can carry into the next part of your pipeline.

Silence Cutter is built around steady iteration on a small set of options rather than feature creep. Every additional setting attracts a slightly different audience, but a long settings panel makes the common case slower for everyone. The current controls reflect what users of the tool actually use.

Some context on why Silence Cutter exists in this form: modern File APIs, high-performance JavaScript engines, and well-maintained open-source libraries now make it possible to perform audio editing and conversion work entirely in the browser. Silence Cutter is built on top of that capability, which is why a single page can host the full pipeline.

Silence Cutter produces deterministic output: the same input plus the same options always produces the same result. That predictability matters when the result has to match an upstream specification or be reproducible later.

If you want to get the most out of Silence Cutter, three small habits help. Drag-and-drop is faster than the file picker once you get used to it. The keyboard shortcut for downloading the result is whatever your browser uses for "save link as," because the result is a normal download. And if you are working on a sensitive file, processing in an Incognito or Private window is a good extra layer — it leaves no trace in browser history when the tab closes.

When something goes wrong, the cause is usually one of three things: a malformed input, a browser that is out of memory, or a corporate proxy that is interfering with the page's static assets. The first two are easy to diagnose; the third typically requires asking your IT team to allow the Silero Voice Activity Detector model running on ONNX Runtime Web (WebAssembly) to load.

Open the workspace above to start using Silence Cutter. The engine loads on the first interaction so the page itself stays light, and once the tool is warm it processes subsequent jobs quickly. The moment the page is interactive, the tool is ready to do real work on your file.

How it works

  1. 1Open the Silence Cutter workspace above. The interface is a single page, so there is nothing to navigate.
  2. 2Add your MP3, WAV, OGG, FLAC, M4A, and AAC input by dropping it onto the page or browsing for it.
  3. 3Pick any non-default settings you need. Most users leave the defaults alone for the first run and only revisit if the result needs tuning.
  4. 4Trigger processing. the Silero Voice Activity Detector model running on ONNX Runtime Web (WebAssembly) reads your input, applies the transformation, and writes the result back into the page.
  5. 5Download the result as `{name}-cut.wav`. The file is generated in your browser and saved through your normal download flow.
  6. 6Re-run with different settings as often as you want. Each run produces a fresh output and the original file on disk is never modified.

Common use cases

FAQ

How does it know what is silence?

The Silero VAD model classifies every 32-ms frame as speech or non-speech. Frames flagged as non-speech for longer than the threshold get cut; speech regions are preserved.

Will it cut out short pauses between words?

No — the minimum-silence-duration threshold defaults to 600 ms so natural between-word pauses are preserved. Adjust the threshold if you want tighter or looser cuts.

Does it remove music too?

Music is treated as non-speech and may be trimmed. For mixed speech-and-music recordings (podcasts with background music) lower the silence threshold or run only the speech sections through the tool.

Will my audio upload?

No. The Silero VAD model (~2 MB) downloads once from our CDN; the rest of the work happens locally on the WebAudio API.

Can it remove very short pauses (vocal stutter)?

For sub-300 ms gaps use the Filler Word Remover tool — it pairs Silero with the Whisper engine so it can target specific filler words rather than just silence.

How accurate is Silence Cutter?

Silence Cutter is built on the Silero Voice Activity Detector model running on ONNX Runtime Web (WebAssembly), which is the same class of engine used by professional audio editing and conversion pipelines. For deterministic operations, the output is byte-identical to what an equivalent CLI run would produce; for operations involving a codec or a model, the result is well within the range of what comparable tools generate. If you have a specific reference output you need to match, run a small test job first to confirm the configuration produces what you expect.

Will Silence Cutter ask me to pay to download the result?

Silence Cutter is free to use. The processing runs in your browser, which keeps the per-user cost low enough that the tool can be offered openly. The download is the same file the engine produced — you can use it for as many runs as you need.

What is the maximum file size for Silence Cutter?

Inputs are capped at 200 MB per file, which keeps memory usage stable across phones, tablets and older laptops. You can run Silence Cutter as often as you need; every run produces a full-quality result.

Does Silence Cutter upload my file to a server?

Your file is processed inside your browser by the Silero Voice Activity Detector model running on ONNX Runtime Web (WebAssembly). The engine reads the file's bytes from your tab's memory, computes the result, and writes the result back into the tab. You can confirm what the page does by opening developer tools and watching the Network tab during a run — the requests you see are for the tool's static assets only.

Is Silence Cutter lossless?

Silence Cutter is built to preserve quality wherever the underlying audio format allows it. Operations that are mathematically lossless (e.g. structural transformations, lossless re-encoding) round-trip with no perceptible change. Operations that involve a lossy codec inevitably introduce small artefacts at the byte level, but the defaults aim at the sweet spot where output looks or sounds the same to a normal viewer or listener while still being meaningfully smaller or faster than the input.

Will Silence Cutter keep working in a year?

Silence Cutter is updated whenever the underlying engine releases an improvement or a bug fix. Because the tool is delivered as a static page, every visit fetches the latest version automatically — there is no "version" to manage on your end. If a particular release ever changes default behaviour, the change is documented on Favtoo's changelog so you can confirm what shifted.

Can I self-host Silence Cutter for my team?

Silence Cutter is a static page running an open-source engine in your browser, so a typical corporate firewall does not get in the way as long as it allows JavaScript and WebAssembly to load from Favtoo. For teams that need to host it themselves on an internal network, the underlying engine (the Silero Voice Activity Detector model running on ONNX Runtime Web (WebAssembly)) is open-source and can be packaged into a private build with the same behaviour. Reach out via the Contact page if that is something you are exploring.

Which browsers are supported by Silence Cutter?

Silence Cutter works in any modern browser released in the last few years — Chrome, Edge, Firefox, Safari, Brave, Arc and the major Chromium derivatives are all supported. The underlying engine relies on widely-supported web APIs, so there is nothing exotic to install. If you are on a very old browser version and the tool fails to load, updating to the latest release of your preferred browser is the only fix needed.

Compress Audio

Shrink any audio file to a smaller size by lowering the bitrate. Pick a target quality (96, 128, 192, 256, or 320 Kbps) or output format (MP3, OGG, M4A) and the file is re-encoded right inside your browser using FFmpeg WebAssembly. Nothing is uploaded — your audio never leaves your device.

Convert Audio

Convert any audio file between MP3, WAV, OGG, FLAC, M4A, AAC, and Opus right in your browser. Pick the output format and (for lossy formats) the target bitrate. Everything runs locally with FFmpeg WebAssembly — your file is never uploaded and no account is required.

Audio Recorder

Record from your microphone directly in the browser. Pick quality (high, medium, low), toggle echo cancellation, noise suppression and auto-gain, then save to WebM/Opus or M4A/AAC. Audio is captured locally — nothing is uploaded.

Text to Speech

Type or paste text, pick a system voice, and listen instantly. Adjust speaking rate (0.5×–2×), pitch, and volume in real time. Uses your browser's built-in Web Speech API — no cloud TTS, no API keys, no costs.

Tone Generator

Generate a pure tone at any frequency from 20 Hz to 20 kHz. Pick a sine, square, triangle, or sawtooth waveform, choose duration, amplitude, and mono/stereo. Exports a 16-bit PCM WAV file at 44.1 kHz with built-in click-preventing fades.

Silence Generator

Generate a perfectly silent WAV file of any length from 1 second up to 1 hour. Pick mono or stereo, get a 16-bit PCM WAV at 44.1 kHz. Useful as padding between clips, intro silence, leader audio for video timing, or test material.

White Noise Generator

Generate white, pink, or brown noise as a 16-bit PCM WAV file. Pick noise type, duration up to 1 hour, amplitude, and mono/stereo. Useful for sleep, focus, masking distractions, audio testing, and as a backing layer for ambient music.

Metronome

A precise browser-based metronome powered by the Web Audio API. Set BPM from 30 to 300, choose a time signature, accent the first beat, and use tap-tempo to sync. Click timing is sample-accurate using lookahead scheduling — much steadier than typical JavaScript setInterval beats.

View all Audio Tools