Conclusion: First check the video in the browser alone
Open the physical shutter and select the camera used for meetings in DevelopTools. After checking video, actual displayed resolution, estimated FPS, and framing, confirm the same device and permissions in the meeting app as well.
| order | What to Check | Points of judgment |
|---|---|---|
| 1 | connection | The camera to use is recognized by the OS |
| 2 | Permissions | Changes to displayed after permission is granted |
| 3 | selection | The active device is the meeting camera |
| 4 | Video | Check brightness, angle of view, and updates |
| 5 | Meeting app | Select the same device and permissions |
Narrow down the areas to check based on symptoms
Camera recognition by the OS, acquisition by the browser, display in the video element, and use by the target app are separate stages. A black screen or acquisition failure alone does not indicate a hardware failure.
| Symptoms observed | Main points to check | Next action |
|---|---|---|
| Acquisition failed due to waiting for permission | Site permissions, OS permissions, HTTPS, management policies | Check the address bar and OS camera settings |
| The target camera is not in the list. | Enumeration restrictions before permissions, USB connectivity, disabling, drivers | Re-enumerate after permission and compare with OS recognition |
| Displayed but black/static | Physical shutter, other apps, lighting, drivers | Check other apps and compare on different browsers and devices |
| Displayed in DevelopTools | Web conference/web application side selection, authority, background processing | Select the same camera within the target service |
| Image quality and FPS are different than expected | Ideal constraints, bandwidth, lighting, USB, camera capabilities | Compare the required value and displayed value separately under the same conditions. |
Even if the video is displayed with DevelopTools, we do not guarantee that it will work in Zoom, Google Meet, Microsoft Teams, etc. Each service has its own camera selection, permissions, background effects, and bandwidth requirements.
Priority cause for this symptom
- The physical shutter is already closed before the meeting
- The built-in and USB camera selections are mixed up.
- Site permissions differ between DevelopTools and meeting services
- A meeting application's background effect or virtual camera is selected
- Another app or tab is using the camera
If video appears in DevelopTools, that indicates video from the selected camera is reaching the current browser. It does not guarantee that the meeting app works correctly, that the network works, or that the other party can view it.
If necessary, save a PNG snapshot or short WebM to your device to check the framing. If third parties appear, consider consent and the save location; if unnecessary, do not use the save feature.
Setting names and screen configurations may change depending on OS/browser updates, devices, and organization management policies. If it doesn't exactly match the article, look for Camera, Site settings, Privacy & Security, etc.
Scope and limitations that can be checked with webcam testing
| Item | What you can check with current tools | something that cannot be determined |
|---|---|---|
| Video confirmation | Display preview of selected camera in video element | Does not automatically determine camera failure just because no image appears |
| device | Select from the videoinput list and display the label of the track in use | Before permissions, labels and non-default cameras may be restricted. |
| Resolution | Automatically requests 640×480, 1280×720, 1920×1080 and displays videoWidth×videoHeight | There is no guarantee that the requested value and actual displayed value match. |
| FPS | Displays estimated FPS by counting drawn frames approximately every second | It is not the frameRate or camera specification value of MediaTrackSettings itself. |
| inversion | Flip the preview horizontally and vertically and reflect it on the PNG snapshot | WebM recording records the original stream, so CSS reversal is not burned in. |
| Save | You can save PNG snapshots and WebM recordings of up to 5 minutes to your device. | Does not support in-page playback, arbitrary format conversion, or server storage |
| end | Stop MediaStreamTrack on stop and page exit | It does not control the use of cameras maintained by the OS or other applications. |
The selected resolution value is an ideal constraint and may not necessarily match the value actually adopted by the camera and browser. The screen resolution field is videoWidth and videoHeight of the video element. Estimated FPS is also a guideline that counts the drawing frames, and is not the actual track setting value or product specification value.
Snapshots are saved as PNG, and recordings are saved as WebM on the device. The maximum recording time is 5 minutes. Horizontal and vertical flips are reflected in preview and PNG, but there is no process to burn the flips into the source stream recorded by MediaRecorder.
Proceed with confirmation and correction in order
- 1. Connect the camera used for the meeting and open its shutter.
- 2. Allow access in DevelopTools and select the target camera.
- 3. Check video, field of view, brightness, resolution, and estimated FPS.
- 4. Save a snapshot or short recording only when needed.
- 5. Select the same camera in the meeting app and recheck the preview.
Changing multiple settings at the same time can make it difficult to determine the cause. Please change one item at a time and retest with the same camera, lighting, USB port, and browser.
Check the current specifications with official information
Permission UI, OS setting names, and Web API support will be updated. It is based on the following primary information and does not assume old screen procedures or fixed camera capabilities.
| Confirmation destination | URL | What you will see in this article |
|---|---|---|
| Google Chrome Help「Use your camera and microphone in Chrome」 | https://support.google.com/chrome/answer/2693767 | Camera permissions by site, default camera, managed browsers |
| Mozilla Support「How to manage your camera and microphone permissions with Firefox」 | https://support.mozilla.org/kb/how-manage-your-camera-and-microphone-permissions | Camera permissions by site in Firefox |
| Apple Support「Customize settings for each website in Safari on Mac」 | https://support.apple.com/guide/safari/ibrw7f78f7fe/mac | Camera settings for each website in Safari |
| Microsoft Support「Camera does not work in Windows」 | https://support.microsoft.com/windows/hardware/camera/camera-doesn-t-work-in-windows | Checking Windows 11 Camera access, other apps, and drivers |
| Microsoft Support「Manage cameras with Camera settings in Windows 11」 | https://support.microsoft.com/windows/hardware/camera/manage-cameras-with-camera-settings-in-windows-11 | Connected cameras, disabled status, and camera-specific settings |
| Apple Support「Control access to the camera on Mac」 | https://support.apple.com/guide/mac-help/mchlf6d108da/mac | macOS Privacy & Security and Safari Camera permissions |
| Apple Support「If the built-in camera is not working on your Mac」 | https://support.apple.com/102437 | Software updates, Screen Time, permissions, restart |
| MDN「MediaDevices.getUserMedia()」 | https://developer.mozilla.org/docs/Web/API/MediaDevices/getUserMedia | Permissions, secure context, exceptions, iframes and Permissions Policy |
| MDN「MediaDevices.enumerateDevices()」 | https://developer.mozilla.org/docs/Web/API/MediaDevices/enumerateDevices | Restrictions on label/non-default device enumeration based on privileges |
| MDN「MediaTrackSettings」 | https://developer.mozilla.org/docs/Web/API/MediaTrackSettings | Actual settings for width, height, frameRate, facingMode, etc. |
Check again under the same conditions after making corrections
Reload the page after changing settings, and if necessary, stop and start the camera again. Compare the device in use, video, actual display resolution, and estimated FPS under the same conditions. Create PNG or WebM only if you need to save it.
| Reconfirmation items | Clues for improvement | Next division if remaining |
|---|---|---|
| Permissions | Change from waiting for permission to displaying | Check OS permissions, HTTPS, and management policies |
| device | Intended camera name is displayed on the device in use | Check connections, disables, drivers, and alternate ports |
| Video | Preview is updated continuously | Compare physical shutter, other apps, lighting, and different browsers |
| Target app | Images are displayed using the same camera | Check app selections, permissions, background effects, and restart |
After checking, press "Stop Camera". The tool will stop the retrieved MediaStreamTrack. Also make sure that the device's camera usage lamp and browser usage indicator disappear.
Example: Join a meeting with a USB camera
Select a USB camera from the list instead of the built-in camera, and confirm the active device name.
Even after it appears in DevelopTools, set the meeting app's input camera to the USB device.
- Connect a USB camera.
- Start the camera and select a device.
- Check the field of view and brightness.
- Select the same device in the meeting application as well.
A successful Web camera test alone does not prove that conference apps also work normally.
Frequently asked questions
- If it works in the test, will it definitely work in Zoom or Teams?
- No. Separately check permissions, device selection, background effects, and network settings on the meeting service side.
- Is video sent to a server?
- The Web camera tester does not send video or recorded data to servers or external APIs. It downloads to your device only when you choose to save.
Try It in Your Browser
Your input is processed entirely in your browser. Keep the original data, review the output, and only then save or share it.
Open webcam test