How to Test WebRTC Audio

A WebRTC audio test checks whether a browser can capture sound from an input device, such as a microphone, and play sound through an output device, such as headphones or speakers. The test usually runs on the local device, with the browser using its WebRTC media APIs. Some test pages may also connect briefly to a remote service for call simulation, but basic input and output checks do not require that.

Before you start

Use a current desktop or mobile browser with WebRTC support, such as a recent version of Chrome, Edge, Firefox, or Safari. Connect the microphone or headset you want to test before opening the test page. If the device has a physical mute switch, make sure it is not muted.

Set the intended microphone as the system default input device and the intended speakers or headphones as the default output device. This reduces the chance of the browser choosing another device automatically. Close other apps that may be using the microphone so they do not hold the device or affect the input level.

Step-by-step instructions

• Open the WebRTC audio test page in the browser.
• Allow microphone access when the browser shows the permission prompt.
• Select the microphone you want to test if the page offers an input device list.
• Speak at a normal volume and watch the input level indicator.
• Start playback or monitoring and listen on the selected output device.
• Stop the test when you have confirmed the signal.

The exact labels differ by browser and test tool. Some tests show a live microphone meter and a play button for a short echo or audio loop. Others include a call-style test with separate input and output sections. In a browser, device access can be changed from the site permission settings if you denied access by mistake.

Check the output

A working microphone should produce visible movement in the input level meter when you speak or tap near the microphone. Speech should sound clear through the output device without severe delay, distortion, or constant background noise. Some level of room tone or fan noise is normal, but a strong continuous hum or hiss may point to a gain, connection, or grounding issue.

Browser audio is often delivered at a sample rate chosen by the browser and operating system, such as 44.1 kHz or 48 kHz. You do not need to match a specific sample rate for a basic test. If the test page reports a rate, the reported value should be read as diagnostic information rather than a quality guarantee.

Common problems and next steps

If there is no microphone movement after allowing access, return to the test page permission settings and confirm that the microphone is allowed and the correct input device is selected. Check the operating system sound settings to verify that the device is enabled and not muted.

If you hear no sound during monitoring, confirm the correct output device is selected in the test page and in the operating system. Check the volume, mute state, and cable or Bluetooth connection. If the browser appears to have the wrong device, close the page, set the desired device as the system default, and reopen the test.

If the audio sounds choppy or delayed, close other tabs and applications that use audio, and move closer to the microphone. On a wireless headset, reduce distance or sources of interference. After changing any input or output device, repeat the test from the start to confirm the new configuration.