Your test data stays in this browser.Security and Privacy
Device Test Bench

Observation → comparison → next step

Plan a Camera or Microphone Access Check

Work through browser permission, selected input and another application before treating a camera or microphone startup error as hardware failure.

Published 2026-10-01

Your working record stays in this page. No automatic device access, media capture or saved test history. Copy or print only if you choose.

Media startup crosses several boundaries: a secure page, browser permission for this origin, operating-system access, device selection and a live stream. A permission indicator checks only part of that path. A successful local preview also does not prove that a meeting application selected the same device. This plan records where access stops and keeps camera and microphone observations separate.

Before the comparison

Comparison 1 of 3

Record the access boundary

Open Browser Permission Checker on HTTPS. Read the state for the chosen input, then review this site in the browser site controls if necessary.

Why it matters. An unavailable permission query is not equivalent to denied access. Browser and operating-system controls can differ, and neither a granted state nor API availability guarantees an openable stream.

Open Browser Permission Checker (new tab)

All possible observations and next steps
ObservationWhat it suggestsUseful next step
The permission is denied or a site control blocks itThe browser access boundary needs an intentional decision.If you want the test, adjust only this site permission and start the chosen media test again.
Permission is granted or a prompt is availableThe permission boundary alone does not explain the final stream result.Deliberately start Webcam Test or Microphone Test and record the exact visible error if it fails.
The permission query is unsupportedThis browser cannot report that state through this query.Use the browser site controls and an intentional media start; do not label the device faulty.

Comparison 2 of 3

Confirm the selected input and live stream

Start the relevant test, select the intended input where available, and confirm moving video or a changing microphone level. Do not record private conversations.

Why it matters. A device name or selection is not proof of a live track. A static video or zero level can also reflect a shutter, mute control, competing application, input choice or processing setting.

Open Webcam Test (new tab)

All possible observations and next steps
ObservationWhat it suggestsUseful next step
The intended input provides a live signalThe local browser path worked under these conditions.Stop the test and verify the same input inside the actual meeting application.
The wrong input opensA stream exists, but it is not evidence about the intended input.Select the intended device and repeat before interpreting video quality or audio level.
No stream starts or the signal remains absentRecord the exact error or absent signal; the cause is still unresolved.Check operating-system access, the physical control and competing applications one at a time.

Comparison 3 of 3

Compare another application

Stop every local stream, then try the selected input in another trusted application or the intended call app. Keep the same connection and physical controls.

Why it matters. An application-specific failure is a different support case from access failing across applications. Repeated failures still require a model-specific check rather than an invented hardware diagnosis.

Open Microphone Test (new tab)

All possible observations and next steps
ObservationWhat it suggestsUseful next step
It works here but fails in the meeting appThe two application paths differ.Check meeting-app input selection, permissions and audio/video processing settings.
It fails in both applicationsThe issue extends beyond this site.For external media, compare a direct port; consult operating-system or manufacturer guidance with the recorded error.
The comparison was skippedThe meeting-app path has not been verified.Keep that uncertainty in the record and avoid describing the equipment as ready for the call.

Your private comparison record

Use a general device description, not a serial number or private recording. Do not enter passwords, complete typed messages or sensitive personal information. Leaving or reloading this page can discard the record; the site does not save it.

How to describe evidence

Illustrative example, not a measured case report. The camera previews here after permission, but the meeting app displays a different camera.

Useful conclusion. Local capture works for the selected input. The next comparison concerns meeting-app device selection, not sensor repair.

Stop conditions and limits

Do not disable security protections globally to make a test work. On managed equipment, follow the organization permission policy and ask its administrator for approved access.

This workflow cannot certify hardware, decide warranty eligibility or replace model-specific inspection. It does not request camera, microphone or controller access. Dedicated tests require separate deliberate actions.

Primary and official references

These sources document browser behavior or platform troubleshooting. Our comparison sequence is an editorial workflow, not a manufacturer-approved repair procedure.

Questions about this comparison

Does granted permission mean the camera is working?

No. It describes an access decision, not a successfully opened stream or a selected input in another application.

Can I finish without granting media access?

Yes. You can read the complete workflow and record media steps as not tested. No media access is requested by the planner itself.

Read the detailed explanation

  • Video Call Equipment Checklist — Check your webcam, microphone and speakers before a video call, then verify the same devices in the meeting app with a printable preparation checklist.
  • USB Hub and Dock Troubleshooting — Compare direct and docked connections to investigate missing devices, webcam dropouts and audio interruptions without guessing which component failed.

Choose another problem · Report a correction

Search