Skip to main content
I/O Checkup
System ready
Active lab / 06Microphone LabMic input, gain, noise, frequency, and channel checks.

Mic Test

Microphone tools use local Web Audio analysis. Audio is not uploaded.

Idle0Input Level
Peak0%
ChannelsUnavailable
Digital levelNot measured

Microphone Test: Mic Permission, Live Input Level, Peak Signal, And Local Browser Audio Check

Check microphone permission, input level, peak signal, and detected audio source.

What this test checks

  • Browser microphone access
  • Input level and signal stability
  • Noise, channel, or frequency behavior
  • Watch Live Level And Peak Signal

How to read the result

Mic Test reads local Web Audio signals. Compare quiet-room noise, normal speech, and peak levels; clipping, channel imbalance, or a high noise floor can come from gain settings, the room, or the selected input device.

Grant Microphone Permission

The browser asks for microphone access before the test can read audio input. The tool is local-first, so users can check mic status without uploading recordings.

Mic Access
Start Mic
Local Only

Speak Into The Selected Microphone

A normal speaking voice should produce a visible level response. This confirms the mic is connected, selected, and not muted by the operating system or browser.

Speak NormallyMic

Watch Live Level And Peak Signal

The display helps users see quiet, normal, and clipping levels. It is useful for headset microphones, laptop microphones, USB mics, and external audio interfaces.

Input LevelLive
PermissionLive

Stop The Stream After Testing

Stopping the mic closes the active browser stream. Users can then switch devices, change input gain, or retest after adjusting operating system sound settings.

Mic Working
Stop
Retest

What does Mic Test measure?

Check microphone permission, input level, peak signal, and detected audio source.

Do I need to install anything for Mic Test?

No. Mic Test runs directly in a modern browser. Some checks may ask for permission when they need camera, microphone, gamepad, pointer lock, touch, or audio output access.

Are results uploaded?

The test runs in your browser and uses local input events or browser hardware APIs for the visible diagnostics.

Why should I run related tests too?

Related tools help separate hardware issues from browser timing, display behavior, input device settings, or permission problems, which makes the final diagnosis more useful.

Detailed Testing Guide

Audio-input symptom

This microphone page checks whether the selected input is present, clean, loud enough, and routed correctly.

Start with a baseline run before changing device settings. Record any repeated symptom so the next comparison is useful.

Signal evidence

Watch permission, live level, peaks, noise floor, frequency shape, channel balance, and clipping behavior.

Watch Browser microphone access, Input level and signal stability, Noise, channel, or frequency behavior, Watch Live Level And Peak Signal. These observations come from the browser; they do not reveal hidden firmware or factory calibration data.

Recording method

Choose the correct input, speak at normal distance, and measure quiet-room noise separately from voice.

Keep the test conditions stable. Changing browser, cable, port, lighting, surface, volume, grip, or selected device all at once makes the result harder to trust.

Result reading

Wrong device selection, headset mute, automatic gain, noise suppression, and room fans can distort the result.

A repeated pattern matters more than a single spike. When something looks wrong, confirm it with another pass and compare a related tool before deciding the device itself is defective.

Limits and next checks

Use microphone test, volume meter, noise meter, frequency analyzer, and channel check together.

For a closer comparison, try Microphone Test, Volume Meter, Noise Level Meter, Frequency Analyzer. Keep the same device and connection while you investigate the next symptom.