DeviceOK
SearchDevice checks
Home / Fixes / Wrong Camera Selected

camera · evidence-led troubleshooting

Wrong Camera Selected

Separate camera detection, permission, actual frames, resolution and frame stability when an app or browser is using a different camera than intended. The result should determine which troubleshooting layer comes next.

Reviewed 2026-08-116 diagnostic steps2 official sources
Run Webcam testSee fault tree ↓

What this symptom means

This symptom concerns the camera path. Start with a neutral DeviceOK test where available so the next step is based on evidence rather than a generic reset sequence.

Diagnostic principleTreat 'not detected', 'permission denied', 'black image', 'frozen image', low resolution and low frame rate as different failures. A single generic webcam fix path wastes time because each state points to a different layer.

Fault tree

Camera fault tree

Use the observation that best matches what you can reproduce. Do not treat every cause as equally likely.

1
Privacy shutter or permission

Evidence: The camera is listed but video is blocked or black immediately.

Next: Open the physical shutter, check browser permission, then OS camera privacy settings.

2
Another app owns the camera

Evidence: The camera works after closing Teams/Zoom/OBS or after rebooting.

Next: Close competing apps and retest before touching drivers.

3
Mode/bandwidth issue

Evidence: Video works at lower resolution/FPS but not at the requested mode.

Next: Reduce resolution/frame rate, connect directly, and remove hubs/capture chains.

4
Detection or hardware path

Evidence: No camera appears in DeviceOK or another trusted app.

Next: Check cable/USB port, OS recognition, official driver/firmware, then hardware.

Interpret the result

Evidence matrix

A test result is useful only if it changes the next troubleshooting branch.

ObservationWhat it supportsPrioritize next
Live preview worksA camera stream successfully reached the browser.Affected app settings, device selection, virtual camera, permissions or app contention.
Camera listed, preview blackEnumeration succeeded but usable frames are not reaching the preview.Shutter, source selection, capture source, app contention, privacy or camera pipeline.
Preview starts then freezesThe stream opened and then stopped updating.USB stability, bandwidth, driver/firmware, competing apps or power management.
No camera listedThe browser cannot enumerate a camera endpoint.Connection, OS recognition, privacy policy, disabled device or hardware.

Fast baseline

Rule out the simple causes first

  1. 1

    Run the DeviceOK webcam test and note whether the camera is detected, permitted, and producing live video.

  2. 2

    Confirm the intended camera is selected and any physical privacy shutter/switch is open.

  3. 3

    Close other apps that may be using the camera.

Full sequence

Work from reversible checks to invasive ones

Avoid destructive resets, unofficial driver packages, firmware flashing, or replacing hardware before the simpler detection, permission, connection and configuration checks are exhausted.

  1. 1

    Run the DeviceOK webcam test and note whether the camera is detected, permitted, and producing live video.

  2. 2

    Confirm the intended camera is selected and any physical privacy shutter/switch is open.

  3. 3

    Close other apps that may be using the camera.

  4. 4

    Check browser and operating-system camera permissions.

  5. 5

    Reconnect an external camera or try another USB port if applicable.

  6. 6

    If the camera fails in multiple trusted apps, follow the device manufacturer's official support/driver path.

Platform branches

Where the setting lives

Windows

  • Settings → Privacy & security → Camera
  • Open the Windows Camera app for an independent comparison
  • Use Device Manager only after checking privacy/shutter and external USB path

macOS

  • System Settings → Privacy & Security → Camera
  • Quit apps that may be holding the camera
  • For external cameras, test a direct port/cable before a dock

Browser

  • Confirm the correct camera in site permissions
  • Reload after changing permission
  • Inspect active resolution/FPS separately from simple detection
If it works in DeviceOK

A stable browser preview proves usable camera frames are reaching this session. If the original symptom remains, keep the next checks above the hardware layer until evidence says otherwise.

If it also fails here

Failure in DeviceOK and the operating-system camera path makes app-only configuration less likely. Compare the simplest direct connection and official diagnostic path before replacement.

Escalation threshold

When software troubleshooting has stopped being high value

  • No image in DeviceOK and the OS camera app
  • Repeated disconnect/reconnect with a direct known-good port
  • Physical shutter/hinge/cable damage
  • OEM diagnostics or service tools identify a camera module fault
Changed one variable?After every meaningful change, repeat the same test under the same conditions and compare the result. Retest under the same condition so the result is comparable.
Retest Webcam test