Can I test my mic before Zoom, Teams, Google Meet, or Discord?

Yes. Run the test, confirm that the correct input is selected, speak through the guided noise-and-level check, and play back a short recording. Then choose the same microphone inside your call app. The call app may apply its own echo cancellation or noise processing, so its final sound can differ slightly from the browser recording.

Why is my microphone not working?

The two most common causes are blocked browser permission and the wrong input device being selected. Click the lock or site-info icon in your browser's address bar, confirm Microphone is set to Allow, then reload the page. If the meter still does not move, open the device dropdown above and pick the correct microphone.

Does the mic test work on mobile phones?

Yes. The mic test works on Android (Chrome, Edge, Firefox, Brave, Opera) and iPhone / iPad (Safari). On iOS you must use Safari. The site must be served over HTTPS for browsers to allow microphone access.

Can I record my voice and play it back?

Yes. Start the mic test, click Record 10s Test, and listen with the built-in player. This lets you hear the selected microphone as recorded by the browser. A call app may sound slightly different if it adds noise suppression, gain control, or other processing.

How do I fix microphone permission blocked?

Click the lock icon (or site-info icon) to the left of the URL in your address bar. Find the Microphone setting and change it to Allow. Then reload the page and click Start Mic Test again.

Why is my mic too quiet even though it works?

Move closer to the microphone (a headset boom should sit 2 to 5 centimetres from the corner of your mouth), increase the operating-system input level (Windows: Sound Settings, Mac: System Settings → Sound → Input), and remove software like Krisp or NVIDIA Broadcast that may be processing the signal before it reaches the browser.

How does the latency test work?

The latency test plays a short click through your speakers and measures when the microphone picks it up. The result is a rough acoustic round-trip estimate that includes browser scheduling, speaker output, the room, and microphone input. Use it to compare setups on the same device, not as a promise of call-platform latency.

What is a good background noise level?

Our 5-second noise meter rates from Studio quiet (under -55 dBFS) to Too loud (above -35 dBFS). For calls, Office quiet or better is fine. If it rates worse, move away from fans, AC vents, open windows, or busy hallways.

Why does my mic show as mono in the stereo check?

Almost all microphones used for calls — headsets, USB mics, laptop built-ins, smartphone mics — are mono. That is correct and expected. Stereo mics exist mostly for music recording.

Will Krisp or NVIDIA Broadcast affect the mic test?

Yes — those tools create a virtual microphone. To test the actual hardware mic, either close those apps or pick the raw hardware device from the dropdown above (for example Headset Microphone Realtek rather than Krisp Microphone).

Why is my microphone picking up the other person's voice on calls (echo)?

That is speaker bleed — your speakers are loud enough that your mic re-captures the other person's voice. Fix: wear headphones. If you must use speakers, lower their volume, move them further from the mic, and enable the call app's echo cancellation.

Can I use this mic test on a call-center workstation?

Yes. Open the page in a supported browser on the agent station, run the guided test, play back a short recording, and then select the same headset inside the softphone. If browser microphone access is managed by your IT team, you may need them to allow the site first.

What does the technical readout show?

Device name as reported by your OS, sample rate (typically 44100 Hz or 48000 Hz), channels (1 = mono, 2 = stereo), recording codec, and browser engine. Useful for IT troubleshooting and confirming your setup matches what your call app expects.

✓ 100% Free · No Sign-Up · No Download

Free Mic Test Online

Test your microphone in your browser before Zoom, Teams, Google Meet, Discord, calls, meetings, or recordings. Live input meter, device selector, and a built-in 10-second record & playback.

Works in browser
No upload
Test before calls
Mobile-friendly

Test Your Microphone No clipping

Audio never leaves your device

Input device

Signal quality —

Frequency range —

Click "Start Mic Test" to begin. Allow microphone access when prompted by your browser.

Record & play back your voice

