Free · Real-time · No upload · No sign-up

Mic Test — Free Online Microphone Test with Live Waveform, Spectrum & Diagnostics

Test your microphone in seconds. Click Enable microphone, allow access, and this tool shows a live waveform, a frequency spectrum, a professional dB VU meter with a loudness verdict, a rolling level history, and full device diagnostics. A software gain slider raises the signal inside this page (it does not change your operating system or hardware gain). Record a sample, play it back, and download it as a WAV file. Everything runs in your browser — your audio is never uploaded and never stored on any server.
🎙️ Live waveform + spectrum 📊 dB VU meter + verdict 🔊 Software gain control 🔴 Record & download WAV 🔒 Audio never uploaded

Microphone Test

Enable access → speak → check the meter → record a sample.
Microphone not started
Click “Enable microphone” below. Your browser will ask for permission.
Ready to test your microphone?
This tool will ask your browser for microphone permission. Nothing is uploaded — the entire test runs locally on your device.
🔒 No upload ⚡ Instant 📱 Works on mobile 🖥️ Chrome · Firefox · Safari · Edge
Peak this frame
— dB
RMS this frame
— dB
Detected pitch
—
Processing rate
— Hz
Channels
—
Input latency
— ms
Echo cancellation
—
Noise suppression
—
Auto gain control
—
Device
—
Record & play back
Ready
Guided tests · click each item to tick it off

What each reading means

A quick guide to every number on the tool above.
dBFS (decibels relative to full scale)
Digital audio tops out at 0 dBFS — above that, samples clip and distort. Real sounds sit below it, so levels are shown as negative numbers. Normal speech peaks around −12 to −6 dBFS, quiet speech −30 to −20 dBFS, and silence is below −60 dBFS.
Peak vs RMS
Peak is the single loudest sample in the current window — it tells you how close you are to clipping. RMS is the average power over the window and corresponds to perceived loudness. A good signal has both in the target range with the peak sitting at least 6 dB above RMS.
Loudness verdict
The coloured badge next to the VU meter gives an instant read on the current level: Silence below −60 dB, Very quiet −60 to −40 dB, Quiet −40 to −25 dB, Good −25 to −12 dB, Loud −12 to −3 dB, and Clipping at 0 dB.
Software gain
A software multiplier applied to the mic signal before the analyser sees it. Useful for quiet headset mics that cannot be turned up in the operating system. Range 0.25× to 8×. Boosting gain also boosts any background noise, so use the smallest gain that puts your voice into the good range.
Sample rate (Hz)
How many times per second the mic captures a sample. 48,000 Hz is standard for voice and video calls; 44,100 Hz is standard for music. Both are high-fidelity for human hearing (which tops out at about 20 kHz).
Channels
Mono (1 channel) is standard for headsets, laptops, and phone mics — voice is a single source, so stereo would duplicate the same signal. Stereo (2 channels) is used for USB condenser mics, audio interfaces, and stereo field recording.
Latency (ms)
Input latency is not consistently exposed by browsers. This tool displays a value only when the microphone track explicitly reports one; it does not estimate latency from output-device or AudioContext values.
Echo cancellation
A real-time filter that removes speaker output from the mic signal. Essential for voice and video calls but can make recordings sound thinner. If you want a raw sample, disable it in your operating system's sound settings.
Noise suppression
Attenuates steady background noise like fans, air-conditioning, and keyboard clatter. Useful in noisy rooms, but it can also attenuate breath and sibilants in singing — turn it off for musical recording.
Auto gain control (AGC)
Automatically adjusts the input level so quiet speech becomes audible and loud speech does not clip. Convenient for calls, problematic for recording because it changes the level between takes. Turn it off when recording music or podcasts.
Detected pitch (Hz)
The fundamental frequency currently picked up by the mic. Typical human voice ranges: 85–180 Hz for adult men, 165–255 Hz for adult women, and 250–400 Hz for children. Instruments and musical tones will read their fundamental note.

Troubleshooting — mic not working?

Work through these in order. The problem is almost always one of the first four.

