How to Fix OBS Noise Suppression Not Working: RNNoise, Speex, Robotic Voice, and Better Filter Chains

Quick Answer

If OBS noise suppression is “not working,” the problem is usually one of six things: the filter was added to the wrong mic source, the suppression is too light to notice, the suppression is too strong and causes robotic voice, the filter order is fighting itself, the user expects keyboard or fan noise to disappear while speaking, or the NVIDIA option is missing because its redistributable is not installed.

OBS’s own documentation says the Noise Suppression filter is meant for mild background noise or white noise and is generally not effective for loud environments. It also warns that stronger suppression can distort your voice. In practice, that means live suppression is a compromise: it can reduce steady noise, but it may not fully erase clicks, fans, or room sound under speech.

The safest starting point for most voices in OBS is:

• Light RNNoise first
• Compressor only if you actually need level control
• Expander near the end to reduce quiet-gap room noise
• Limiter last

If your recording already exists, or if stronger live filtering makes the voice watery, metallic, or underwater, it is often smarter to clean exported OBS audio with SimpleClean instead of stacking more live filters.

Symptom-to-fix table

What OBS noise suppression can and cannot fix

Before changing settings, it helps to reset expectations. According to the official OBS knowledge base, the Noise Suppression filter is designed to remove background noise such as white noise. OBS also notes it is generally not effective at removing louder background noises and that heavy suppression may distort the source audio.

That explains why people think the feature is broken when it is actually just being asked to do too much.

• Good fit: mild fan noise, steady hiss, low-level room noise
• Mixed results: keyboard clicks, mouse clicks, louder PC fans while you are talking
• Poor fit: loud rooms, strong echo, severe background noise, aggressive suppression without artifacts

If your issue is more about keyboard noise than steady hiss, this guide pairs well with OBS mic picking up keyboard.

Check the basics first

A surprising number of OBS audio problems come from editing the wrong source. OBS filters are added per source, not magically across every microphone in every scene. In the OBS interface, open the source’s Filters panel and confirm you are editing the exact microphone that is active in your mixer.

1. Find your active mic source in OBS.
2. Open Filters for that source.
3. Add or edit Noise Suppression.
4. Record a short sample.
5. Listen back before adding another filter.

That last step matters. Make one change, then test. If you stack several filters at once, it becomes hard to tell which one caused the problem.

RNNoise vs Speex vs NVIDIA Noise Removal: which should you use?

OBS supports multiple suppression methods, but they solve different problems.

RNNoise: best default for most people

OBS describes RNNoise as the higher-quality option, but with higher CPU usage. If you want the simplest starting point, this is usually it. Try it first when you want mild cleanup without lots of tuning.

• Best for: most streamers, creators, and screen-recording users
• Main downside: can sound robotic if pushed into a bad recording situation

Speex: best when RNNoise artifacts are worse

Speex is more configurable. OBS explicitly says that 0 dB is effectively off, and moving the slider left increases suppression strength. The catch: stronger settings also raise the risk of distortion.

• Best for: users who want manual control
• Main downside: easier to overdo

NVIDIA Noise Removal: best only if your OBS setup supports it

OBS notes that NVIDIA Noise Removal appears only after the NVIDIA Broadcast SDK redistributable is installed. If you do not see the option, that does not automatically mean OBS is bugged; it may simply mean the needed NVIDIA component is not present.

• Best for: users already in a supported NVIDIA audio-effects workflow
• Main downside: availability depends on the NVIDIA setup being installed correctly

If your NVIDIA path is failing more broadly, see how to fix NVIDIA Broadcast not working and remove background noise in NVIDIA Broadcast.

Why OBS noise suppression sounds robotic

“Robotic,” “metallic,” and “underwater” are classic signs that the suppression is too aggressive for the recording conditions. This is not unique to OBS; it is the normal tradeoff when live denoise tries to separate voice from noise in real time.

Common causes:

• RNNoise is working on a voice-plus-noise mix that is too messy
• Speex is set too far left, increasing suppression strength too much
• You are combining suppression with other filters that exaggerate artifacts
• The room or mic position is too noisy for light live cleanup to sound natural

Best fixes:

• Back off the suppression amount
• Try the other method: RNNoise if Speex sounds bad, or Speex if RNNoise sounds worse
• Remove unnecessary filters and rebuild a simple chain
• Use post-cleanup on the exported file instead of forcing live denoise harder

If you already recorded the file and just need a safer cleanup pass, remove background noise from recorded OBS audio with SimpleClean can be the more practical route.

Why keyboard clicks and fans may still be heard while talking

This is the single biggest misunderstanding behind the phrase “OBS noise suppression not working.” Users often expect one live filter to remove everything all the time, including while speech is happening. But live suppression is a compromise. It may reduce non-speech sounds, yet it often cannot fully erase them beneath your voice without damaging the voice too.