Record ten seconds and play it back to hear the selected microphone as captured by your browser. Call apps may add their own processing, so their final sound can differ.

Microphone blocked? Fix it in a few seconds:

Click the lock icon (or site-info icon) to the left of the URL in your browser's address bar.
Find the Microphone setting and change it to Allow.
Reload this page and click Start Mic Test again.

Device: — Sample rate: — Channels: — Codec: — Browser: —

Privacy: All audio is processed entirely in your browser using the Web Audio API. Nothing is recorded, saved, or uploaded by this page. Only the optional 10-second test recording is created — and only on your own device.

Permission: When prompted, click Allow on your browser's microphone request. If you previously blocked it, use the lock icon in the address bar to reset the permission.

100% private — nothing uploaded No download — pure browser Works on mobile — iOS & Android Free forever — no signup

Advanced microphone tests

Start the main mic test above first — then run any of these advanced tests to dig deeper into your microphone setup.

Echo & monitor test

Live loopback

Hear your own voice in real time with the same signal your call apps receive. Use headphones — speakers will cause feedback.

Wear headphones before enabling. Speaker playback will create a feedback loop.

Idle — start the mic test, then click Enable Echo.

Background noise level

5-sec sample

Stay silent for 5 seconds — we'll measure your room's ambient noise floor and rate it from Studio-quiet to Too loud.

Idle — start the mic test, then click Measure Noise Floor.

Stereo & channel check

L vs R peak

Detect if your microphone is true stereo or mono, and which channel is hot. Most call mics are mono — that's expected and correct.

Idle — start the mic test to see channel info.

Latency test

Round-trip ms

Measures the round-trip time between your speakers and your mic. Lower is better — under 100 ms is excellent for live calls.

ℹ This test plays a short test tone through your speakers. Take headphones off or use a separate set with speakers.

Idle — start the mic test, then click Measure Latency.

How to test your microphone online

Plug in or connect your mic — USB, 3.5 mm, Bluetooth, or built-in laptop microphone all work.
Click "Start Mic Test" above and approve your browser's permission prompt.
Pick the right input from the device dropdown if you have more than one microphone (headset, webcam, built-in, USB).
Speak at your normal call volume — say a full sentence, not just "hello." Watch the live meter and spectrum react.
Check the quality rating — "Excellent" or "Good" means you're ready for calls. "Weak" or "Silent" means it's time to move closer or boost your input level.
Try the 10-second recording to hear the microphone selected in your browser. Your call app may apply additional processing.

Why test your mic before calls and meetings

A bad microphone costs you sales calls, job interviews, client meetings, and team trust. People stop listening the moment your voice sounds muffled, distant, or distorted. Running a quick mic test before you join a call:

Confirms the correct input device is selected — the #1 cause of "they can't hear me"
Catches background noise, echo, or clipping before the meeting starts
Lets you verify your gain level — too low sounds weak, too high sounds harsh and distorted
Saves you from awkward "can you hear me now?" moments on Zoom, Microsoft Teams, Google Meet, Discord, Slack, Skype, WhatsApp, or Webex
Confirms your headset or webcam mic is the one being used, not a forgotten built-in mic from across the room

Common mic problems & quick fixes

Microphone permission blocked

If clicking Start Mic Test does nothing, the browser has likely blocked mic access. Click the lock or site-info icon in the address bar, find Microphone, set it to Allow, and reload the page.

Mic is too quiet

If the rating shows "Weak" or "Silent": move closer (a headset boom should sit 2–5 cm from the corner of your mouth), increase the OS input level, and remove voice-processing software (Krisp, NVIDIA Broadcast, Discord noise suppression) that may be muting the signal before your browser sees it.

Wrong input device selected

Many laptops have 2–4 microphones available at once (built-in array, webcam, USB headset, Bluetooth). Use the device dropdown above to pick the right one. Note: browsers only show device labels after you've granted mic permission once.

Background noise or echo

