How to mute a section of loud background noise in a clip
- Step 1Locate the noise burst in seconds — Scrub the clip and find where the noise starts and ends, in seconds. Transient noises (slam, bump) are often under a second — use decimals.
- Step 2Decide if anything wanted overlaps — If someone is talking over the burst, muting silences that too. If the noisy stretch has nothing to keep, muting is ideal; otherwise consider a denoiser instead.
- Step 3Drop the clip onto the tool — Open the audio region muter and drag the clip in. FFmpeg.wasm runs in your browser — no upload. MP4, MOV, MKV, WebM, AVI, M4V, TS accepted; MP4 out.
- Step 4Set Start (s) and End (s) — Enter the noise window. Start is the lower bound, End must be strictly greater than Start (or the tool stops with End time must be after start time). Decimals are rounded to 3 places.
- Step 5Run the mute — FFmpeg silences the window with
volume=0and copies the video stream untouched. The noise burst is replaced with clean silence. - Step 6Verify and repeat for more bursts — Play across the boundaries. For several noise events, feed the output MP4 back in and run another pass per event.
The only two controls (verified against the tool UI)
The options panel for this tool has exactly two numeric fields. There is no beep/tone option, no fade, no waveform scrubber, and no multi-region list — every claim here is checked against the actual client component.
| Control | What it is | Range | Default |
|---|---|---|---|
| Start (s) | Start of the mute region in seconds. Passed to FFmpeg as the lower bound of between(t, start, end). Decimals allowed (rounded to 3 places, e.g. 12.480) | 0 to clip duration | 0 |
| End (s) | End of the mute region in seconds. Upper bound of the between() expression. Must be greater than Start or the tool stops with *End time must be after start time* | 0 to clip duration | 0 |
| Region count | One region per pass. The tool applies a single between(t, start, end) window. To silence several separate sections, run the tool once per section (the output of one pass is the input to the next) | 1 | 1 |
| Replacement | Silence only — the region's volume is set to 0. There is no beep, tone, hum, or audio substitution. The registry note is explicit: silence is the default to avoid copyright on common beep sounds | fixed | silence |
Mute the region vs. denoise the track
This tool is a time-based mute, not a noise-reduction filter. Use this comparison to confirm muting is the right approach for your noise.
| Noise type | Mute the region (this tool)? | Why |
|---|---|---|
| One-off slam / bump / blast with nothing to keep | Yes — silence the window | Transient, localised; nothing wanted is lost |
| Traffic / crowd burst during silence between lines | Yes | The window has no dialogue to preserve |
| Loud noise over wanted speech | No (caveat) | Muting silences the speech too; there's no source separation |
| Steady hiss / hum under continuous dialogue | No | This isn't a denoiser/EQ/noise-gate — use a dedicated denoising tool |
| Wind across a whole outdoor clip | No | Global problem; muting would silence everything wanted |
What actually happens to your file
Grounded in the FFmpeg command the tool runs. The video stream is copied bit-for-bit; only the audio is touched. This is a mute, not noise reduction — it sets the window to silence rather than filtering noise out of usable audio.
| Stage | FFmpeg behaviour | Effect on your file |
|---|---|---|
| Video stream | -c:v copy — the video is stream-copied, never decoded or re-encoded | Zero quality loss on the picture. No generation loss, no re-compression artefacts, frame-identical to the source |
| Audio filter | -af volume=enable='between(t,START,END)':volume=0 — audio plays at full volume everywhere except the region, where volume drops to 0 | Hard silence inside the region; original audio everywhere else |
| Audio re-encode | -c:a aac -b:a 192k — the entire audio track is re-encoded to AAC at 192 kbps, not stream-copied | One transcode pass on the whole track. AAC 192k is transparent for speech/most music, but it is a re-encode, not a copy |
| Container | Output is always written as out_*.mp4 | You always get an .mp4 back, whatever container you fed in (MOV, MKV, WebM, AVI, M4V, TS) |
| Where it runs | FFmpeg.wasm inside your browser tab — no upload | The file never leaves your device. Nothing is sent to a server |
Cookbook
Timing transient noise bursts. They're often sub-second, so use decimals and keep the window tight.
Silence a door slam
A slam spikes between 0:15.2 and 0:15.7. A tight sub-second window kills it.
Start (s): 15.2 End (s): 15.7 -af volume=enable='between(t,15.200,15.700)':volume=0 Result: the slam is gone; surrounding room tone intact.
Mute a camera bump between sentences
A bump landed in the pause between two lines — nothing wanted is lost.
Pause with bump: 8.0 - 8.6 Start (s): 8.0 End (s): 8.6 The bump is silenced; both lines around it are clean.
Two noise events, two passes
A bump early and a truck later. One pass each, chaining outputs.
Pass 1 -> Start 8.0 End 8.6 (download) Pass 2 -> reload, Start 52.0 End 54.5 (download) Both bursts silenced; video copied each pass.
Widen if the tail of the noise survives
If you still hear the ring-out of a slam, extend End slightly.
First try: Start 15.2 End 15.6 -> tail audible Second try: Start 15.1 End 15.9 -> clean
When NOT to use this tool
If the noise sits under someone talking, muting silences the speech too. Use a denoiser instead, not this tool.
Noise overlaps dialogue 30-35. Muting 30-35 silences the dialogue as well. -> Use a dedicated denoise/noise-gate tool, not a region mute.
Edge cases and what actually happens
Wanted audio overlaps the noise burst
CaveatMuting is time-based, not spectral — if dialogue or other wanted sound plays under the noise, silencing the window silences it too. There is no source separation or noise-gate here. Only mute windows where nothing you need is present.
Trying to remove steady background hiss
Wrong toolThis tool mutes a time window; it does not reduce continuous noise. For steady hiss, hum, or wind under dialogue, you need a denoiser/EQ/noise-gate — muting the whole track's noisy span would silence everything wanted along with the noise.
End is less than or equal to Start
RejectedIf End is the same as or earlier than Start, the tool stops immediately with *End time must be after start time. Set both Start and End in the options panel.* Set End to a value strictly greater than Start. A common cause is leaving both at the default 0.
Region runs past the end of the clip
By designThe between(t, start, end) expression simply has no frames to act on past the real end of the audio, so an End value larger than the clip duration silences from Start to the end of the audio and stops. The UI also caps the End field at the detected clip duration, so you normally cannot overshoot.
Audio gets re-encoded even outside the region
ExpectedThe command runs -c:a aac -b:a 192k, which re-encodes the whole audio track, not just the muted window. AAC at 192 kbps is transparent for speech and most music, but if you need a true stream-copy of the untouched audio, this tool is not the right choice — it always does one audio transcode.
Output is MP4 even though you uploaded MOV/MKV/WebM
By designThe tool always writes out_*.mp4. If you need the original container back (for example MKV with multiple tracks), this tool will not preserve it. Use it for the MP4 deliverable, or mute first then remux elsewhere.
Several separate sections to mute
By designEach pass mutes one window. For multiple non-adjacent sections, run the tool repeatedly: mute section 1, download, feed that MP4 back in, mute section 2, and so on. The video is stream-copied each time so the picture never degrades across passes.
Noise tail rings out past your End
CaveatSlams and bumps have a decay tail. If a faint ring survives after the window, extend End by 0.1–0.3 s. Conversely, trimming End too tight leaves an audible click at the edge.
Very large file on the Free plan
BlockedFree caps a single video at 1 GB. A 1080p hour-long export can exceed that. Pro lifts the cap to 10 GB and Pro-media to 100 GB. Because the video is stream-copied, processing is fast even on large files — the bottleneck is the size cap, not duration.
Variable-frame-rate phone footage
SupportedBecause the video is copied rather than re-encoded, VFR footage from phones and screen recorders passes through untouched. The mute window is keyed to playback time t in seconds, so the silence lands at the same wall-clock position regardless of frame timing.
Frequently asked questions
Is this a noise-reduction filter?
No. It's a time-based mute — it sets a window to silence (volume 0). There's no spectral denoise, EQ, or noise-gate. It's ideal for one-off bursts in stretches you don't need to keep.
What if someone is talking over the noise?
Muting silences everything in the window, including wanted speech — there's no source separation. Only mute windows where nothing you need is playing; otherwise use a dedicated denoiser.
Can it remove steady background hiss across the whole clip?
No — that's continuous noise, and muting the whole span would silence the dialogue too. Use a denoising tool for steady hiss, hum, or wind.
Will muting a burst hurt the video quality?
No. The video is stream-copied with -c:v copy, so the picture is frame-identical. Only the audio is re-encoded (to AAC 192k).
How tight can the mute window be?
As tight as you like — Start and End accept decimals (rounded to 3 places), so you can catch a sub-second bump without swallowing the speech around it.
What if the noise's tail still rings out?
Extend End by 0.1–0.3 s to cover the decay. If you trim too tight you may hear a click at the edge.
How do I handle several noise bursts?
Run one pass per burst: mute the first, download, reload, mute the next. The copied video doesn't degrade across passes.
Is the clip uploaded?
No. FFmpeg.wasm runs entirely in your browser tab; the file never leaves your device.
Does the silence fade in?
No — it's a hard cut to silence at both edges. There's no fade control.
What output format do I get?
Always MP4, regardless of the input container.
What if End is before Start?
The tool stops with End time must be after start time. Set both Start and End in the options panel.
How big a clip can I process?
Free up to 1 GB; Pro 10 GB; Pro-media and Developer 100 GB. No minutes cap — limits are by file size and batch count.
Privacy first
Every JAD Video tool runs entirely in your browser via WebCodecs and FFmpeg (WebAssembly). Your video files never leave your device — verified by zero outbound network requests during processing.