Skip to the loadout
LOADOUTAUDIO Free first · frames counted
Menu

OBS noise gate settings, and the four-filter chain around them

Sourceyour mic and its room floor
Suppressionfirst in the chain
Gatetwo thresholds, after suppression
The front of the chain in three wells, in signal order: the gate is the cheapest piece in the tray. The compressor and limiter follow it.

Set the OBS noise gate with two sliders:

BUILD 2026.10.09by the Loadout Audio squad

OBS ships -32 dB close and -26 dB open as defaults, and they're a fair starting point for many headsets.

Then build the rest of the mic chain in this order: Noise Suppression, Noise Gate, Compressor, Limiter. OBS's own knowledge base fixes one end of that firmly: the limiter "should be the last filter in your chain". The rest is reasoning, and this page shows it, so you can change the order on purpose rather than by accident.

This is for anyone streaming or recording a mic in OBS 32 or later who hears keyboard bleed between sentences, or watches the meter jump into the red when they shout. If your problem is constant fan hum under your voice, start at OBS noise suppression. A gate can't touch noise that plays while you talk.

Add it, chip by chip

Right-click mic source→Filters→+→Noise Gate

Repeat the same path for Noise Suppression, Compressor and Limiter. Filters run top to bottom in the list, and you drag them to reorder. They belong to the audio source, not to the scene. If you add your mic to a second scene as a fresh source rather than a reference, it starts with an empty chain.

The chain, top to bottom (and why)

The OBS mic chain, top to bottom: mic source, Noise Suppression (RNNoise default, or Speex at -30 dB), Noise Gate (close -32 dB, open -26 dB, attack 25 ms, hold 200 ms, release 150 ms), Compressor (ratio 10:1, threshold -18 dB, attack 6 ms, release 60 ms, output gain 0 dB), Limiter (threshold -6 dB, release 60 ms, always last), then stream and recording.
the four filters with OBS's default values. Tune each against your own meter.
#FilterIts jobOBS defaultIf it sits in the wrong slot
1Noise SuppressionLowers steady noise: fans, hum, room toneMethod RNNoise; Speex level -30 dBAfter the compressor, it's cleaning noise the compressor already lifted
2Noise GateMutes the mic between sentencesClose -32 dB, Open -26 dB, Attack 25 ms, Hold 200 ms, Release 150 msAfter the compressor, the thresholds move every time you touch the compressor
3CompressorMakes loud moments quieter10:1, -18 dB, Attack 6 ms, Release 60 ms, Output Gain 0 dBBefore the gate, its output gain raises the floor the gate is judging
4LimiterA hard ceiling so peaks can't clipThreshold -6 dB, Release 60 msAnywhere but last, a later filter can push past the ceiling

Why suppression first. RNNoise lowers the room before the gate ever sees it. That widens the gap between your floor and your voice, which is the whole thing a gate needs.

Why the gate before the compressor. OBS's compressor page says it "typically would be placed at or near the beginning of your filter chain". We put it third, behind the two clean-up filters, and here's why. A compressor with output gain lifts quiet sound, room noise included. Gate first, and your thresholds are set on a signal no other knob changes.

Why the limiter last. OBS is explicit. A limiter is "a special type of compressor with a very fast attack and a very high ratio" that stops the signal peaking above 0 dB, and it "should be the last filter in your chain". Anything placed after it can undo the ceiling.

The two-slider method

OBS's own advice for the gate fits in one line: a close threshold above the noise, and an open threshold slightly below your voice. The method is how you find those two numbers on your rig.

  1. Find your floor. Sit silent with your hands on the keyboard and the fan running, and watch the mic meter in the OBS audio mixer. With suppression already above the gate, read the meter after it's applied. Say the room rests at -45 dB.
  2. Set Close just above the floor. With a -45 dB floor, try Close around -40 dB. The gate now shuts on room noise alone.
  3. Set Open just below your quiet voice. Talk at your real muttering-at-teammates volume and note the meter. Put Open a few dB under it. The defaults, -26 dB open and -32 dB close, fit a lot of headsets; your meter beats the defaults.
  4. Test like you play. Type hard while silent: the gate should stay shut. Speak mid-clatter: it should open at once. Adjust in 2 dB steps, one slider at a time.
The two sliders on one scale, placed by the numbers in the method above
-50 dBquieter → louder-20 dB

Four marks, four numbers, all four of them from the method and the FAQ on this page; the scale runs -50 to -20 dB so the gap between floor and voice is the thing you see. Your own meter replaces every mark on it.

The gap between the two thresholds is deliberate. Open has to sit above Close, so a voice that dips briefly between words doesn't slam the gate shut and chatter.

