How to set up your microphone in OBS Studio for Twitch in 2026

Why microphone setup in OBS matters more than the mic itself

OBS Studio gives you the same five filters every Twitch partner uses: Noise Suppression, Noise Gate, three-band EQ, Compressor and Limiter. If you are still picking software, our streaming software guide compares OBS, Streamlabs and the rest at a higher level; this article assumes OBS Studio specifically. The reason most new streams sound rough is not the hardware. It is the order, the thresholds, and the fact that Windows hands OBS a microphone path that resamples, ducks for VoIP and switches devices when a Bluetooth headset connects. Fix the chain once and the same mic that sounded thin will hold a steady level across a four-hour stream.

This guide assumes OBS 30 or newer (the three-band EQ filter that ships with OBS arrived in version 29.0). The values below are starting points used by streamers across r/Twitch and the OBS forums; the right final numbers depend on your room and your mic, and the only way to land them is to record a test, listen back in headphones, and adjust by 2-3 dB at a time. If you have not picked the mic itself yet, our how to choose a microphone for streaming guide covers the trade-offs between USB and XLR, dynamic and condenser, and budget vs. broadcast tier.

Pick the right input device, not 'Default'

Before you open OBS, select the specific microphone in Windows Sound (Right click the speaker icon > Sound settings > Input) or System Settings > Sound on macOS. Set its level around 70-75% so OBS has headroom to work with. Confirm the level meter responds to your voice. If it does not, the system is not getting audio and no OBS filter will save it.

Inside OBS, never leave Mic/Auxiliary Audio on 'Default'. The OBS forums repeat this point in almost every audio thread: 'Default follows Windows/macOS's idea of the default mic, which changes when you plug in headphones, connect Bluetooth, or dock a laptop. Pick your specific mic by name.' If you switch from a desktop dock to a laptop battery and Bluetooth earbuds connect, the OS quietly swaps the input and your stream goes silent without warning.

While you are in Windows Sound, open the mic's Properties, then the Advanced tab, and turn off all Audio Enhancements. Windows tries to apply ducking and AGC for VoIP apps it thinks are running, and that processing fights every filter you add inside OBS. The result is the muffled, fish-bowl tone people complain about on the OBS forum and Quora threads. Disable the enhancements and most of that complaint disappears.

One more environment check: a fan, an air conditioner or a mechanical keyboard sitting 30 cm from a condenser mic will defeat any noise suppression you stack on top. Move the mic 6 to 12 inches (15-30 cm) from your mouth, slightly off-axis to avoid plosives, and aim it away from the loudest desk noise. The cleaner the input signal, the less aggressive your filters need to be. If a desk-mounted condenser is impractical for an IRL or face-cam setup, our best lavalier microphone for streaming roundup covers clip-on options that survive movement and shoulder pivots.

Add the mic: Settings vs Audio Input Capture

OBS gives you two ways to bring a mic into the program. Through Settings > Audio you set a global Mic/Auxiliary Audio device that follows every scene. Through Sources > Add > Audio Input Capture you add the mic as a per-scene source with its own filters and properties. Both work; the choice changes what happens when you switch scenes.

Two real-world rules:

• If you only ever talk on one mic, use Settings > Audio. The mic stays live across scenes, gets one set of filters and never disappears mid-stream.
• If you swap mics by scene, run a 'Just Chatting' setup separate from a gameplay scene, or want different filter chains, use Audio Input Capture per scene.
• Do not do both at once. Adding the same mic globally and as a scene source duplicates the signal; you will hear a flanging delay or a hard echo on stream.

When the mic is added per scene and you switch scenes, the source goes silent if the new scene does not contain it. That is the most common 'OBS broke my audio' complaint on the support forums. Either copy the source into every scene (right click > Copy, then Paste (Reference) into each scene), or fall back to the global Settings > Audio approach and stop fighting the scene tree.

Sample rate, bitrate and the mono question

