Noise Gate in Audacity: Reduce Noise Without Chopping Tails (2026)

Audacity 4 Cleanup Guide · Updated September 6, 2026

A noise gate is not the final step every AI track needs. It is a conditional tool for turning down low-level noise when the wanted signal falls below a threshold.

That makes it useful when residual hiss or room-like noise becomes noticeable between phrases, notes or sections. It does not remove that same noise while louder music is playing.

First: decide whether a noise gate is the right tool

Noise mainly between phrases

Good candidate. If the noise is masked while the music plays but obvious during pauses, a gate can reduce those quieter passages.

Steady hiss under the entire song

Start with Noise Reduction. A gate closes only when the signal drops below threshold; it does not clean noise underneath active vocals or instruments.

One ugly gap or isolated silence

Manual edit may be better. A fade, local gain change or clean replacement can be more transparent than processing the entire track.

Clicks, pops or digital glitches

Wrong tool. Use Repair, Click Removal or a local source-level fix depending on the artifact.

The key distinction: Noise Reduction tries to reduce a learned noise profile across the selected audio. A noise gate instead attenuates audio when its level falls below a threshold. Those are different jobs.

Do you need a gate after Noise Reduction?

Sometimes. Audacity specifically notes that a gate can be useful after Noise Reduction because it may let you use less aggressive noise reduction overall, then control the remaining noise during quieter passages.

But this is not a mandatory chain. If the track already sounds natural after repair or Noise Reduction, stop. Do not add another process simply because it exists.

If the unwanted sound remains present underneath active music, go back to the Noise Reduction guide rather than forcing the gate to solve a problem it cannot solve.

A safer Noise Gate workflow in Audacity 4

Keep an untouched version. Duplicate the track or save a version before gating so you can compare the processed result against the source.
Find a representative quiet/noise section. The beginning of your selection should contain noise without wanted music if you plan to use Analyze Noise Level.
Open Effect → Noise Removal and Repair → Noise Gate. Choose Analyze Noise Level. Audacity analyzes the first half-second of the selection and reports a suggested threshold, so the beginning of that selection should be pure background noise.
Choose a short test region containing both noise and wanted audio. Do not process the whole song until you know how the gate behaves around real phrases, attacks and decays.
Temporarily use very strong Level Reduction only to test the threshold. Audacity's documented workflow uses -100 dB while finding the threshold because it makes gate opening and closing obvious. In the current Audacity 4 control range, reductions of about -96 dB or lower effectively silence the gated audio. This is a diagnostic test—not a recommended final sound.
Adjust the threshold until wanted audio stays open and noise-only passages close. Listen especially to breaths, quiet words, reverb tails, cymbal decay, pads and soft instrument endings.
Back off the Level Reduction. Once threshold behavior is correct, use the least aggressive attenuation that makes the residual noise acceptable. Full digital silence is rarely necessary.
Tune Attack, Hold and Decay by ear. These controls determine how naturally the gate opens, stays open and closes around musical material.
Keep stereo linking on for conventional stereo music unless you have a specific reason not to. Independent gating can make the stereo image move strangely from side to side.
A/B the result in context. If the track sounds cleaner but less alive, the gate is too aggressive—or unnecessary.

Audacity 4 Noise Gate control reference

These are the current control ranges and defaults in Audacity 4. They are useful for understanding the interface, but they are not JR presets and they are not universal AI-music settings.

Gate Threshold

Range: -96 to -6 dB.
Default: -40 dB.
The signal below this level is attenuated. Too high can remove soft wanted audio; too low can leave noise behind.

Level Reduction

Range: -100 to 0 dB.
Default: -24 dB.
More negative values create stronger attenuation. Around -96 dB or lower, gated audio is effectively silenced.

Attack

Range: 1–1000 ms.
Default: 10 ms.
Controls how the gate opens. Audacity uses lookahead to help protect the front of words and transients.

Hold

Range: 0–2000 ms.
Default: 50 ms.
Keeps the gate open after the signal falls below threshold and can protect sustains and tails.

Decay

Range: 10–4000 ms.
Default: 100 ms.
Controls how gradually the gate closes after the hold period.

Gate Frequencies Above

Range: 0–10 kHz.
Default: 0 Hz.
Lets the gate operate only above a chosen frequency when the problem is concentrated higher in the spectrum.

Stereo Linking: Audacity 4 defaults to linked stereo gating. That is usually the safer choice for a conventional stereo music mix because both channels open and close together instead of pulling the stereo image from side to side.