Echo usually means your speakers are too loud and the mic is picking them up — use headphones. Background hum or fan noise can be reduced with a noise gate in the VoxBoost Voice Enhancer.

Microphone is too loud (clipping)

If the meter pegs red and audio distorts: lower the input level in your OS sound settings, disable any "mic boost" toggle, and move slightly off-axis from the mic so you're not breathing directly into it.

Browser compatibility

The mic test works in modern Chrome, Edge, Firefox, Safari, Brave, Opera, and Vivaldi on Windows, macOS, Linux, ChromeOS, Android, and iOS. The page must be served over HTTPS for the browser to allow microphone access. On iPhone/iPad, Safari is required.

OS-specific mic fixes

Windows 10 / 11

Open Settings → System → Sound → Input. Pick the right device, click Properties, and check the input level. Also confirm Microphone privacy allows desktop apps and your browser to access the mic.

macOS

Open System Settings → Sound → Input. Select the correct device and adjust the input level slider. Then check Privacy & Security → Microphone and ensure your browser has access.

iPhone / iPad

Use Safari over HTTPS. Open Settings → Safari → Microphone and confirm it's set to Ask or Allow. On the page, tap Start Mic Test and approve the prompt. Other iOS browsers also use Safari's engine.

Android

In Chrome, tap the three-dot menu → Settings → Site settings → Microphone. Make sure it's set to Ask first. On the page, tap Start Mic Test and tap Allow when prompted. Works in Chrome, Edge, Firefox, Brave, Opera.

ChromeOS / Chromebook

Open the Chromebook Settings → Privacy and security → Site settings → Microphone. Allow access for this site. Built-in mics and USB headsets both work — pick the right input from the device dropdown above.

Linux

Most distributions use PulseAudio or PipeWire. Open Sound Settings → Input, pick the right device, and raise the input level. In Chrome/Firefox, allow microphone access for this site.

Test your mic before any calling app

Quick app-specific steps. Run the mic test above first, then jump to your app's section to confirm the same mic is selected and the input level matches.

Mic test for Zoom

Open Zoom → Settings → Audio.
Set the mic to the same device you just tested.
Click Test Mic, speak, and confirm playback.
Uncheck Automatically adjust microphone volume if Zoom keeps changing your level.
Match the input level you saw in our meter above (Good/Excellent).

Mic test for Microsoft Teams

Click your profile photo → Settings → Devices.
Pick the same microphone you tested above.
Use Make a test call to hear your voice back.
Disable Noise suppression: Auto if your voice sounds chopped.

Mic test for Google Meet

Join a meeting (or start a new one) → click the gear icon .
Open the Audio tab.
Pick the same mic you tested in the dropdown.
Speak — the green dots next to your mic should light up.
If silent, check browser-level mic permission for meet.google.com.

Mic test for Discord

Open Discord → User Settings → Voice & Video.
Pick your input device.
Click Let's Check under Mic Test, speak.
Set Input Sensitivity manually if voice activity cuts out mid-sentence.
Turn off Krisp if it muffles your voice.

Mic test for Webex

Open Webex → Settings → Audio.
Pick the same mic you tested above.
Click Test and speak — the level bar should jump.
For poor calls, switch Audio mode to Music for higher fidelity.

Mic test for Skype

Open Skype → click ••• → Settings → Audio & Video.
Pick the right microphone.
Watch the level bar — speak normally; it should fill with blue.
Call the Echo / Sound Test Service contact to hear your voice played back.

Mic test for WhatsApp Web / Desktop

On web.whatsapp.com click the lock icon next to the URL.
Confirm Microphone is set to Allow.
Start a call to a friend — or use WhatsApp's voice message button as a quick playback test.

Mic test for FaceTime

On iPhone/iPad: Settings → FaceTime — confirm it's enabled.
On Mac: open FaceTime → Video menu → pick the right Microphone source.
Run our mic test in Safari first to confirm the mic works system-wide.

