Mycelgrid

LISTEN · VERIFY · PLAY BACK

Microphone Test

Test your microphone online with a live input meter, waveform, input selection, and a short local playback sample.

Microphone permission starts only when you choose Start microphone test. Audio from this test is processed locally in your browser and is not uploaded by the app.

Input—
SignalNot running
Level— dBFS
RecordingIdle

Live microphone input

Speak normally. The meter and waveform reflect digital audio reaching this page.

INPUT LEVELNot requested
Device details

Ready. Start the microphone test when you want to grant access.

What this microphone test checks

The test verifies whether this browser can open a microphone input and receive digital audio from it. The live meter and waveform respond to samples delivered by the browser, while the local recording lets you hear a short version of what the browser received.

Live signal

Use the input meter and waveform to confirm that speech or sound is reaching the selected microphone.

Choose the right mic

After permission is granted, select another available microphone when the browser exposes multiple audio inputs.

Hear the sample

Record up to 10 seconds and play it back locally to check what the browser captured.

How to interpret the level

The displayed dBFS value is a digital full-scale level derived from the live audio samples. It is useful for seeing relative input strength, but it is not an environmental sound-pressure measurement in dB SPL and does not calibrate microphone sensitivity.

Practical check: normal speech should move the meter and draw a visible waveform. If the app reports clipping risk, reduce gain or move farther from the microphone. If it remains very quiet, check input gain, distance, and the selected device.

Why microphone names may appear only after permission

Browsers can limit device labels until microphone permission has been granted. The selector is therefore populated after the test starts, rather than pretending every input is identifiable before access.

What recording and playback can tell you

Playback can reveal obvious silence, distortion, excessive background noise, or the wrong selected input. It cannot certify studio quality, frequency response, speech intelligibility, acoustic treatment, or whether another application such as Zoom, Teams, Discord, or a game is configured to use the same device.

Browser-reported device details

When available, Device details shows settings the active browser track reports, such as sample rate, channel count, echo cancellation, noise suppression, and automatic gain control. These are browser/device observations and can differ across systems.

Privacy boundary

Microphone audio and the playback sample are handled by this app in the current page and are not uploaded by the Microphone Test. Mycelgrid's website-level services, including advertising when enabled, are separate from microphone audio and are covered by the Mycelgrid Privacy Policy.

Related device checks

Use Computer Keyboard Test for physical keys, Mouse Tester for buttons and scrolling, and Reaction Time Test for browser-observed visual response timing.

Why does the browser ask for microphone permission?

Web pages cannot open a microphone silently. A supported browser on HTTPS requires explicit permission before microphone audio can be delivered to this app.

Why do I see “No signal yet” after allowing access?

The microphone track is open, but the current samples are near digital silence. Speak closer to the microphone, confirm the selected input, and check operating-system input settings.

Does this test upload or save my recording?

No. The sample is held locally in page memory for playback. Clearing it, refreshing the page, or leaving the page can discard it.

Can this test measure real-world decibels?

No. Without calibrated hardware and a known acoustic reference, a browser microphone test cannot honestly report sound-pressure level in dB SPL.

Why can a microphone work here but not in another app?

Each application can have its own selected input, permission state, processing options, and operating-system routing. This test confirms what this browser page receives; it cannot inspect another application's settings.

Read the testing guide for permissions, digital level measurement, recording behavior, and browser limits.