Set Settings > Audio > Sample Rate to 48 kHz. Then open Windows Sound > Recording > your mic > Properties > Advanced > Default Format and set it to '16 bit, 48000 Hz (DVD Quality)'. Twitch and YouTube both expect 48 kHz; mismatched rates between the OS and OBS cause slow audio drift that pulls voice out of sync with video over a long broadcast. The film and broadcast industry standardized on 48 kHz precisely because it divides evenly into common video frame rates, which is why every modern streaming platform inherited it.

For audio bitrate, 160 kbps is the safe choice for Twitch in 2026. The community consensus is direct: 160 kbps audio is the sweet spot for streaming and offers quality indistinguishable from higher bitrates for voice content. Push to 192-256 kbps if music or game soundtrack is part of the show; our equipment for music streaming guide goes deeper on the audio interface and routing decisions that matter when songs are the main content. Do not drop below 128 kbps; compression artefacts become audible on hi-hats and consonants.

Most streaming microphones, including the Blue Yeti, Shure MV7 and every XLR condenser, are mono devices. If your voice only comes out of the left channel, the mic is sending a single channel into a stereo bus. Open Edit > Advanced Audio Properties on the audio mixer and tick 'Downmix to Mono' for the mic. The single channel is duplicated to both sides of the stream output, your voice sits centred and viewers stop tilting their heads.

Set base gain before any filter

Get the level right with no filters loaded. The mixer fader sits at 0 dB by default; leave it there and adjust the mic's hardware gain, the audio interface knob or Windows level until normal speech peaks land around -18 dB to -10 dB on the OBS meter (the yellow zone). Loud bursts can touch -6 dB; nothing should pin the red.

If the mic is too quiet at maximum hardware gain, add a Gain filter (Filters > '+' > Gain) and lift it 5-10 dB. Forum threads document users pushing it to +20 or +30 dB on weak USB mics, but every dB of digital gain also amplifies the noise floor; raising the input by 30 dB on a noisy mic is why the noise suppression filter then has to work much harder than it should.

Two anti-patterns to avoid. Do not crank the mic to be the loudest source on the stream just to stand out; modern Twitch encoder behaviour and viewer player normalization will not help you, and you will fight clipping for the rest of the stream. Do not increase Windows mic level past 100% (the +6 dB to +30 dB 'Boost' option) before trying the OBS Gain filter; the Windows boost is applied before any OBS filter and is harder to undo cleanly.

Filter chain order that actually works in 2026

Open the mixer (View > Docks > Audio Mixer if it is hidden), click the gear icon next to your mic, choose Filters, then click '+' to add each filter in order. Order matters because each filter feeds the next. If you put the compressor before noise suppression, the compressor lifts the noise floor during quiet passages and the suppression has to work twice as hard.

The chain order most current OBS guides converge on for voice in 2026:

• 1. Noise Suppression (RNNoise or Speex)
• 2. Noise Gate
• 3. Three-Band EQ (80 Hz cut, 3 kHz presence)
• 4. Compressor (3:1 or 4:1)
• 5. Limiter (-3 dB ceiling)

The reasoning runs top to bottom. Strip the steady background hum first so the gate sees a cleaner signal. Gate the silences. Shape the tone so the compressor and limiter are working on a voice, not on a low-frequency rumble. Compress to even out shouts and whispers. Limit to catch the surprise peak when chat says something funny and you bark a laugh. A common quote on the OBS forums sums it up: 'That order lets you remove gentle background noise first, then close the mic when you're not talking, then even out your voice, and finally keep peaks under control.' Drop a Gain filter at any point in the chain if you need to make up level after compression.

Noise Suppression: RNNoise vs Speex (and when to use NVIDIA)

The OBS knowledge base lists three methods inside the Noise Suppression filter: RNNoise, Speex and NVIDIA Noise Removal. RNNoise is the default and the right choice if you have any modern CPU. It uses a small machine-learning model trained to strip background noise while preserving speech, and it has no parameters to tune; you just turn it on. Speex is the older, lighter algorithm with a configurable suppression level (-30 dB is the OBS default, range -60 to 0). The trade-off is direct: RNNoise is higher quality at the cost of more CPU; Speex is lighter on a slow machine but less aggressive on transient noise like keyboard clatter.