Mic test for OBS / Streamlabs

In OBS: Settings → Audio → Mic/Auxiliary.
Pick your device. Add the Compressor + Noise Suppression filters.
Watch the audio meter in OBS while you speak.

Mic test for Slack Huddles

Slack → Preferences → Audio & video.
Pick the microphone you just tested.
Click Use a Huddle to test with a coworker.

Mic test for RingCentral

App → Settings → Audio.
Pick the same input device as our test.
Click Test Microphone — speak — confirm the bar moves.

Mic test for Five9 / Genesys

Most call-center softphones use your OS default mic — confirm it matches our test.
If the agent station has a USB headset, plug it in before launching the softphone.
Restart the softphone after switching devices.

Mic test in every browser

All major browsers support the Web Audio API used here. If you're getting blocked, the fix is usually in the lock icon to the left of the URL.

Mic test in Chrome

Click the lock icon next to the URL.
Site settings → Microphone → Allow.
Reload. Best overall performance and codec support.

Mic test in Edge

Click the lock icon → Permissions for this site.
Set Microphone to Allow.
Same engine as Chrome — identical quality.

Mic test in Firefox

Click the icon to the left of the URL.
Remove the Blocked Temporarily entry for Microphone.
Reload, then click Allow on the new prompt.

Mic test in Safari

Safari menu → Settings → Websites → Microphone.
Set this site to Allow.
Required on iPhone & iPad — third-party iOS browsers all use Safari's engine.

Mic test in Brave

Brave Shields may block — click the lion icon and set Shields to Down for this site if needed.
Then lock icon → Site settings → Microphone → Allow.

Mic test in Opera

Lock icon → Site settings → Microphone → Allow.
Disable any built-in VPN if mic permission keeps resetting.

Mic test in Vivaldi

Lock icon → Site settings → Microphone → Allow.
Same Chromium engine as Chrome — full feature support.

Mic test in private/incognito mode

Most browsers ask for permission again in private windows.
Permission is forgotten when the private window closes — that's normal.

Works with every type of microphone

USB, 3.5 mm, Bluetooth, headset, lavalier, podcast, or your laptop's built-in — all use the same browser API and all show up in the device dropdown.

USB mic test

Plug the USB mic in before opening the browser.
Pick it from the device dropdown above (look for the brand: Blue Yeti, Shure, Samson, FIFINE, etc.).
USB mics usually give the cleanest signal — no preamp needed.

Headset mic test

Headsets give the best speech intelligibility for calls.
Position the boom 2–5 cm from the corner of your mouth.
Excellent & Good ratings here mean you're call-ready.

Bluetooth mic test

Pair the device in your OS settings, then refresh this page.
Pick the Bluetooth device from the dropdown.
Bluetooth typically adds 100–200 ms latency — fine for calls, bad for live music.

3.5 mm jack mic test

Plug in to the pink/red mic input (or a combo TRRS headset jack).
If silent, your OS may have routed it to the wrong port — check Sound settings.

Built-in laptop mic test

Usually labelled Internal Microphone or Microphone Array.
Sounds boxy and picks up keyboard — fine in a pinch.
Tip: cover the speaker grille area to confirm you're testing the right hole.

Podcast / studio mic test

Pick the mic from the dropdown.
Aim for Excellent rating; bass-rich condenser mics may need a high-pass filter on the call side.

Lavalier mic test

Clip 10–15 cm below your collar, on a flat surface (no fabric rubbing).
Run our test and confirm Good or Excellent rating before recording.

XLR mic via interface test

Interfaces like Focusrite Scarlett or PreSonus AudioBox appear as a single input.
Set gain on the interface to where peaks hit -6 dB without clipping.
The clipping pill above will turn red if you push too hot.

Microphone troubleshooting — 30-second guide

Walk through these in order. By question 5 you'll know exactly what's wrong.