1. Browser permission is blocked

Look for a lock, camera, or microphone icon in the address bar. Click it, find “Microphone”, and set it to Allow. Then reload the page and click “Enable microphone” again. Some browsers hide this in a menu — look for “Site settings” or “Site information”.

2. Operating system permission is blocked

macOS: System Settings → Privacy & Security → Microphone → toggle your browser on. Windows 10/11: Settings → Privacy → Microphone → “Allow apps to access your microphone” ON, and “Allow desktop apps” ON. iPhone/iPad: Settings → Safari → Microphone → Ask or Allow. Android: Settings → Apps → Chrome (or your browser) → Permissions → Microphone → Allow.

3. The wrong device is selected

Open the device dropdown at the top of the tool and pick your mic. If the label is missing (shows just “Microphone 1”), you have not granted permission yet — click Enable, then refresh the device list. On Windows, also check the default input device in Settings → System → Sound. On macOS, check System Settings → Sound → Input.

4. The mic is muted at the hardware level

Many headsets, USB mics, and laptops have a physical mute switch, a small red indicator LED, or a key combination (Fn + F4 is common on laptops). Physically verify the mic is not muted. Some USB mics also have a mute knob on the body that has been accidentally turned.

5. Gain is too low or a pad is engaged

Use the software gain slider inside this tool to boost the signal digitally. Beyond that, raise the input volume in your operating system's sound settings. On an audio interface, check the gain knob and make sure the “−10 dB pad” (if present) is not engaged. Speak closer to the mic — 10–20 cm for most condenser and dynamic mics.

6. Another app is using the microphone

Most operating systems allow only one application to hold the mic at a time. Close or mute Zoom, Teams, Discord, Skype, Meet, OBS, GarageBand, Audacity, and any other app that might have the mic open, then click Enable again.

7. Bluetooth headset is in “Stereo” instead of “Headset” mode

Bluetooth headsets have two profiles: Headset / Hands-Free (uses the mic, lower audio quality) and Stereo / A2DP (playback only, high quality). To test the mic, select the Headset profile in the device dropdown or in your operating system's Bluetooth settings.

8. The signal is there but very quiet

If the meter moves slightly but does not reach −20 dBFS on normal speech, the level is too low. Common causes: mic is far away, gain is turned down, Auto Gain Control has failed to adjust, or the physical mic port is a combo jack not receiving enough power. Try a different USB port (avoid unpowered hubs), or use the tool's software gain slider.

9. Crackling or static in the recording

Excessive mic gain amplifies the pre-amp's own noise — turn the gain down and speak closer. A faulty USB cable or a marginal port can also cause crackling; try a different cable and port. On Windows, set the mic's sample rate to 48 kHz in Sound settings to match most applications.

10. Browser tab is frozen or throttled

Browsers throttle background tabs to save battery. Keep the mic test tab visible and in the foreground while testing. If you have dozens of tabs open, close some — some browsers reduce real-time audio performance under heavy CPU load.

What is an online microphone test?

An online microphone test is a browser tool that captures a sample of audio from your microphone, visualises it in real time, and plays it back. It answers one practical question: is my mic working, and is it working well? That question comes up constantly — before a Zoom interview, before recording a podcast, before going live on Twitch or YouTube, before a customer support call, before a remote exam, and before any online meeting where you cannot afford to sound broken.

The tool on this page uses three standard web APIs built into every modern browser: getUserMedia (to ask for microphone access), the Web Audio API (to route and analyse the audio signal), and a ScriptProcessor recording path (to capture a sample you can play back or download). No plugins, no extensions, no account, no installation. The audio never leaves your device.

You get live feedback on five different things at once: the waveform shows the shape of the captured signal after software gain, the frequency spectrum shows which pitches are present, the VU meter shows how loud the signal is in decibels, the level history shows how consistent the level has been over the last fifteen seconds, and the stats panel shows the technical settings (sample rate, channels, latency, filters) that the browser is actually using.

