Quick answer
What this guide helps you determine
Check your webcam, microphone and speakers before a video call, then verify the same devices in the meeting app with a printable preparation checklist.
Begin with the observable browser result, repeat it under the same conditions, and change one connection, setting or application at a time. A browser result narrows likely causes but does not certify hardware or decide a repair.
Scope of this check
A visible camera preview and a moving microphone meter are useful starting points, but neither proves that a remote participant will see and hear you. This checklist separates local equipment checks from meeting-app selection and the network path. Prepare in the room and connection mode you will use, with a non-private background and a short neutral sentence for microphone playback. Avoid changing many settings immediately before an important call.
Step-by-step method
- Connect the intended camera and headset before opening the meeting application. Charge wireless accessories, close unused camera previews and set a comfortable listening level. If possible, have a known-good wired headset available as a fallback. Record whether the setup uses a dock.
- Open Webcam Test and click Start when ready to grant access. Select the intended camera, check the preview and actual stream dimensions, and adjust framing and front-facing light. A preview of the wrong room or angle usually calls for a device-selection check. Stop the stream before moving to the next test.
- Open Microphone Test, select the intended input and speak a short phrase at normal distance. Watch the level change and use local playback if offered. A moving meter confirms input activity, while playback helps you notice muffling, clipping or the wrong microphone. Do not interpret the meter as a calibrated sound-pressure measurement.
- Use Speaker Test or Headphone Test at low volume. Play each channel deliberately and confirm the sound comes from the intended device rather than a monitor or laptop speaker. If the microphone playback is silent, verify output selection before concluding that the recording failed.
- Open the real meeting app or meeting website and select the same camera, microphone and output there. Browser permissions belong to individual sites, and an installed meeting app has its own device settings. Check physical mute, in-app mute and the preview again. On Windows, use the official microphone and camera privacy instructions linked below if the app cannot access a device.
- Use the meeting app's test-call feature if available, or arrange a short call with a willing participant. Check whether the other person receives sound and video. If local tests work but the call fails, investigate app permissions, selected devices, processing settings and connection quality. Close the device-test tabs and confirm media indicators stop when you finish.
What to check first
Use these checkpoints to keep the comparison focused. Record the visible behavior rather than assigning a fault label too early.
- Use the devices and room intended for the call
- Check input and output independently
- Finish in the actual meeting application
How to read what you see
| Observation | What it can suggest | Useful next check |
|---|---|---|
| Local microphone playback works; the meeting input meter does not move | The local input path worked, but the meeting may use another input or be muted. | Select the same device and check app-specific permission and mute controls. |
| Both previews work; only remote video is poor | The local camera check does not explain the whole call path. | Inspect the meeting's quality indicators and network conditions. |
| A camera permission error appears on the meeting website only | A permission granted to the tester does not grant access to another origin. | Review permission for the actual meeting site. |
| Your own voice returns after a delay | Another participant or a second local device may be playing the call into a microphone. | Use headphones and mute one extra call device at a time. |
Common mistakes to avoid
- Do not run speaker tones loudly beside an active call microphone.
- Do not leave a private recording or camera stream running after testing.
- Do not describe a local equipment check as a successful network or remote-call test.
Put the guide into practice
Keep this checklist beside the meeting app. You can return to one failed stage without repeating working stages. The last check is a real app or call check, so leave it Not tested if you only used local device tools.
When the browser succeeds but the meeting fails
Compare the selected device names in both places, then check permission and mute controls for the meeting itself. For a meeting website in Chrome, review Settings → Privacy and security → Site settings → Camera or Microphone for that site. A work or school administrator may control the choice. Do not change organization policy to bypass a restriction; ask the administrator which meeting setup is supported.
A practical fallback plan
Write down a backup input and output that you have actually checked. If your USB webcam fails, the built-in camera may be adequate; if speakers feed back, a compatible headset can separate playback from capture. Recheck the selected devices after switching. Do not assume that a meeting app follows a new system default while a call is already active.
Your inspection worksheet
Use Observed working, Needs follow-up or Not tested for each item. These labels describe this session, not a hardware certification.
Notes stay in this open page and are not submitted or saved by the site. Print or save as PDF before leaving or reloading. Test links open a separate tab so you can keep this worksheet open.
-
Connections and physical mute
Confirm intended accessories, sufficient charge and a comfortable listening level.
-
Camera preview
Check selection, framing and focus; stop the stream after the observation.
Open test (new tab) -
Microphone input
Check a normal spoken phrase and local playback if available.
Open test (new tab) -
Output and channels
Play left and right at low volume and confirm the intended output.
Open test (new tab) -
Meeting app selection and permission
Confirm the same devices in the actual app or meeting website.
-
Remote or app test call
Record what the remote participant or test-call service receives; otherwise leave Not tested.
-
Streams stopped and fallback ready
Close test streams and record the backup equipment you have verified.
Continue with a related check
Official setup and troubleshooting instructions
Use the platform or device manufacturer's current instructions when settings differ from this guide.
- Camera and microphone permissions in ChromeGoogle Chrome Help
- Fix microphone problems in WindowsMicrosoft Support
- Manage camera permissions in WindowsMicrosoft Support
Build evidence another person can use
Write down the exact action, visible result and whether it repeats. Include the browser family, operating-system family, connection type and the single comparison that changed the result. Quote the observation directly—for example, “Local microphone playback works; the meeting input meter does not move”—then add where it occurred and which comparison changed it.
Change one condition per comparison and return settings that have no effect. Follow model-specific manufacturer instructions before firmware changes, cleaning, disassembly or warranty action.
When to seek qualified support
If the same problem remains in multiple applications and on another compatible connection or computer, collect the repeatable observations and contact the manufacturer or a qualified technician. Stop using equipment that is physically damaged, unusually hot, wet, sparking or unsafe. Device Test Bench cannot inspect electrical condition or make a repair decision.
Privacy during testing
Our public tests process key events, pointer values, media streams and controller input locally. Do not send private recordings, complete typed text or device identifiers when asking for help. A short description of the behavior, browser and page URL is normally enough.
Questions readers ask
Why does the tester work while my meeting app does not?
The two applications can select different devices and have different permissions, mute states and processing. Compare those settings before changing the hardware.
Can I check call quality without another participant?
You can inspect local input, output and any test-call function the app provides. A remote participant test adds evidence about the full call path that a local preview cannot supply.
What should I do if there is no time to troubleshoot?
Use a previously verified fallback such as a compatible wired headset or another approved device. Tell the meeting organizer about remaining limitations instead of rushing through firmware or driver changes.
Primary technical references
The following specifications define the browser APIs discussed in this guide. They are primary web-platform references, not product repair manuals.