1Does the live meter above move when you speak?

Yes → your mic is working. Skip to your call app's settings and pick the same input device.

No → permission is blocked or the wrong device is selected. Go to question 2.

2Did the browser show a permission prompt?

Yes, and I clicked Allow → go to question 3.

No prompt appeared → click the lock icon next to the URL, find Microphone, set to Allow, reload, click Start Mic Test again.

I clicked Block by accident → same as above — reset via the lock icon.

3Have you opened the device dropdown above and confirmed the right mic is selected?

Yes → go to question 4.

No → open it. Pick your USB / headset / Bluetooth mic by name — not the laptop built-in. Click Start Mic Test again.

4Is any other app currently using the microphone?

Yes → close Zoom, Teams, Discord, OBS, voice typing, and any virtual mic software (Krisp, NVIDIA Broadcast). Some apps grab exclusive access. Reload the page.

No → go to question 5.

5Is the OS input level above zero?

Yes, level looks normal → the mic itself may be broken. Test on another device or with another app to confirm.

It's at 0 or muted → raise it. Windows: Sound Settings → Input → Properties. macOS: System Settings → Sound → Input. iOS/Android: there's no global level slider; check the mic isn't physically obstructed.

6Voice is detected but sounds bad?

Too quiet → move closer, raise OS input level, disable noise suppression that's gating you out.

Clipping (red pill above) → lower OS input level until peaks stay green/yellow.

Echoey → use a headset; speaker pickup is the cause.

Robotic / chopped → Bluetooth bandwidth issue. Try a wired mic.

Why VoxBoost AI is the best free mic test online

Side-by-side with the other free mic test sites you might land on. Built for real call agents — more features, more privacy, more depth.

Feature	VoxBoost AI	Typical free mic test site
Live spectrum visualizer	Yes	Basic level bar only
Record & playback	Yes — 10-second tester + download	Some sites only
Echo / monitor loopback	Yes	No
Background noise level meter	Yes — 5-sec ambient sample	No
Stereo / channel check	Yes — L vs R peak meters	No
Latency test	Yes — round-trip ms	No
Clipping detector	Yes — live red-flash warning	No
Technical readout (sample rate, channels, codec)	Yes	No
App-specific guides (Zoom, Teams, Meet, Discord, etc.)	12 guides	Few or none
OS-specific fixes (Win, Mac, iOS, Android, ChromeOS, Linux)	6 OSes covered	1–2 only
Browser-specific instructions	8 browsers	No
Mic-type guides (USB / Bluetooth / 3.5mm / XLR / built-in)	8 types	No
Troubleshooting wizard	Yes — 6-step decision tree	No
Works on mobile	Yes — Android & iOS	Desktop-first
100% private — no upload	Yes — Web Audio API local only	Most do, but unclear
Free forever	Yes	Usually yes
No signup / no email	Yes	Usually yes
No ads on tool	Yes	No — ads everywhere

Mic Test FAQ

Yes — completely free. No sign-up, no email, no download. The mic test runs entirely in your web browser using the Web Audio API.

No. All audio is processed locally in your browser. Nothing is recorded, stored, or sent to any server unless you choose to download the optional 10-second test recording yourself.

Yes. Confirm the correct input, complete the guided quiet-and-speech check, and play back a short recording. Then choose the same microphone inside Zoom, Teams, Meet, Discord, or your softphone. Those apps may apply their own audio processing, so the final sound can differ slightly.

Most often it's a permission issue or the wrong input device. Check the lock icon in your address bar and confirm Microphone = Allow. Then use the device dropdown above to pick the correct mic. If you still see no bars, try unplugging and reconnecting your mic, or restart the browser.

Yes. It works on Android (Chrome, Edge, Firefox, Brave, Opera) and iPhone / iPad (Safari). The site must be served over HTTPS. On iOS you must use Safari.