How to use this mic test

  1. Click “Enable microphone”. Your browser will show a permission prompt. Click Allow. If you click Block by mistake, look for the lock or camera icon in the address bar and change the setting back to Allow.
  2. Speak at your normal volume. The waveform and spectrum should visibly move. The VU meter should land in the green or yellow region (roughly −20 to −6 dBFS) on normal speech. The verdict badge will read Good when the level is right.
  3. Switch devices if needed. Use the device dropdown at the top of the tool. If you have a headset, a USB mic, a webcam mic, and a built-in laptop mic, all will appear. Pick the one you actually want to use.
  4. Use the software gain slider if the level is too low. This applies digital gain inside the page — it does not change the microphone hardware or operating-system input level.
  5. Check the diagnostics. The stats panel shows the Web Audio processing rate, channel count, browser-reported processing settings, and whether echo cancellation, noise suppression, and auto gain control are on. Input latency is shown only when the browser reports a usable value.
  6. Record a sample. Click Record, speak for 5–10 seconds, click Stop, then play it back. This is the single best way to catch problems a level meter alone will miss.
  7. Download if you want to keep it. The Download WAV button saves a standard uncompressed WAV file. Open it in Audacity, GarageBand, Voice Memos, Reaper, or any audio editor for a closer look.

Why test your microphone before an important call

Microphone problems are one of the most common sources of frustration in video calls, live streams, and recordings — and almost every problem is preventable. Testing ahead of time gives you three things:

  • Confidence. A thirty-second check before a call removes the low-grade anxiety of “will they hear me?” and lets you focus on the conversation.
  • Diagnostics. If the meter is not moving, you know immediately that something needs fixing and you can troubleshoot before the meeting starts.
  • Quality. Recording a short sample reveals problems the meter alone cannot show — excessive room echo, keyboard noise, plosives on “p” and “b”, sibilance on “s”, and the characteristic Bluetooth voice quality that only shows up when you hear yourself.

Understanding what the tool is showing you

The waveform

The waveform is a plot of the mic signal against time. The centre line represents silence; the further the trace moves away from the centre, the louder the signal at that instant. Spiky waveforms indicate sharp sounds (claps, plosives, clicks); smooth sine-like waves indicate steady musical tones; the irregular, constantly changing shape of the trace is what voices look like. A waveform that hugs the top and bottom edges is clipping — the input is too loud and the sound will be distorted.

The frequency spectrum

The spectrum shows how much energy is present at each frequency. The left side is bass, the middle is mid-range (where voice lives), and the right is treble. A good mic will show a broad, smooth curve on speech — energy across the voice band from about 80 Hz to 8 kHz. Narrow spikes indicate a single tone (a musical note, a whistle, a hum); a spike at 50 or 60 Hz with almost nothing else is electrical hum from a bad cable or a ground loop.

The VU meter and verdict

VU stands for “volume unit”. The meter here shows the signal level in dBFS. The white line marks the peak of the current frame and holds for a moment so you can see it; the coloured bar fills to the current RMS level. The verdict badge next to the meter gives an instant read: Silence below −60 dB, Very quiet −60 to −40 dB, Quiet −40 to −25 dB, Good −25 to −12 dB, Loud −12 to −3 dB, and Clipping at 0 dB. The “CLIP” indicator lights up when the signal reaches 0 dBFS and stays lit — if it lights up, turn your mic gain down.

The level history strip

The bottom strip is a rolling chart of the RMS level over the last fifteen seconds. It is the fastest way to see whether your voice is consistent (flat strip), whether it has sharp spikes (plosives), whether it drops out (Bluetooth dropouts, USB glitches), or whether it is picking up a steady background hum (constant non-zero floor).

The software gain slider

The software gain slider multiplies the captured signal by a factor between 0.25× and 8× inside this page. It does not change the microphone preamp or operating-system input level. Increasing it also raises background noise and can clip the processed signal and recording. Use the smallest gain that gives a useful level.

The stats panel

