Skip to main content
appkiro.com

Test Your Microphone Online

Choose an input device, speak normally and check what the browser receives. Use delayed replay, waveform, spectrum and level readings to spot silence, background noise or clipping.

Microphone access is requested only after you start the test. Render any local-only or no-recording claim only after confirming the implementation.

Microphone access

State exactly what the source code does. If audio frames remain in memory and are neither recorded nor sent to a server, say so. If analytics, diagnostics, recording or remote processing touches microphone data, disclose that instead. Stopping the test should release the media tracks.

Live audio view

Waveform
Frequency spectrum
Input level-∞ dB

Input Level

-∞dBFS

Peak

-∞dBFS

Noise floor

-100dBFS

Replay delay

1.0s

Replay controls

s
Use headphones or lower speaker volume to avoid acoustic feedback.

How can I tell whether my microphone is working?

Select the intended input, allow access and speak at your normal distance. A moving level meter confirms that a signal is arriving; delayed replay lets you hear noise, distortion, dropouts and the wrong device before using another app.

What the tester checks

Device selection

Confirm that the browser is listening to the headset, USB microphone or built-in input you actually intend to use.

Live signal views

Waveform, spectrum and meter views show different aspects of level and frequency content without replacing a proper calibration tool.

Delayed replay

Hear the captured signal after a short delay so the microphone is less likely to feed directly back into the speakers.

Running indicators

Average level, peak, background noise, detected speech and clipping help identify obvious setup problems.

When to test a microphone

  • Before a video meeting, interview or online class.
  • Before recording a podcast, voice-over or screen tutorial.
  • After changing the operating-system input device or connecting a new headset.
  • When callers report low volume, noise, distortion or intermittent sound.
  • When checking whether echo cancellation or another browser constraint changes the signal.

How to run the microphone test

  1. Choose the input

    Select the exact microphone you plan to use. Device names may appear only after permission is granted.

  2. Grant access

    Allow microphone access for this site. The test cannot start while permission is blocked.

  3. Speak normally

    Use your normal speaking distance and volume rather than shouting into the capsule.

  4. Listen and inspect

    Use headphones for replay, then check noise, peak level, clipping and whether speech is detected consistently.

  5. Fix the source, then retest

    Adjust input gain, placement, cable, mute state or room noise and repeat the same test conditions.

Understanding the measurements

Input level and dBFS

dBFS is measured relative to the digital maximum: 0 dBFS is the ceiling, while normal signals are negative. Do not publish universal “ideal” numbers without a documented measurement method.

Peak and clipping

Peak shows the loudest recent sample or frame. Repeated clipping means the input is reaching or exceeding the digital ceiling and should be reduced at the source.

Noise floor

Noise floor estimates the level present when you are not speaking. Fans, air conditioning, electrical hum and high microphone gain can raise it.

Replay delay and monitor volume

Delay controls how long the browser waits before playing the input back. Monitoring can create feedback, so headphones are the safest default.

Waveform, spectrum and meter

Waveform shows level over time, spectrum shows frequency energy, and the meter is the quickest way to check whether the signal is too low or too hot.

Permission and data handling

State exactly what the source code does. If audio frames remain in memory and are neither recorded nor sent to a server, say so. If analytics, diagnostics, recording or remote processing touches microphone data, disclose that instead. Stopping the test should release the media tracks.

What this test cannot prove

  • It cannot guarantee how a separate meeting or recording app will process the microphone.
  • Browser echo cancellation, noise suppression and automatic gain control can alter the signal.
  • Displayed levels depend on the implementation and are not a substitute for calibrated acoustic measurements.
  • Speaker replay can cause feedback and does not accurately represent headphone or remote-call quality.

Practical setup tips

  • Test from the same distance and room you will use later.
  • Keep the microphone slightly off-axis to reduce breath pops.
  • Lower hardware or system gain before relying on software normalization.
  • Compare with and without browser processing only when the UI exposes those constraints.

Common microphone problems

The meter does not move

Check the selected device, hardware mute, operating-system input level and browser permission. Another app may also have exclusive access.

The replay is delayed or choppy

Some delay is intentional. Heavy tabs, Bluetooth devices and high system load can add latency or dropouts.

The signal sounds distorted

Reduce microphone gain, move farther away and verify that clipping falls to zero. Digital clipping cannot be repaired by turning playback volume down.

There is a loud squeal

That is acoustic feedback. Stop monitoring, use headphones or reduce speaker volume immediately.

Microphone test FAQ

Does the microphone tester record my voice?

Only claim “no recording” if the implementation never writes or persists microphone audio. A live test can still read audio frames in memory to display levels and replay the signal.

Why can I not select my microphone?

Browsers often hide device labels until permission is granted. Allow access, then reopen the device list.

Why is there no sound in replay?

Check Monitor, replay volume, mute state and the output device. Use headphones and verify that the page is not blocked from autoplay.

What does clipping mean?

Clipping means the input reached the digital ceiling and the waveform was cut off. Lower gain or increase the distance from the microphone.

What is a good microphone level?

There is no single number for every microphone and workflow. Aim for clear speech with headroom, no clipping and a stable gap above the room noise, then follow the target of the app you will use.

Why does the browser test sound different from a meeting app?

Other apps may apply their own noise suppression, gain control, codec and network processing. Use this page to validate the input path, not to predict every downstream effect.

Can I test a Bluetooth headset?

Yes when the browser and operating system expose it as an input device. Bluetooth profiles can reduce quality or add latency.

How do I stop microphone access?

Stop the test and confirm the browser’s recording indicator turns off. The implementation should stop every active media track when the page or test closes.