If you have an RTX GPU and download the NVIDIA Broadcast SDK, you also get NVIDIA Noise Removal as a third option in the dropdown. It is the strongest of the three for loud rooms, which makes it the right pick for an apartment with traffic outside or a streamer who shares a room with a mechanical keyboard typist. The cost is GPU load that you might prefer to spend on the encoder; on a single-PC stream with an x264 encoder running 1080p60 at 6000 kbps, RNNoise on the CPU is usually the cleaner trade.

A practical limit the OBS docs spell out: 'While this is generally not effective at large amounts of background noise (i.e. in a loud room) it can be quite effective at reducing things like PC fan noise or other environmental noises.' If your room is genuinely loud, fix the room (close the window, move the mic away from the fan, hang a blanket on the bare wall behind you) before you ask any noise suppression to compensate. The cleaner the input, the less the filter has to chew on the consonants of your voice.

Noise Gate thresholds for streaming

Noise Suppression handles the constant hum. Noise Gate handles the silences between sentences: when you stop talking, it closes the mic so chat does not hear the fan or the keyboard. The two thresholds work together. The Open Threshold is the level your voice has to cross to open the gate; the Close Threshold is where the gate closes again. The Close value should sit a few dB below the Open value so the gate does not chatter on and off when your voice trails off at the end of a sentence.

Reasonable starting values for a desk mic:

• Close Threshold: -40 dB (range -45 to -32 dB depending on room noise floor)
• Open Threshold: -30 dB (range -35 to -26 dB; about 5-6 dB above Close)
• Attack: 25 ms (slower attack on dynamic mics, faster on condensers)
• Hold: 150-200 ms (long enough so the gate does not chop the tail of a word)
• Release: 150 ms

A symptom check: if your first syllable is clipped on every sentence, raise Hold or lower the Open threshold. If the gate chatters open and shut while you breathe, raise the Close threshold or extend Hold. If words drop mid-sentence in a heated game moment, the gate is too tight and you should loosen both thresholds by 3-5 dB. The goal is intelligibility, not silence; over-aggressive gating is the single most common reason streamers say 'my mic cuts off'.

Three-band EQ: 80 Hz cut, 3 kHz presence

OBS 29.0 added a built-in three-band EQ. It is enough for voice if you do not want to install VST plugins. The filter has three controls: Low (around 100 Hz), Mid (around 1 kHz) and High (around 10 kHz). The general rule from the OBS forums and FIFINE's voice tuning notes: do not move any band by more than +/- 5 dB. Microphones are calibrated to sound natural at zero, and large EQ swings make the noise suppression and compressor less predictable.

Sensible voice starting curve:

• Low (around 100 Hz): -3 dB to cut desk rumble and AC hum, or down to -6 dB if you have a deep voice that books low
• Mid (around 1 kHz): 0 dB; do not push this band, it sits where the voice already lives
• High (around 10 kHz): +2 dB for a small lift on consonants; back to 0 dB if your mic is already bright

If you want true presence boost in the 2-3 kHz band where consonants sit, the three-band EQ is too coarse and you will need a parametric VST (see the ReaPlugs section below). For most streamers the simple low cut and gentle high lift are enough; the rest of the perceived 'broadcast sound' comes from the compressor, not the EQ. The OBS forum thread on voice EQ puts it bluntly: 'Between two and three kHz you can usually add clarity to your voice', but the cost of overdoing it is harshness on every sibilant, and harshness is harder to fix than dullness.

Compressor for a steady voice

A compressor measures incoming level and attenuates anything above the Threshold by the Ratio. The result is a tighter dynamic range: whispers come up, shouts come down, the average voice sits at a steady level for chat to follow. For streaming voice the bracket of values most guides settle on is Ratio 3:1 to 4:1, Threshold around -18 dB, Attack 6 ms, Release 60 ms, Output Gain +3 dB to +9 dB to make up the level that compression took away.

Reading the parameters in plain language:

