Background Noise Rejection Test
The Background Noise Rejection Test plays background noise through your speakers while it records your voice, then plays back the result so you hear exactly how well your microphone rejects noise — instead of testing it in silence. The midi keyboard and controller input test takes under a minute and needs nothing but your browser.
Run a Background Noise Rejection Test and you'll see, in real time, whether your microphone actually filters out the hum, keyboard clatter, and traffic sitting behind your voice — or just passes it straight through to whoever's listening. The result that matters most is how clean your voice sounds once the noise floor is stripped away, not just whether a waveform moves on screen. That distinction is why a plain mic test often isn't enough: it confirms a signal exists, but it doesn't tell you how much of that signal is actually you.
Understanding Your Noise Rejection Test Results
Every microphone captures two things at once: your voice and everything else in the room. A background noise rejection test isolates that second part so you can judge it on its own. Engineers describe the balance between the two with the signal-to-noise ratio, usually shortened to SNR, which is the same measurement broadcasters and podcast editors use to decide whether a recording is broadcast-ready or needs cleanup. Try the free free airpods mic test for a quick, no-install way to check this yourself.
$$ SNR_{dB} = 20 \log_{10}\left(\frac{V_{signal}}{V_{noise}}\right) $$
A higher SNR means your voice sits well above the noise floor; a low one means the room is fighting your microphone for attention. Most built-in laptop mics land in a mediocre range, while a decent USB microphone with active rejection can push several decibels higher.
Noise Suppression and Echo Cancellation Explained
Noise suppression and echo cancellation solve two different problems. The former filters out steady background sound — fans, HVAC hum, distant traffic — by learning what "silence" sounds like in your room and subtracting it.
The latter removes the delayed copy of your own voice or the other caller's audio that bounces back into your mic, which is what causes that hollow, doubled sound on a video call. A test that only checks levels won't catch either failure; you need to actually listen to the sound quality of the recorded clip.
Signal-to-Noise Ratio and Quality Rating
Once you have a reading, compare it against a simple quality rating: anything with a clearly audible hiss under your voice needs work, while a clean gap between the two is a pass. Watch the waveform while you're silent — a real-time waveform that stays nearly flat between words is a strong sign of good rejection, while one that keeps jittering during silence usually means the noise floor is too high.
- A real-time waveform that goes nearly flat the instant you stop talking
- Steady audio input levels with no sudden spikes from background sound
- Clean playback with no clipped or distorted audio track
- Low latency between speaking and hearing yourself if you monitor to yourself
How to Reduce Background Noise Before You Test
You can improve your score before you even open the test. A surprising amount of what people blame on "bad microphones" is actually an untreated noise problem that better habits and noise reduction settings can fix directly at the source, which is always more effective than trying to suppress it after the fact. The check whether your noise suppression is working properly takes under a minute and needs nothing but your browser.
Distance and Room Acoustics
Where you sit matters as much as what hardware you use. Keep a consistent distance between your mouth and the mic — too close and you'll get popped consonants, too far and the room's natural reflections become more prominent than your voice.
- Keep roughly a hand's length of distance between your mouth and the microphone
- Add rugs, curtains, or soft furniture to absorb reflections and cut down on reflected sound
- Avoid bare walls and hard floors, which bounce sound straight back into the mic
Headphones and Feedback During Playback
Wear headphones while you test, not speakers. Running playback through open speakers lets the mic pick the sound back up, creating feedback that has nothing to do with how well your microphone actually rejects noise and everything to do with how you're monitoring the test.
Getting an Accurate Mic Test Reading
This kind of test is really a more demanding version of an ordinary mic test — it doesn't just confirm your microphone works, it grades how well it works under real conditions. Run a plain microphone test in a silent room and almost anything will pass; the useful data comes from repeating an online mic test with the fan on, a window open, or a keyboard nearby, since that's the environment you'll actually be using it in. Judging audio quality this way, rather than in a hushed room, is what separates a mic test that's actually useful from one that just checks a box.
Input Device, Input Volume, and Sample Rate
Before judging the noise rejection itself, confirm the basics are set correctly. Select the right input device from the list, since testing the wrong one wastes the whole session, and check that your input volume isn't clipping — a level that's already too hot will mask any noise-rejection differences.
Sample rate matters too: a higher sample rate captures more detail in both your voice and the noise around it, which makes the rejection algorithm's job easier to evaluate accurately. A loose or damaged cable can introduce its own crackle that looks like background noise but is really a connection issue.
Audio Channels and Automatic Gain Control
Check how many audio channels your microphone reports — most consumer mics are mono, and a stereo reading from a mono mic usually signals a driver misconfiguration rather than a hardware feature. Automatic gain control is worth watching closely during your test: this setting continuously adjusts input sensitivity, and while that smooths out quiet and loud speech, it can also amplify the room's noise floor during pauses, which is exactly the failure mode a rejection test is meant to expose.
| Setting | What It Does | Why It Matters for Rejection |
|---|---|---|
| Noise Suppression | Filters steady background sound like fans or hum | The core setting a rejection test is grading |
| Echo Cancellation | Removes delayed copies of voice bouncing back into the mic | Prevents hollow, doubled audio on calls |
| Automatic Gain Control | Auto-adjusts input sensitivity as you speak | Can amplify noise floor during pauses |
| Sample Rate | How often the mic captures audio per second | Higher rates resolve noise vs. voice more clearly |
| Sample Size | Bit depth of each captured sample | Affects dynamic range between quiet and loud sound |
| Latency | Delay between input and playback | High latency makes real-time monitoring unreliable |
| Quality Rating | Overall score combining the above | Quick pass/fail read on rejection performance |
Troubleshooting Background Sound Testing Problems
If your results look worse than expected, the cause is usually mundane rather than a bad microphone. Work through the common culprits before assuming your hardware can't handle background sound testing.
Driver Issues and Connection Problems
Most failed rejection tests trace back to one of two things: outdated software or a loose physical connection.
Driver Issues
An outdated driver can silently disable this feature even when the setting looks enabled in software. Update it through your device manager or the manufacturer's site, then reload the test.
Connection Problem
Check that the cable is fully seated in the audio jack — a connection problem this small can look identical to a hardware failure, but it's the easiest thing on this list to rule out first.
Microphone Permission and Browser Access
If the test never starts, your browser probably hasn't been granted microphone permission yet. Every modern browser requires explicit browser access before any site can read from your microphone, so check the address bar for a blocked-permissions icon.
System Settings and Privacy
Beyond the browser, check your operating system's own privacy settings — some system settings block microphone access at the OS level even after the browser prompt is approved, which is a common source of confusion.
Your Recordings Stay Private
Everything in a browser-based test runs locally; nothing is uploaded unless you choose to save it.
Testing on Windows 10, AirPods, and External Microphones
Setup varies slightly by device. On Windows 10, confirm the correct input is selected under Sound settings before testing.
An AirPod microphone routes through Bluetooth, which adds latency the test will pick up. Any external microphone — USB microphone or otherwise — should be selected explicitly rather than left on the system default, and a wireless microphone in particular benefits from a dedicated check since interference can masquerade as poor noise rejection.
Browser and OS compatibility notes
Windows 10 Chrome, Firefox, Edge macOS Safari, Chrome, Firefox Linux Firefox, Chromium iOS/iPadOS Safari, Chrome
Advanced: squeezing out a little more latency
Closing other apps that touch audio, disabling Bluetooth on wired setups, and testing at a higher sample rate can shave a few extra milliseconds off your reading.
- Pick the correct input device from the device selector before you start test
- Close Zoom, Teams, or Discord if they're running in the background
- Check the cable and update your driver if the reading looks off
- Confirm system settings and microphone permission are both granted
- Record a short test clip, then compare it against a wireless microphone if you own one
Real-World Uses for a Background Noise Rejection Test
Beyond a one-off check, this kind of test is worth running any time your setup changes — a new room, a new headset, or a new streaming layout. It's a fast way to confirm clear digital communication before something important, rather than finding out mid-call that the other side can't hear you over the noise.
Podcasts, Livestreams, and Video Calls
Podcast hosts, live stream broadcasters, and anyone on frequent video calls all rely on the same underlying rejection performance, just in different contexts. If your webcam has a built-in mic, don't assume it inherits your external microphone's noise rejection — test it separately, since built-in units are usually the weakest link in an otherwise solid setup.
Recording, Playback, and Sharing Clips
Once you're happy with the reading, make a short recording and listen back to the playback with headphones. Downloading it as an MP3 or uncompressed WAV file lets you archive it alongside the rest of your audio recording library, or do a side-by-side comparison against a previous test clip to confirm an upgrade actually helped.
"I finally figured out why my calls sounded muffled — turns out automatic gain control was amplifying my fan noise the whole time." — Dana R.
"Ran the test with headphones on like it suggested and immediately heard how much room noise I'd been ignoring for months." — Marco T.
"Simple, no sign-up, and the playback download made it easy to compare two microphones side by side." — Priya K.