The stats panel reports the technical details the browser has negotiated for your device. Sample rate and channel count come from the device itself. Latency is reported by the browser when it can be measured. Echo cancellation, noise suppression, and auto gain control are software filters applied either by the browser or by your operating system, and their on/off state is exposed by the browser through the track's settings object.

Target levels for common scenarios

The right level depends on what you are doing. Here is a quick guide to the values broadcast and podcasting professionals actually use.

ScenarioPeak targetRMS targetNotes
Video calls (Zoom, Teams, Meet)−10 to −6 dBFS−22 to −16 dBFSMost conferencing apps apply auto gain, so a slightly quieter signal is fine
Live streaming (Twitch, YouTube)−6 dBFS−18 to −14 dBFSPlatforms normalise to −14 LUFS; peak headroom prevents clipping
Podcast recording−6 dBFS−20 to −18 dBFSAim for a consistent RMS and peak 12–14 dB above it
Music recording−6 to −3 dBFS−18 to −12 dBFSLoud transients (drums) need more headroom
Voice-over / audiobook−6 dBFS−20 to −18 dBFSConsistency matters more than absolute level
Field interview−12 dBFS−22 to −18 dBFSBack off slightly to catch sudden laughs or loud speakers
Podcast interview (two mics)−6 dBFS per mic−20 to −16 dBFSMatch the two mics so one guest is not louder than the other

💡 Rule of thumb. Set your gain so that your normal speaking voice peaks between −12 and −6 dBFS. This gives you headroom for louder moments and keeps you well above the noise floor. If your peaks sit below −20 dBFS, you are too quiet and will need to raise the level in post-processing — which also raises the noise. If your peaks hit 0 dBFS or the CLIP light lights up, you are too loud and the audio is already distorted in ways you cannot fix later.

How the browser actually gets your microphone

When you click Enable, four things happen in sequence, and understanding them makes troubleshooting easier.

  1. The page requests permission. The browser shows a native prompt asking whether to allow microphone access. This is the browser's own prompt, not the page's — the page cannot see your answer until you click something.
  2. The browser grants or denies access. If you allow it, the browser returns a MediaStream object representing the live audio. If you deny it, the page gets an error and shows a message.
  3. The stream is routed through the Web Audio API. The tool creates an AudioContext, wraps the stream in a MediaStreamAudioSourceNode, applies the optional gain, and connects the source to an AnalyserNode. The AnalyserNode periodically samples the audio and exposes it as arrays of numbers — the time domain data (used for the waveform) and the frequency data (used for the spectrum).
  4. The numbers are drawn on canvases at 30 fps. Every animation frame, the tool reads the latest arrays and redraws the waveform, the spectrum, the level history, the VU meter, and the stats.

Recording works slightly differently. When you click Record, the tool sets up a ScriptProcessorNode that runs every 4,096 samples and pushes each chunk of raw PCM samples into an array. When you click Stop, all the chunks are concatenated into one buffer, encoded into a standard 16-bit mono WAV file, and stored as a blob in memory. When you click Play, the browser plays that blob; when you click Download, the browser saves it as a .wav file. Nothing is uploaded at any point.

When to use a mic test

  • Before job interviews and remote meetings — verify the mic works and the level is right.
  • Before going live on Twitch, YouTube, TikTok, or Instagram — catch problems before the audience does.
  • Before recording a podcast or voiceover — check the noise floor and level consistency.
  • When setting up a new mic or headset — confirm the driver installed correctly.
  • When troubleshooting “my mic isn't working” — the tool tells you whether the problem is permission, device, gain, or hardware.
  • When switching between operating systems — Windows, macOS, Linux, iOS, and Android all have different microphone menus.
  • When preparing a customer support call — silence, echo, and clipping make calls much harder than they need to be.
  • When testing audio hardware before returning it — a quick check confirms whether a new mic is faulty or misconfigured.
  • When recording lectures or online courses — good microphone quality is the single biggest determinant of perceived production value.
  • When running online exams or proctored tests — many platforms require a working mic.

