Before your meeting
Check your camera, microphone, short voice playback, and current speaker path in one browser flow before a meeting.
Reading local check sessions…
Browser evidence, then platform confirmation
Choose the intended camera and microphone, inspect the preview, speak while watching the input response, record and replay a short local sample, play the speaker sound, and then confirm the same devices inside the meeting app you will actually use.
A pre-call task is easier when the camera preview and microphone response stay together. You can switch either input, compare the browser-reported settings, hear a short voice sample, and keep your observations in the same local session instead of moving between separate pages.
It can show whether the current browser receives camera frames and microphone input, which input devices the browser reports, whether it can start a bounded test sound, and what you personally observe in the preview and playback.
It does not join Zoom, Google Meet, Microsoft Teams, Webex, or a peer-to-peer call. It cannot verify the app's final routing, a remote participant's audio, echo cancellation in a real call, organization policy, packet loss, jitter, codec behavior, or general network readiness.
Check the camera, microphone, and speaker selected inside the app; review browser and operating-system permissions; close another app that may hold the camera; reconnect Bluetooth audio; and use the platform's official pre-join or test-call flow. Reload or restart only when the device path remains stuck.
Start this check, select the intended camera and microphone, inspect the live preview, and speak while watching the input meter and waveform. Record what you observe, then confirm the same devices in the actual meeting app.
Yes. This page requests both only after you select Start, shows the live camera preview and microphone response together, and keeps raw media in the current browser tab rather than uploading it.
Lower system volume, play the short speaker test, and record whether you heard it clearly and through the intended output. The browser may use the operating system's current output and cannot guarantee that a meeting app chose the same device.
Where MediaRecorder is available, you can create a short sample and play it back locally. The audio stays in page memory, is not uploaded, and is not stored in the diagnostic report.
It checks the browser-visible device path used for this page, not those platforms. Before joining, open the real app or official pre-join flow and confirm that it selected the same camera, microphone, and output.
No. This page does not establish a real meeting or WebRTC session with those platforms, so it does not turn generic browser connectivity into a packet-loss, jitter, bandwidth, or call-quality verdict.
No. Preview and microphone analysis are local to this tab. An optional short voice sample exists only in page memory and is discarded when replaced or when the page closes; only your selected observation and note can enter the local report.