OBS Mic Test: Check Your Microphone Audio Before You Go Live
Overview
OBS Mic Test. The OBS Mic Test checks both your speakers and your microphone before you go live, so a dead channel or a silent mic never catches you mid-stream. Click Play Left or Play Right to confirm each speaker, then hit Enable Microphone and speak normally to watch your waveform and level meter move from Quiet through Good to Loud. Below the meter you'll find the exact OBS settings — Audio Mixer levels, Noise Gate filters, and the Windows exclusive-mode conflict — that actually cause a mic to fail inside OBS Studio. Run the gaming headset test online to see exactly what's working and what isn't.
Nothing ruins a stream faster than a muted or clipping microphone, and this online OBS mic test catches both before you go live. It reads your mic in the browser with no download and shows the exact dBFS levels OBS Studio will receive, so a one-minute OBS audio test here tells you whether to raise gain, add filters or fix a setting before your next recording.
How to Run an OBS Mic Test in Your Browser
The tool uses the browser's Web Audio API, so your voice is analysed locally and never uploaded. Nothing is stored once you close the tab. It works the same on Windows, macOS and Linux, and with any device the operating system already recognises. Use the tv and soundbar test tool whenever you want a fast, repeatable way to confirm this.
- Click Start and allow microphone permission when prompted.
- Pick the same device you use in OBS from the input list.
- Talk at your normal streaming volume for about 20 seconds while watching the live waveform and meters.
- Note the average speech level, the loudest peaks and the level of the room when you are silent.
- Read the frequency response view to see whether low rumble or harsh highs dominate your voice.
Because the OBS mic test tool reads the raw input before any OBS filter touches it, the numbers it gives you are your starting point for every setting below.
What the Microphone Tester Reads From Your Input Level
Every reading is in dBFS (decibels relative to full scale), where 0 dBFS is the digital ceiling and everything else is negative. The tester reports average speech, peak level, the noise floor of your room, any clipping, the device sample rate (usually 48 kHz) and a rough latency figure. Your input level is the number that drives every later decision, so get it right before touching filters.
Recommended OBS Audio Settings and Audio Levels
Match your operating system to OBS Studio first, then set levels. These are the settings most streamers use for broadcast-quality voice, whether the content is gaming or a podcast: Try the google meet audio test for a quick, no-install way to check this yourself.
| Setting or signal | Where to set it | Recommended value |
|---|---|---|
| Sample rate | Settings > Audio > General | 48000 Hz (match Windows or macOS) |
| Mic/Aux device | Settings > Audio > Global Audio Devices | Your mic by name, not "Default" |
| Monitoring device | Settings > Audio > Advanced | Your headphones |
| Speech level | Audio Mixer meter | -18 to -12 dBFS |
| Loudest peaks | Audio Mixer meter | No higher than -6 dBFS |
| Game audio or music | Desktop Audio slider | At least 10 dB below your voice |
Leaving the device on "Default" is the most common cause of a silent mic, because the system default can change when you plug in a new USB headset.
Reading the VU Meter in the Audio Mixer
The audio mixer meter is coloured in three bands. While you talk, aim for the green zone rising into yellow on louder words; hitting red means you are close to distorting. If the bar barely moves, the signal is too low. The volume slider under each source (the fader) only scales what OBS sends out, it does not change what the mic captures.
Gain Staging: A Worked Mic Level Example
Gain staging means setting the hardware input gain or preamp first, then using the OBS gain filter only for trimming. Say your test shows speech averaging -21.4 dBFS, peaks at -11.2 dB and a silent room at -54.6 dB. Your mic level is 3.4 dB too quiet, but you also have to keep the peaks under -6 dB, so the gain you can add sits in a window:
$$G_{min} = -18 - (-21.4) = 3.4\ \text{dB}, \qquad G_{max} = -6 - (-11.2) = 5.2\ \text{dB}$$Adding +4 dB lands speech at -17.4 dB and peaks at -7.2 dB, both inside the targets. The room rises with it to -50.6 dB, because gain lifts the whole signal equally; the gap between voice and room stays 33.2 dB. Pushing past +5.2 dB, or turning on Windows microphone boost, would add distortion on loud words, so any extra loudness should come from a compressor, not more gain. The quiet room also sets your gate threshold, below.
Tuning Audio Filters With the Microphone Tester
Right-click your mic in the mixer and choose Filters. Order matters, because each filter processes what the previous one hands it. A clean filter chain for voice:
- High pass filter set just under your voice's lowest note removes desk rumble and air-conditioning hum.
- Noise suppression: RNNoise handles fans, hiss and keyboard noise more naturally; Speex uses less CPU on older machines.
- Noise gate closes the mic between sentences.
- EQ (equaliser): a small presence lift in the upper mids adds clarity.
- Compressor evens out loud and quiet words so your voice stays above game audio.
- Gain filter last, as a final trim.
Rerun the test after each change. If the room level falls well under -60 dB once suppression is on, the background noise is handled; if your voice starts sounding watery, lower the suppression strength. Hardware noise cancellation on a wireless kit can do the same job, so avoid stacking two aggressive stages of these audio filters.
Setting Noise Gate Thresholds From Room Noise
Set the noise gate's close threshold about 10 dB above your measured room level and the open threshold about 6 dB above that. In the example, with the room at -50.6 dB after gain, that is roughly -40 dB to close and -34 dB to open. Keep attack short (a few ms), hold around 150-250 ms so words don't get chopped, and a release near 100-150 ms. If your voice cuts in and out, the close threshold is too high; lower it by 3 dB at a time.
Record a Test Clip and Check Playback
Meters only prove OBS sees a signal, even when the recording is silent; a test recording proves the recording file has it. Record a 20-second test clip: talk, play a few seconds of a video, clap once, then stop and open the file in another player.
- Is your voice audible on playback, at the same loudness as the desktop audio?
- Does the clap line up with the video? If not, fix audio sync with the source's sync offset before you worry about delay elsewhere.
- Any clicks, hiss or pumping from the gate?
This is the quickest way to test your mic chain end to end, and the same clip shows whether your separate mic track (for example Track 2) is ready for VOD editing in post-production.
Checking a Speedrun Commentary Mic With a Test Recording
The decision here is simple: can one gain setting cover both calm commentary and the shout when a split lands, or does the chain need compression? The answer, worked out below, is that gain alone fails, and a 3:1 compression stage plus 3 dB of make-up gain fixes it.
A dynamic mic runs into an interface with the preamp at about two-thirds. I run the microphone test on this page twice: once talking through a route at normal volume, once shouting the way I do on a personal best. The readings come back as:
- Normal speech: -26.8 dBFS average, with louder words reaching -15.9 dB.
- The shout: -4.7 dB.
With only the calm pass, the gain window looks easy: speech needs at least +8.8 dB to reach -18, and normal peaks allow up to +9.9 dB before -6. So I try +9 dB. Speech lands at -17.8 and normal peaks at -6.9, but the shout goes to +4.3 dB, over the 0 dBFS ceiling, and that clips. The shout's own limit is -1.3 dB of gain, so no positive gain satisfies both readings. That conflict is invisible if you only test your normal voice.
So I keep +9 dB and add compression with its threshold at -20 dB and a 3:1 ratio, then 3 dB of make-up. By hand, anything above -20 keeps a third of its overshoot: the shout becomes -20 + 24.3 / 3 = -11.9, plus 3 = -8.9 dB.
| Reading | Raw | +9 dB gain only | +9 dB, 3:1 at -20, +3 dB make-up |
|---|---|---|---|
| Speech average | -26.8 | -17.8 | -16.3 |
| Normal peaks | -15.9 | -6.9 | -12.6 |
| Shout | -4.7 | +4.3 (clips) | -8.9 |
I then make a short test recording with the shout in it and watch the OBS meter: the shout stays in the yellow. One caveat: these figures use a static curve. Real compression needs a few milliseconds to react, so the first instant of a shout can still overshoot. I'd add a limiter at -6 dB as a safety net rather than trust the arithmetic alone.
The input that matters most here is not the speech average but the gap between calm talk and the loudest moment, 22.1 dB in this case. Once that gap passes about 12 dB (the distance from -18 to -6), no gain setting alone can work.
Test Your Mic Through Audio Monitoring
To hear exactly what viewers hear, click the gear icon in the mixer, open Advanced Audio Properties and pick a monitoring mode. Always use headphones: speakers feed your voice back into the mic and cause echo and feedback.
| Monitoring mode | You hear it | Sent to stream and recording |
|---|---|---|
| Monitor Off | No | Yes |
| Monitor Only | Yes | No (mute output) |
| Monitor and Output | Yes | Yes |
Use Monitor and Output while you test OBS audio, then switch back to Monitor Off if hearing your own latency is distracting. Leaving a mic on Monitor Only is a classic reason a recording ends up silent even though you heard yourself the whole time.
The Pre-Stream Test: Run a Test Stream on Twitch or YouTube
The last pre-stream test checks the real output. On Twitch, add ?bandwidthtest=true to your stream key so the broadcast goes nowhere public; on YouTube, set the stream to Private or Unlisted. Start the test stream, then listen on a phone before you go live publicly, not on the PC running OBS, to avoid feedback and confused routing. If the voice is thin or quiet there but fine locally, check that the audio bitrate is at least 160 Kbps under Settings > Output.
Microphone Audio Not Working in OBS: Causes and Fixes
If this test hears you but OBS does not, the mic itself is fine and the signal is being lost at a setting. Work through these in order before you go live again; this is the same checklist a mic test for OBS points you to when the meter stays flat.
Wrong Mic/Aux Device, Muted Fader or Missing Driver
- Select your mic by name under Settings > Audio and click OK.
- Check the speaker icon (the mute button, red when muted) and that the volume slider isn't dragged fully left.
- Confirm the mic moves in Windows Sound Settings; if it doesn't, reinstall the driver or try another USB port.
Recording Track Not Enabled in Output
OBS writes audio to numbered tracks. In Advanced Audio Properties, note which tracks the mic uses, then open Settings > Output > Recording and enable the same ones. If the mic is only on a track the recording doesn't write, the audio track in the recording is empty. Track 1 is the default for both.
Microphone Access and Exclusive Mode on Windows and macOS
- Windows 10/11: Settings > Privacy & Security > Microphone, and turn on desktop app access. Then fully restart OBS before recording again.
- macOS: System Settings > Privacy & Security > Microphone, and enable OBS. If OBS isn't listed, open it with the mic connected so macOS shows the permission prompt.
- If the mic works in Discord or Zoom but not OBS, untick "Allow applications to take exclusive control of this device" in the mic's Properties > Advanced tab.
Sample Rate Mismatch: Robotic Voice, Crackling and Popping
When Windows runs the mic at 44.1 kHz and OBS at 48 kHz, you get a robotic tone, odd pitch or crackling. Set both to 48000 Hz (Properties > Advanced > Default Format on Windows, Audio MIDI Setup on macOS) and restart OBS.
Quiet, Delayed or Missing Desktop Audio on the Stream
- Set Desktop Audio to your real output device, not Default; some exclusive-mode games and DRM content can't be captured.
- If voice is quiet only on the stream, raise the source slider toward 0 dB and check your compressor in your mic settings.
- For a delay between voice and video, use the Sync Offset in OBS audio properties.
Choosing an OBS Microphone for Streaming
Any of these works in OBS Studio, but your mic type changes how hard the filters have to work:
- USB mic (usually a condenser): plug and play, very sensitive, picks up the room.
- XLR dynamic mic through an audio interface: rejects room noise but needs plenty of gain; condensers on XLR need 48V phantom power.
- Headset mic: convenient, but use stronger RNNoise suppression and a tighter gate.
- Lavalier or wireless microphone: check the receiver shows up as an input in the OS and that the transmitter isn't muted before blaming OBS.
Mic Placement and Room Acoustics
Keep the mic about a hand's width from your mouth, slightly off-axis, and use a pop filter to stop plosive bursts. Soft furnishings cut the reverb that no filter fully removes. After moving the mic or softening the room, rerun the test: the silent-room reading should drop, and P and B sounds should stop pushing peaks toward -6 dB, which leaves your OBS gate and gain settings less work to do.
Frequently Asked Questions
- How do I test my microphone for OBS without opening OBS?
- Run this test in your browser: allow microphone permission, talk at your normal volume and read the RMS level, peak and noise floor. These are the same signal levels OBS receives from the mic, so you can set gain before opening OBS Studio.
- What should my mic level be in OBS for streaming?
- Aim for normal speech between about -18 and -12 dBFS with the loudest peaks no higher than -6 dBFS. On the OBS audio mixer that means the bar stays mostly in the green and only reaches yellow on loud words.
- Why does my mic sound robotic in OBS?
- Usually a sample rate mismatch, for example Windows at 44.1 kHz and OBS at 48 kHz. Set both the device (Sound > Properties > Advanced) and OBS (Settings > Audio) to 48000 Hz and restart OBS.
- What are good noise gate settings for OBS?
- A common starting point is a close threshold around -32 dB and an open threshold a few dB higher, with a short attack and a hold near 200 ms. If your voice cuts in and out, lower the close threshold; if room noise still gets through between sentences, raise it slightly.
- Should I use RNNoise or Speex noise suppression?
- RNNoise usually sounds more natural and removes fans and keyboard noise better, at the cost of a little more CPU. Speex is lighter and a reasonable fallback on older computers.
- How do I test OBS audio without going live?
- Make a short local recording: talk, play some desktop audio, stop, then play the file back outside OBS. For the stream itself, use Twitch's bandwidth test mode or a private or unlisted YouTube stream.
- Why does my mic work in Discord but not in OBS?
- Check that OBS is allowed to use the microphone in Windows or macOS privacy settings, and turn off exclusive mode in the mic's Windows properties so another app can't lock the device.
- Does this OBS mic test record or store my audio?
- No. Audio is processed locally in your browser with the Web Audio API, and nothing is uploaded or kept after you close the tab.