• Ratio 4:1 means once your voice crosses the Threshold, every 4 dB of input becomes 1 dB of output. A 2:1 ratio sounds natural; 10:1 sounds squashed.
• Threshold -18 dB: the compressor starts working when the signal is louder than -18 dB on the meter. Lower the threshold (toward -24 dB) for more compression, raise it (toward -10 dB) for less.
• Attack 6 ms: how fast the compressor reacts. Faster attack catches the very start of a shout; slower attack lets the transient through and then compresses the body of the word.
• Release 60 ms: how fast the compressor lets go. Too short and the compressor pumps audibly; too long and it never resets between sentences.
• Output Gain +3 to +9 dB: pure make-up. Set it so the post-compressor level matches the pre-compressor level on the mixer.

Beginners can use the OBS defaults (Ratio 10:1 is the original default; bring it down to 4:1) and a Threshold of -18 dB. Record 30 seconds of normal talk, then a 30-second simulated rage shout, then a soft aside. Listen back. If the rage moment ducks below the soft aside, the ratio is too high and the threshold is too low. If the soft aside is whisper-quiet next to the rage, the compressor is barely doing anything and you can lower the threshold by 3-5 dB. Trust your ears more than the numbers; the appropriate compressor settings depend on the microphone used and the streaming environment, and the same setting might not be effective for other streamers or with different equipment.

Limiter at the end of the chain

The Limiter is the safety net. It is the last filter in the chain and it has one job: prevent any peak above its Threshold from ever leaving OBS. Set Threshold to -3 dB, Release to 60 ms, and forget it. The limiter does not amplify the signal; it simply holds the ceiling so a sudden laugh, a clap or a Twitch alert never clips the encoder and never blows out a viewer's headphones.

Why -3 dB and not -1 dB? Two reasons. First, every encoder downstream (Twitch ingest, Kick ingest, the YouTube transcoder) does its own loudness processing, and a -3 dB ceiling leaves them headroom to work with. Second, AAC at 160 kbps occasionally produces inter-sample peaks slightly above the digital sample peaks; -3 dB keeps those safe. Some advanced guides go to -1 dB for a louder stream, which works if you trust your room and your monitoring; -3 dB is the conservative number that survives every emotional moment a stream throws at you.

If you stream emotional games and your laughs hit the limiter often, do not raise the threshold. Lower the compressor threshold by 3-5 dB so the compressor catches more of the dynamic range and the limiter only has to do clean-up work. A limiter that is constantly slamming is a sign the compressor before it is set too gently.

Audio Monitoring: Off, Output, Monitor Only

OBS has three monitoring modes per source, set in Edit > Advanced Audio Properties under the Audio Monitoring column: Monitor Off (default), Monitor and Output, and Monitor Only. The setting controls whether you hear the source through your selected Audio Monitoring Device (Settings > Audio > Advanced > Monitoring Device). Most streamers should leave the mic on Monitor Off and listen to themselves through their audio interface or USB mic's direct-monitor knob, not through OBS.

Three real cases:

• Mic on Monitor Off: the right default. You hear yourself through the mic's hardware monitor; OBS only sends to the stream.
• Mic on Monitor and Output: only useful if you cannot direct-monitor your mic and need to hear yourself through OBS to time your own talk. Adds 30-60 ms of delay; sounds robotic in headphones.
• Browser source on Monitor and Output: useful for chat alert sounds and donation chimes you want to hear AND send to the stream.

If you set Mic to Monitor and Output and you also have Windows mic 'Listen to this device' enabled, you will hear your own voice twice with different latencies; that is the canonical OBS echo problem. Either turn off Windows mic listen, or turn off OBS monitoring; pick one path. For a deeper dive on the same symptom, see our walkthrough on how to fix echo in OBS while streaming.

Push-to-talk vs voice-activated

Voice-activated streaming (the default; the mic is open whenever the gate opens) is right for solo content where you talk most of the time. Push-to-talk (PTT) is a hotkey that opens the mic only while held, and it is the right choice when you stream with a partner in the same room, when a roommate is on a call nearby, or when you want absolute control over what chat hears. Configure both in Settings > Hotkeys; every audio source has a 'Push-to-talk' field where you bind a key, plus an optional 'Push-to-mute' inverse (mic always open, hotkey closes it).