The most common microphone problems and their fixes

  • “My mic isn't working at all.” Almost always a permission problem. Check the browser prompt, then the OS permission, then the hardware mute.
  • “The meter barely moves.” The mic is too quiet. Raise gain in the OS or use the tool's software gain slider, move closer, or check that the correct device is selected.
  • “I sound distant / hollow.” The mic is picking up room reflections. Move closer (10–15 cm) or add soft furnishings, a blanket, or acoustic foam behind the mic.
  • “I sound muffled.” Usually a low-quality mic or aggressive noise suppression. Try disabling noise suppression and see if the clarity returns.
  • “There's a constant hum.” Likely electrical — a ground loop, a bad USB port, or a laptop power supply. Try running on battery or using a different USB port or a USB isolator.
  • “My mic works in some apps but not others.” Different apps request different formats, especially the sample rate. Set everything to 48 kHz in the OS and try again.
  • “My Bluetooth headset sounds terrible on calls.” Bluetooth mics use a low-bandwidth voice profile. This is normal and cannot be fixed without switching to a wired mic or a USB dongle.
  • “My voice clips in recordings but sounds fine live.” Live monitoring hides clipping. Trust the CLIP indicator and lower your gain.
  • “I get echo on Zoom / Teams / Meet.” Echo cancellation is not working on the far end or your end. Check that echo cancellation is enabled in the conferencing app, use a headset, or reduce your speaker volume.
  • “The pitch reading jumps around.” This is normal for speech — pitch varies constantly. Try sustaining a single vowel (“aaaaah”) to get a stable reading.

Privacy and how this tool handles your audio

Everything on this page runs on your device. When you grant microphone access, the browser hands the raw audio only to this page's JavaScript. The audio is analysed in memory, visualised on canvas, and (if you record) stored as a blob in your browser's RAM. It is never transmitted anywhere — not to AIToolsPros, not to a third-party analytics service, and not to any server of any kind.

When you click Download, the browser saves the WAV file directly to your Downloads folder. Nothing else happens. When you close or refresh the tab, any recorded audio still in memory is discarded by the browser automatically.

Limitations of browser-based mic testing

  • Browsers can only test microphones that the operating system exposes. If the OS does not see the mic, the browser cannot either.
  • The test checks the current configuration, not the maximum capability of the hardware. An expensive studio mic and a cheap headset may both reach −20 dBFS at speaking distance — but the studio mic will have a much lower noise floor and better frequency response, which shows up best in a quiet recording.
  • This page does not infer microphone input latency by adding unrelated browser audio latency values. Input latency is shown only if the capture track explicitly reports it; this is not a round-trip latency measurement.
  • The tool cannot distinguish between a broken microphone and a broken cable, port, adapter, or driver. If the mic works in one context and not another, the fault is likely outside the mic.
  • Browser echo cancellation, noise suppression, and auto gain control can slightly change what the analyser sees. For raw signal measurements, disable them in the OS before testing.
  • Sample rate and channel count are chosen by the OS or the browser, not by this tool. Some operating systems lock the sample rate to a system default.
  • The pitch detector works well for voice, musical tones, and single instruments, but is less accurate for noisy polyphonic signals (a full band playing at once). It is a diagnostic tool, not a tuner.

Frequently asked questions

What is a microphone test?

A browser-based tool that captures a short audio sample from your microphone, visualises it in real time, and lets you play it back. It confirms the mic is working, the right device is selected, and the level is good enough for calls, streaming, or recording.

Is my audio sent to a server?

No. Everything runs inside your browser using getUserMedia and the Web Audio API. Your audio is analysed locally, visualised on canvas, and (if you record) stored only in your browser's memory until you download or close the tab. Nothing is uploaded.

Why can't my browser access my microphone?

Almost always a blocked permission. Check the lock or camera icon in the address bar and set Microphone to “Allow”. On macOS also check System Settings → Privacy & Security → Microphone. On Windows check Settings → Privacy → Microphone. Then reload and try again.

The meter isn't moving — what should I check first?

(1) Permission granted (browser and OS). (2) Correct device selected. (3) Hardware mute switch off. (4) operating-system microphone input level turned up, or the tool's software gain slider increased. (5) Mic is the right way up and you are speaking into the correct side.