Why -30 dB, 5 ms and 100 ms are not universal settings

The previous version of this article gave a threshold range of -30 to -40 dB, an Attack of 5 ms and a Release of 100 ms as general starting points. That sounds convenient, but it ignores how different AI renders can be.

An exposed breathy vocal, a distorted guitar wall, a sparse piano intro and an ambient synth track can all have completely different useful thresholds and decay behavior. The setting should follow the signal—not the genre label or an old preset.

A better target is: the gate should become difficult to notice. You should hear less unwanted noise without hearing the processor constantly opening and closing.

Audacity envelope warning: Audacity's current Noise Gate documentation warns that applying the effect when a volume envelope is present can remove that envelope and return the audio to its pre-envelope amplitude before the gate is applied. If your edit uses volume-envelope automation, duplicate or save the project first, process a short test region, and confirm the envelope behavior before committing to the whole track.

Common problems—and what they usually mean

Reverb tails get chopped

Lower the threshold, increase Hold or Decay, reduce the amount of Level Reduction—or skip the gate on that section.

The track pumps between phrases

The attenuation is probably too aggressive or the closing behavior too fast. Use less Level Reduction and/or a smoother decay.

Quiet words disappear

The threshold is too high for the performance. The gate is treating wanted low-level vocal material as noise.

The stereo image shifts

For normal stereo music, use linked stereo gating. Independent left/right gating can make the image move as each channel crosses threshold separately.

Noise is still audible under vocals

That is expected. The gate is open while the vocal is above threshold. Use Noise Reduction, source repair or a different generation if the noise itself needs to be reduced during active audio.

The pauses sound unnaturally dead

Use less Level Reduction. A small residual floor, ambience or reverb can sound more natural than hard digital silence.

Silence is not the same thing as professional audio

Breaths, reverb tails, room-like ambience, distorted texture and quiet instrumental decay can all contribute to the emotional shape of a track. A gate cannot know which low-level sound is meaningful. It only follows level and frequency rules.

Before removing something, ask whether a listener would hear it as a defect at a realistic playback level. If not, processing it may solve a problem that did not need solving.

Use the right first tool

NOISE BETWEEN PHRASESNoise Gate
STEADY NOISE THROUGHOUTNoise Reduction
ONE CLICK OR POPRepair
SEVERAL CLICKSClick Removal
NARROW HUM / WHISTLENotch Filter
CHANGING AI GLITCHLocal edit or regenerate

If your issue is transient clicks rather than background noise, use the updated Clicks & Pops Repair Guide.

Where a noise gate belongs in the finishing workflow

A practical order is:

Choose the best source → repair obvious clicks/glitches → reduce genuine steady noise if needed → gate residual quiet-section noise if needed → tonal/mix work → mastering → loudness and export checks.

The words if needed matter. The cleanest processing chain is not the longest one.

Free next step

Stop treating cleanup effects as a mandatory checklist

If the gate is only one decision in a nearly finished track, use the broader finishing workflow to decide what deserves repair, what should be left alone, and what belongs in mastering.

Finish the track in the right order
When every render becomes another rescue job

Build a creative lane you can recognize—and finish—again

If every song requires a completely different cleanup strategy, the bigger problem may be upstream. A more deliberate sound and decision process helps you recognize which generations are worth keeping, what should be regenerated, and what actually deserves finishing time.

Build a more repeatable sound and workflow

Official Audacity 4 references

Last verified September 6, 2026 against Audacity 4.0.0 and the current Audacity manual. For steady-noise cleanup, continue to the Noise Reduction guide. For final level targeting, use the normalization guide. For the complete Audacity finishing stage, continue to the mastering workflow.

Back to blog

Leave a comment

Please note, comments need to be approved before they are published.

articleall levels
On this page

    Your next move

    Turn the reading into useful work.

    Apply this now

    Complete one action before opening another guide.

    Write down the most important decision this article changes, then apply it to the project while the reasoning is still fresh.

    Continue learning

    Keep the subject connected.

    Use the public library to compare related guidance before changing the project.

    Continue with public guidance →
    Go deeper

    Use structured training for ordered work.

    Move into the member system when the project needs a sequence, templates and application—not another isolated tip.

    Explore structured training →
    Use a resource

    Support the next action.

    Use a workbook, checklist or ASK JACK route only when it reduces friction in the work.

    Open the supporting route →

    The Righteous Beat

    Get the week’s most useful creator guidance, platform changes and free resources.

    Join the free newsletter →