Two practical notes from the OBS forums. PTT inside OBS does not affect Discord or other apps; if you want chat in a Discord call to also stop hearing you, you need PTT in Discord too. And the OBS PTT key fires only while OBS has focus or the global hotkey is enabled in Settings > General; if the binding feels broken, that toggle is the first place to check.

VST plugins (ReaPlugs) when stock filters aren't enough

OBS supports VST 2.x plugins through Filters > VST 2.x Plugin. The plugin most often recommended in 2026 is ReaPlugs from the Reaper team. Three modules cover what the stock filters cannot: ReaFir for adaptive noise subtraction (you record a noise profile, then it removes that exact frequency signature), ReaEQ for full parametric EQ with as many bands as you need, and ReaComp for a more transparent compressor than the OBS built-in. ReaPlugs is free for personal and commercial use.

Install gotcha: the ReaPlugs installer can drop the VSTplugin folder into C:\Program Files instead of C:\Program Files (x86), and OBS will not see it. If a VST does not show up in the dropdown, copy the .dll files into C:\Program Files\Common Files\VST2 and restart OBS. The OBS VST 2.x plugin documentation lists the supported paths.

ReaFir is the one most worth the install. Set Mode to Subtract, click 'Automatically build noise profile' for 2-3 seconds while you stay quiet, then turn the build profile checkbox off. The plugin learns the exact frequency signature of your fan, your AC and your room hum, and it subtracts that signature continuously. It is more surgical than RNNoise and it does not chew on the consonants of your voice the way aggressive Speex sometimes does. The catch: every time the room changes (you turn off the AC), you should rebuild the profile or the subtraction will sound off.

Stream Deck mic mute and scene audio

If you run an Elgato Stream Deck or a Stream Deck Plus, the OBS Studio plugin lets you bind a key directly to a mic mute action, a volume nudge, or a multi-action that switches scene + starts background music + mutes mic at the same time. On Stream Deck Plus and Galleon 100 SD, you can assign the audio control to a dial and twist the level on the fly mid-stream. This is the cleanest way to drop the mic for a sneeze without breaking immersion.

A common multi-action for a 'Be Right Back' scene: switch to BRB scene, mute Mic/Aux, lower desktop audio to 30%, start a 5-minute timer. One key press, four actions. If you do not have a Stream Deck, OBS hotkeys (Settings > Hotkeys > Mute / Unmute / Toggle Mute on the mic source) cover the same ground for free.

Test, troubleshoot and move on

Every change above is invisible until you record. Set OBS to record locally (Settings > Output > Recording > set the path to a fast drive), pick a high-quality format (mkv with 160-256 kbps audio), record 60 seconds: normal talk, a soft aside, a loud laugh, a long pause. Open the file in headphones, not laptop speakers. The sound you hear is exactly what Twitch viewers will hear, minus the encoder loss.

Common symptoms and the first place to look:

• No sound on the meter: wrong device selected (Mic/Auxiliary on 'Default' is the most common cause); also check Windows app permissions for the mic.
• Crackle or distortion: input level too high; lower hardware gain or the OBS Gain filter and re-test.
• First syllable is cut off: noise gate Open threshold is too high or Hold is too short.
• Voice sounds underwater or hollow: Windows audio enhancements are still on; disable them in mic Properties > Advanced; also check Bluetooth, which forces the handsfree profile and tanks quality.
• Echo on stream: monitoring is set to Monitor and Output AND Windows 'Listen to this device' is enabled; pick one path or disable both.
• Audio drift over a long stream: sample rate mismatch between Windows and OBS. Set both to 48 kHz.

Once the recording sounds clean, also frame your shot; our how to set up a webcam in OBS guide pairs naturally with this one and you only need to do both once. Then do a 5-minute private Twitch test stream (Settings > Stream > server: closest ingest; set the channel to private or use a fresh test channel). Open the stream on your phone with headphones; the phone gives you a second perspective the local listen-back cannot. If it sounds clean on the phone, ship it. Clean audio raises retention, retention raises Twitch's recommendations, and from there you can layer real-viewer growth tools like StreamRise on top of a stream that is already worth watching.

Frequently asked questions

Registration