Why is my microphone volume too low?

Use the software gain slider inside this tool first — it is a fast fix for quiet headset mics. Then move closer, raise the operating-system microphone input level, disable Auto Gain Control if it is not helping, and check for a physical gain or mute knob on the mic body.

What is dBFS and why are the numbers negative?

dBFS = decibels relative to full scale. Digital audio cannot go above 0 dBFS without clipping, so real sounds are always below it and shown as negative numbers. Normal speech peaks around −12 to −6 dBFS; silence is below −60 dBFS.

What is the difference between peak and RMS level?

Peak is the loudest single sample in the frame — it tells you how close you are to clipping. RMS is the average power over the frame — it corresponds to perceived loudness. Both should sit in the target range with the peak at least 6 dB above the RMS.

What is echo cancellation, noise suppression, and auto gain control?

Real-time filters applied to your mic signal. Echo cancellation removes speaker output from the mic (prevents feedback in calls). Noise suppression attenuates steady background noise. Auto gain control adjusts the input level up or down to keep speech in a comfortable range. The stats panel shows whether each is on for your current device.

Why does my recording sound different from my own voice?

You normally hear your voice through both air and bone conduction, which adds low frequencies that no microphone captures. This is normal and not a fault. Differences in noise suppression and mic placement also change the sound.

How do I test a specific microphone instead of the default?

Click Enable first so the browser can read device labels, then choose the mic from the dropdown. On Windows and macOS you can also set the default input in Sound settings.

Does this test also check my speakers?

No — this tool tests the microphone only. Use a separate speaker or headphone test to check the output side. The Play button on this page plays back your own recording, which is a quick speaker test in itself.

Can I record and download the test?

Yes. Click Record, speak for 5–10 seconds, click Stop, then Download WAV. The file is a standard uncompressed 16-bit mono WAV that opens in any audio editor.

Why does the browser ask for permission every time?

Browsers deliberately re-ask unless you tell them to remember. Use the site-settings menu (lock icon in the address bar) to permanently allow microphone access for this domain.

Does this work on mobile phones?

Yes — on iOS Safari, Android Chrome, Samsung Internet, and most modern mobile browsers. The front mic is used by default; Bluetooth headsets usually work but may need the Headset profile to be selected.

Does the tool work offline?

The mic test itself runs entirely on your device once the page has loaded. Losing internet mid-test does not affect the meter, waveform, or recording. Reloading the page does require a fresh load of the HTML, CSS, and JavaScript.

What sample rate and channels should I expect?

48,000 Hz is standard for voice and video. 44,100 Hz is common for music. Mono (1 channel) is standard for headsets and laptops; stereo (2 channels) appears on some USB mics and audio interfaces. All four combinations are legitimate.

What is latency and does it matter?

Latency is the delay between the sound arriving at the mic and being delivered to the app. High latency causes echo in calls and makes recording music impractical. Browsers do not consistently expose microphone input latency, so this tool shows a value only when the capture track reports one.

Why does my recording crackle or sound staticky?

Usually one of four things: gain turned too high and amplifying the pre-amp's own noise, a faulty USB cable or port, a sample-rate mismatch between the OS and app, or wireless interference on Bluetooth. Try a different port, cable, and sample rate, and lower the gain.

Can I test the mic during a meeting?

Most operating systems allow only one app to hold the mic at a time. If Zoom, Teams, Meet, or Discord is open, this tool may not get access. Close or mute the other app first.

Do I need to install anything?

No. This is a single HTML page. No extension, no plugin, no installer, no account. Everything is built into your browser.

What browsers are supported?

Chrome 60+, Firefox 60+, Edge 79+, Safari 14.1+, Opera 47+, Samsung Internet 8+, and modern mobile browsers. Internet Explorer is not supported.

Does the tool save my recordings?

No. Recordings live in your browser's memory until you download or close the tab. Nothing is written to disk by the tool, and nothing is uploaded.

Sources & methodology

Scroll to Top