How to Test Webcam on Teams Web Version Versus Desktop Application

Understanding this distinction is genuinely useful for isolating a problem quickly: if the camera works in Teams Web (accessed at teams.microsoft.com in your regular browser) but fails specifically in the desktop app, the issue almost certainly sits in the desktop app's own OS-level permission or local configuration, not in your camera hardware itself — since the browser-level test already confirmed the hardware and driver are fundamentally healthy.

The reverse pattern is equally informative: if the desktop app works fine but Teams Web doesn't, that points toward your browser's own site-specific permission for teams.microsoft.com specifically, completely independent of whatever permission the desktop app already has configured.

Both versions ultimately access the same underlying camera hardware, but through entirely different code paths and permission systems — Teams Web through your browser's standard WebRTC implementation, and the desktop app through Microsoft's own native media capture code integrated directly into the application.

Step 1: Test in Teams Web first

At teams.microsoft.com in your regular browser, to check whether the camera works through the standard browser permission path.

Step 2: Test the desktop app separately

Checking its own device settings and OS-level desktop app permission.

Step 3: Compare the two results.

If one works and the other doesn't, focus your troubleshooting specifically on whichever one failed, using the diagnosis above to know which permission system to check.

Step 4: If both fail identically, the cause is more likely at the camera hardware or driver level

Since it's affecting both independent code paths equally. ↑ Confirm with the widget above as a third, independent data point.

How do I reset the Windows Camera app itself?

Go to Settings → Apps → Installed apps, find Camera, open its three-dot menu, and choose Advanced options → Reset. This clears the built-in Camera app’s own cache and settings without uninstalling it, which can fix a stuck, frozen, or permanently black preview even when the underlying device and driver are both working correctly. It only resets that one app — not your camera driver, and not other applications that use the camera.

Could my antivirus be silently blocking my camera?

Many third-party security suites — Bitdefender, Kaspersky, Norton, and ESET among others — include their own webcam-protection feature that runs independently of Windows’ own privacy settings. That means Windows can show camera access as fully permitted while the antivirus software blocks it anyway, at a layer Windows has no visibility into. Check the antivirus program’s own settings, usually under a Privacy, Webcam Protection, or similarly named section, and confirm your browser or conferencing app is on its allow-list.

How do I re-enable my camera in Device Manager if it's disabled?

Right-click the Start button → Device Manager, expand Cameras or Imaging devices, and look for a greyed-out icon or a small down-arrow badge. Right-click that entry and choose Enable device. This is a different action from updating a driver — a disabled device won’t respond to any other fix until it’s explicitly re-enabled here first, so it’s worth checking before assuming the problem is a driver or a permission.

Is Windows' own camera privacy toggle blocking access, separately from anything else?

Windows keeps a system-level camera permission at Settings → Privacy & security → Camera, completely separate from Device Manager, the Camera app, and any antivirus software. This one screen has a master Camera access switch plus a per-app list beneath it — both need to be on. It’s worth checking directly, since a camera can show as fully enabled and working in Device Manager while this toggle silently blocks every app from reaching it.