Yes. Start the test, click Record 10s Test, and listen with the built-in player. You will hear the microphone as recorded by the browser. For longer recordings and self-review, use the Practice Recorder.

All modern browsers: Google Chrome, Microsoft Edge, Mozilla Firefox, Safari, Brave, Opera, and Vivaldi — on Windows, macOS, Linux, ChromeOS, Android, and iOS.

Click the lock icon (or site-info icon) to the left of the URL in your address bar. Find Microphone and change it to Allow. Then reload the page and click Start Mic Test again.

Move closer to the mic (a headset boom should sit 2–5 cm from your mouth), increase the OS input level (Windows: Sound Settings → Input → Properties; macOS: System Settings → Sound → Input), and remove software like Krisp or NVIDIA Broadcast that may be processing your signal before the browser sees it.

Yes. The browser shows a clear permission prompt before any audio is read, and you can revoke permission at any time. No audio is uploaded, no account is created, and no data leaves your device.

Clipping happens when your input signal is louder than the microphone can handle — peaks get cut off and the sound becomes distorted. When you see the red Clipping! warning, lower your OS mic input level until the pill stays green or yellow. On a call this is the difference between sounding clear and sounding crunchy.

The test plays a short click through your speakers and measures when the microphone picks it up. That number includes browser scheduling, speaker output, the room, and microphone input, so treat it as a rough comparison between setups on the same device—not a measurement of your call platform or internet connection.

The five-second sample reports the microphone’s noise level in dBFS. It is useful for comparing rooms or microphone positions, but it is not a calibrated sound-pressure reading. If the input noise is high, move away from fans, vents, open windows, and hard reflective surfaces, then repeat the sample.

Almost all microphones used for calls — headsets, USB mics, laptop built-ins, smartphone mics — are mono. That's correct and expected. Stereo mics exist mostly for music recording. If the stereo check shows roughly equal L and R activity, it's a mono mic duplicated across channels (also normal). True stereo only matters for music and binaural recording.

Yes. Connect headphones, start the main test, then click Enable Echo. This sends the raw browser microphone signal to your headphones so you can check the selected input. It does not reproduce the processing used by a call app. Do not enable it through speakers, because that can create loud feedback.

Yes. ChromeOS uses Chrome, which fully supports the Web Audio API and MediaRecorder. Allow microphone access when prompted, pick your device from the dropdown, and run the test. Built-in mics, USB headsets, and Bluetooth devices all work.

Yes — if those tools create a virtual microphone, your browser may pick up the processed stream instead of the raw signal. To test the actual hardware mic, either close those apps before testing, or pick the raw hardware device from the dropdown above (e.g. Headset Microphone (Realtek) rather than Krisp Microphone).

That's speaker bleed — your speakers are loud enough that your mic re-captures the other person's voice and sends it back. Fix: wear headphones. If you must use speakers, lower their volume, move them further from the mic, and turn on the call app's echo cancellation (Zoom and Teams both have it built-in).

Yes. Open the page in a supported browser on the agent station, complete the guided test, play back a short recording, and then select the same headset inside your softphone. If your employer manages browser microphone permissions, ask the IT team to allow voxboostai.com.

After you start the test, the readout shows: Device (the mic's name as reported by your OS), Sample rate (typically 44100 Hz or 48000 Hz), Channels (1 = mono, 2 = stereo), Codec (the recording format the browser will use), and Browser (which browser engine is running). This is useful for IT troubleshooting and for confirming your setup matches what your call app expects.

It goes beyond a basic moving bar: you get a guided quiet-and-speech check, live spectrum, ten-second playback, headphone monitoring, background-noise measurement, channel information, a rough latency comparison, clipping detection, and troubleshooting guides. No account or audio upload is required.

If everything rates Good or Excellent, you're ready for calls. If you want to go further: try our free voice enhancer for real-time EQ and compression, or our practice recorder to rehearse your pitch before a real call.