How the two gate thresholds behave: a voice trace on a -50 to -20 dB scale rises past the -26 dB open line and the gate opens, dips between words but stays above the -32 dB close line so the gate holds open, then falls below -32 dB, waits out the 200 ms hold and fades over the 150 ms release.
open and close, plus hold and release, on OBS's default values. The trace is illustrative, not a measurement.

The three timing controls, in plain terms:

Compressor and limiter starting points

OBS describes the compressor in one sentence: it "makes loud sounds quieter". It's the fix for the clutch-moment shout that spikes the meter while your normal speech sits fine.

Limiter: -6 dB threshold and 60 ms release by default, last in the chain. It's the safety net, not a tone control. If it's working constantly, the compressor above it isn't doing its job.

A bonus streamers miss: ducking. Put a second compressor on your Desktop Audio source and set its Sidechain/Ducking Source to your mic. Your game audio then dips whenever you talk. OBS's suggested starting values are:

Where suppression sits, and the CPU budget

The Noise Suppression filter has three methods. OBS's notes:

OBS is also candid about the filter's limits. It's "generally not effective at large amounts of background noise", but good at things like PC fan noise.

Every one of those methods spends something: CPU for RNNoise and Speex, GPU for NVIDIA's. Measure what your rig pays, rather than trusting a number from someone else's. Run the same five minutes of your game with the filter off and then on, and compare the 1% lows. The free stack page has the full 60-second protocol. If your GPU is already the bottleneck, a GPU filter is the wrong pick, and if your CPU is pinned by an x264 encode, RNNoise is.

There's one more alternative to a gate. OBS's Expander "can be used in place of a gate". It turns quiet sound down by a ratio instead of muting it, which gives a smoother open and close. OBS places it near the end of the chain, after compression and before the limiter. Use one or the other, not both.

If you'd rather run one suppressor for every app instead of a separate chain in each, a virtual mic upstream does that. Krisp's desktop app installs Krisp Microphone; select it as the OBS mic source and keep the gate, compressor and limiter below it. Don't stack OBS suppression on top of it. Krisp has no ongoing no-cost tier. Once the 7-day trial ends, keeping it means Core at $8 per month on annual billing, or $16 if you pay monthly (pricing checked 9 October 2026).

Gate before or after suppression?

This is the one ordering argument with two defensible answers.

Either works, as long as you set the thresholds after the filters above the gate are in place, and re-check them whenever you change one. A threshold copied from a chain in another order is a guess.

Testing with a recording

Your own ears lie while you're talking. Record instead:

  1. In OBS, record two minutes with only your mic and the full chain on.
  2. Cover four moments: silent typing; a soft callout mid-typing; a shout; a laugh.
  3. Play it back on headphones. Listen for keyboard between sentences (the gate), clipped first words (Open or attack), pumping after a shout (the compressor's release or ratio), and any harsh peaks (the limiter isn't last, or the compressor is too light).
  4. Change one control, re-record, and compare. Two changes at once tell you nothing.

When a gate is the wrong tool

Lobby questions

What are good OBS noise gate settings?
Start at OBS's defaults: Close -32 dB, Open -26 dB, Attack 25 ms, Hold 200 ms, Release 150 ms. Then set Close just above your room's noise on the meter, and Open a few dB below your quietest speech. Test while typing and adjust in 2 dB steps. Numbers copied from another streamer's mic rarely transfer.
What order should OBS audio filters go in?
Noise Suppression, Noise Gate, Compressor, Limiter. Suppression lowers the floor, the gate mutes the gaps, the compressor tames loud moments, and the limiter caps the peaks. OBS's own docs fix only the end: the limiter goes last. If you use an Expander instead of a gate, OBS places it after compression and before the limiter.
Should the noise gate go before or after noise suppression?
Either can work. After suppression, the gate sees a lower floor and is easier to set; before it, the gate judges the raw mic. What matters is setting the thresholds once the filters above the gate are in place, and re-checking them whenever you change the order.
What are good OBS compressor settings for a mic?
OBS's defaults are a 10:1 ratio, -18 dB threshold, 6 ms attack, 60 ms release and 0 dB output gain. 10:1 is strong. OBS calls 2:1 weak and 6:1 much stronger, so step down if you sound squashed. Lower the threshold until shouts get caught but normal speech doesn't, then add output gain in small steps.
Why does my OBS noise gate cut off the start of my words?
Your Open threshold is above your quietest syllables, so soft first sounds never open the gate. Lower Open a few dB and test again. If it still clips, shorten the attack. A gate placed after a compressor can also shift where your voice lands, so check the filter order too.

Next objective