That is why you may still hear:

• Keyboard clicks during speech
• Fan tone under spoken words
• Room ambience in louder environments

An expander can help with the spaces between words. OBS explains that an expander reduces quieter sounds and is often smoother than a hard noise gate. It is typically placed near the end of the chain, before a limiter. That makes it useful for lowering low-level room noise during pauses without chopping off speech as abruptly as a gate might.

Recommended safer OBS filter chain for speech

If your current setup is a pile of random filters, simplify it. Based on the official OBS filter docs, a safer speech-focused chain is:

1. Light Noise Suppression
2. Compressor only if needed
3. Expander near the end
4. Limiter last

Why this order works:

• The suppression handles mild steady noise first
• The compressor, if used, manages level consistency
• The expander reduces low-level noise in quiet moments
• The limiter stays last because OBS says it should be the final protection against clipping

Do not assume more filters mean better audio. Each added filter increases the odds of artifacts, pumping, choppiness, or performance issues.

How to fix OBS noise suppression not working, step by step

1. Open the correct mic source. In OBS, find the microphone you actually use and open its Filters panel.
2. Add Noise Suppression. Start with RNNoise if you are unsure.
3. Record a 10 to 20 second test. Speak normally and include a few seconds of silence.
4. Listen for the real problem. Is there no change, robotic voice, cutouts, or just some remaining background noise?
5. If there is no change, verify the source. Make sure you did not add the filter to the wrong source, scene item, or inactive mic.
6. If voice sounds robotic, reduce aggression. If using Speex, remember 0 dB is off and moving left increases suppression strength. Move toward lighter settings. If using RNNoise, try Speex instead.
7. Add an expander near the end. Use it to reduce quiet-gap room noise more smoothly than a hard gate.
8. Keep limiter last. This follows OBS guidance and avoids clipping after the rest of the chain.
9. Retest after every change. Do not change three things at once.
10. Stop when quality starts getting worse. If stronger live cleanup makes speech unnatural, export and clean the file separately.

When NVIDIA Noise Removal is missing in OBS

If you do not see the NVIDIA method in the Noise Suppression filter, check the official requirement first: OBS states that the NVIDIA Broadcast SDK redistributable must be installed before the option appears.

That means the fix is usually:

• Install the NVIDIA Broadcast SDK redistributable referenced by OBS
• Restart OBS
• Reopen the filter dropdown and check again

For broader NVIDIA audio-effect context, the official NVIDIA Broadcast and Audio Effects SDK pages are the right references. If your setup still fails, the issue may be outside OBS rather than a missing filter setting.

Performance note: filters cost resources

OBS documents RNNoise as the higher-CPU option, and in general every live filter adds processing cost. If OBS performance drops after you build a heavy chain, simplify it and retest.

Try this order of troubleshooting:

• Disable extra filters temporarily
• Keep only Noise Suppression and Limiter
• Record another short test
• Add the Expander back only if needed
• Use the simplest chain that solves the problem well enough

When not to fight OBS

Sometimes the best fix is to stop chasing a perfect live chain.

Use exported-file cleanup instead when:

• The recording already exists
• Stronger suppression makes the voice watery or metallic
• You need more cleanup than mild live suppression can give
• You want to preserve speech quality instead of forcing aggressive real-time denoise

In that situation, SimpleClean is a natural next step for file-based cleanup after OBS export. If you are also finishing the video for publishing, Best AI Captions can add captions and subtitles, Translate Dub can translate and dub the finished video for multilingual audiences, and Mallary.ai fits when you are ready to distribute clips and publish cleaned content across multiple social platforms.

Should you use a VST or plugin instead?

If the built-in OBS options are not enough, OBS’s filters guide confirms that VST 2.x plugins can be used in OBS. One commonly referenced path is an RNNoise-based plugin such as the werman project. The point is not that plugins are always better, but that if you have outgrown the built-in filter, a dedicated plugin workflow may offer different tradeoffs.

Still, built-in fixes should come first. They are faster to troubleshoot, easier to test, and often good enough for mild noise.

Best-for recommendations

• Best default: RNNoise with light settings and a short test recording
• Best when RNNoise sounds weird: Speex, used conservatively
• Best for quiet-gap cleanup: Expander near the end of the chain
• Best for clipping prevention: Limiter last
• Best for already recorded OBS files: file-level cleanup after export instead of more live suppression

Final takeaway

OBS noise suppression usually is not “broken.” More often, it is either set on the wrong source, pushed too hard, or expected to do more than live denoise can realistically do. Start with the right source, use light settings, keep your chain simple, and test after every change. If the voice starts sounding robotic, that is your sign to back off and switch to post-cleaning rather than doubling down.