Know what will work before the meeting starts.

Measure the browser, microphone, and camera; confirm speaker output; then get an evidence-based Ready or Needs attention result with a local PDF report.

Pre-call readiness report

Not started
One guided run, four evidence groups.

MeterSee measures the browser, microphone, and camera. Speaker output still requires one honest listening confirmation.

  1. Allow microphone access
  2. Stay quiet for 1 second
  3. Speak normally for 2 seconds
  4. Allow or skip unavailable camera
  5. Confirm the speaker tone
Diagnostic result

Not started

Start the guided check to create a local, evidence-based readiness report.

Audio and video are sampled locally and stopped after measurement. Device labels may be withheld by the browser. “Ready” means ready for browser-based calls under the measured conditions; it is not a hardware certification or proof of a desktop app's selected settings.

Use evidence, not a generic green check.

MeterSee separates browser-observed measurements from manual listening and visual confirmation, and preserves unavailable values instead of inventing them.

Observed signalLikely layerNext check
Microphone warningLow level, clipping, or elevated background noise

Select the tested input in the meeting app, adjust input gain, and repeat in the same room.

Camera failedPermission, missing device, busy device, or browser capture failure

Close competing apps, verify system and browser permission, then run the dedicated webcam preview.

Speaker not confirmedOutput cannot be heard by browser software

Play the confirmation tone and verify the same output device in Zoom, Teams, or Meet.