Quick answer
What this guide helps you determine
Select among built-in, USB and virtual cameras after permission exposes their labels.
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
Computers often expose a built-in camera, USB camera, dock camera and one or more virtual cameras. Before permission, browsers may hide identifying labels; after permission, selection should be confirmed by both the label and the live viewpoint.
Step-by-step method
- Connect only the cameras needed for the comparison, click Start and allow access for this site. Open the device selector after labels become available and choose one entry at a time.
- Verify the viewpoint by covering only the intended lens briefly with a hand—without touching it—and by checking framing and active dimensions. Similar labels can refer to different physical or virtual inputs.
- Stop the browser preview before opening another application. Select the same named device there and disable virtual-camera software if it replaces the physical feed unexpectedly.
What to check first
Use these checkpoints to keep the comparison focused. Record the visible behavior rather than assigning a fault label too early.
- Grant permission only when ready
- Use the in-page device selector
- Verify the preview before stopping the stream
How to read what you see
| Observation | What it can suggest | Useful next check |
|---|---|---|
| Changing the selector changes the viewpoint | Multiple camera inputs are available and selection works. | Choose the intended device and remember the label. |
| A virtual logo or generated scene appears | A virtual-camera application is selected. | Switch to the physical camera or close the virtual software. |
| The chosen camera is busy in another app | The driver may not support simultaneous clients. | Stop all other previews before retesting. |
Common mistakes to avoid
- Do not publish screenshots containing all device labels.
- Do not unplug an active camera during a recording or call.
- Do not assume the first list item is always the built-in camera.
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, “Changing the selector changes the viewpoint”—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 are devices called Camera 1 and Camera 2?
Browsers can conceal identifying labels until permission is granted to reduce fingerprinting and privacy risk.
Will my browser choice become the meeting app choice?
Not necessarily. Each application maintains its own selected input.
Primary technical references
The following specifications define the browser APIs discussed in this guide. They are primary web-platform references, not product repair manuals.