Teams video not working during a call — your camera shows a black screen to others, the camera selector in Teams shows “no camera,” or video starts then freezes — is one of those issues where the cause is usually straightforward once you know where to look. You’ll find the complete rundown in our Complete Guide to Fixing Windows, Browser, and Software Errors.
The most important first check: can anyone else in the meeting see you? Join a test meeting or video call. If others see a black screen: Teams has camera access but the feed is broken. If they see “camera unavailable” or you’re not visible at all: Teams doesn’t have camera access. Each points to a different fix.
Start here: the Teams video test
Before a real meeting: Teams Settings → Devices → Camera section has a preview. If the preview shows a live camera image: hardware and permissions are working correctly — the problem is configuration inside Teams or during calls. If the preview is black or blank: something upstream is broken.
Also open the Windows Camera app (search “Camera” in Start). If the Camera app shows a live picture but Teams doesn’t: Teams-specific permission or device selection is the issue. If the Camera app is also black: the hardware or system-level permissions need fixing first.
Fix 1: Windows camera privacy permissions
This is the most common cause of Teams video not working, especially after a Windows Update. Settings → Privacy and security → Camera:
- “Camera access” → On
- “Let apps access your camera” → On
- “Let desktop apps access your camera” → On (Teams requires this)
Scroll down to the app-specific list and confirm Microsoft Teams shows “On.” After enabling: close and reopen Teams completely (right-click system tray icon → Quit, then reopen) — don’t just rejoin the meeting.
Fix 2: Select the correct camera in Teams
Teams remembers the last camera it used. If that camera is disconnected, disabled, or has been replaced by a new one: Teams selects it by name even though it’s no longer available.
Teams Settings (click profile picture → Settings) → Devices → Camera → change the dropdown from the current selection to the correct active camera. If multiple cameras appear (built-in + USB webcam + virtual camera): select each one to see which shows a live preview in the preview box.
This matters especially when using USB docking stations that include a webcam, or when switching between home and office setups where different cameras are available.
Fix 3: Exclusive camera access conflict
Windows allows only one application to use the camera in certain modes. If another app (Zoom, OBS, Skype, the Camera app) has the camera open when Teams tries to access it: Teams either gets a black feed or can’t connect to the camera at all.
Close all other apps that use the camera → restart Teams → test video. The Windows Camera Frame Server manages camera sharing in Windows 11, but some older applications use exclusive access that blocks Teams.
Fix 4: Camera driver
Device Manager → Cameras (or Imaging Devices) → right-click the camera → Update driver. For built-in laptop cameras: the manufacturer’s support page has the correct driver, not Windows Update’s generic version. For USB webcams: the manufacturer’s website or Windows’ automatic detection usually works.
If the camera appears with a yellow triangle in Device Manager: right-click → Properties → check the error code. Error code 43 (USB device) means a USB power or driver issue — try a different USB port.
Fix 5: Teams version and update
An outdated Teams version sometimes has camera bugs that were fixed in a newer release. Teams menu (three dots → Help → About) shows the current version. Teams → three dots → Check for updates → apply any available update → restart Teams.
If using New Teams (2.x) and video worked better in Classic Teams: Teams Settings → General → a “Try the new Teams” toggle may let you switch back to evaluate. New Teams has improved camera handling overall, but specific hardware configurations occasionally work better with the classic version while compatibility issues are resolved.
Fix 6: Teams cache clear
Cached Teams configuration can store stale camera settings that conflict with the current hardware state. For New Teams: close Teams → navigate to %localappdata%PackagesMSTeams_8wekyb3d8bbweLocalCacheMicrosoftMSTeams → delete the Cache folder. For Classic Teams: %appdata%MicrosoftTeams → delete Cache, blob_storage, and GPUCache folders. Reopen Teams — it rebuilds fresh configuration including camera settings.
Corporate environments: camera policy
In managed Teams environments: IT can disable video for specific users or meeting types through Teams meeting policies in the Teams Admin Center. If the camera toggle is greyed out in Teams or “Video” appears unavailable in meetings: check with IT. Meeting policies are applied per-user and can be adjusted by Teams administrators.
Our guide on Windows camera troubleshooting covers the hardware and driver approach for cameras not working across all applications. For Teams audio problems that often accompany video issues, our microphone troubleshooting guide covers the Windows privacy settings that affect both audio and video. Microsoft’s Teams video documentation covers the specific minimum hardware requirements for video and the diagnostic information available at Teams → Help → Give feedback with call quality information.
Virtual backgrounds and video performance
Teams virtual backgrounds and video filters require GPU processing. If the video feed freezes or drops specifically when a virtual background is active: GPU resources are the bottleneck. Switch to “No background” or simple blur → test whether video is stable without the enhanced background effect. If it is: the GPU can’t sustain the background processing at your current video resolution or alongside other running applications.
Teams Settings → Devices → try reducing video quality (if available) or disable hardware acceleration in Teams: Settings → General → disable GPU hardware acceleration → restart. Background processing is covered in more detail in our Teams virtual background guide.
Video quality issues vs video not working
These are different problems. Completely no video: permissions, camera driver, or device selection. Poor video quality (pixelated, low resolution, laggy): typically bandwidth or system performance.
For bandwidth-related video quality: check upload speed (fast.com shows upload). Teams video calls use 300 Kbps–1.5 Mbps per participant for standard HD video. If upload is below 1 Mbps: Teams automatically reduces video quality. Limiting other applications’ upload bandwidth during calls helps — particularly cloud sync (OneDrive, Dropbox) that may be active in the background.
USB camera and power delivery
USB webcams — especially HD cameras — draw significant power. When connected through a USB hub without external power, or on USB ports with marginal power delivery: the camera initialises but produces a black or flickering image rather than failing outright. Connecting the webcam directly to the computer’s USB port (bypassing any hub) resolves this specific issue.
Camera software and OBS virtual camera conflicts
OBS Studio, Snap Camera, and similar tools create virtual camera devices that appear alongside real cameras in Teams. When a virtual camera is selected in Teams but its source application (OBS, Snap Camera) isn’t running: Teams shows a black screen from the virtual camera without an obvious error. The selected camera source has to be active and providing a feed.
Either start the source application and configure its output, or switch Teams to the real physical camera in Settings → Devices → Camera.
Hardware acceleration and rendering conflicts
Teams uses hardware acceleration for video encoding and rendering. On systems with GPU driver issues: Teams video encodes incorrectly, producing artifacts, freezing, or black screens during calls specifically (not in the preview).
Teams Settings → General → disable GPU hardware acceleration → restart Teams → join a call and test video. If video works without hardware acceleration: update the GPU driver from the manufacturer’s website, then re-enable acceleration.
Reinstalling Teams for persistent issues
When all configuration-level fixes have been tried: a clean Teams reinstall resolves state corruption that cache clearing doesn’t address. Settings → Apps → Microsoft Teams → Uninstall. For New Teams (Store version): also delete %localappdata%PackagesMSTeams_8wekyb3d8bbwe. Restart → download and install from teams.microsoft.com → sign in → test camera before joining any meeting.
Camera freeze during calls specifically (not in preview)
Camera preview works fine in Teams settings, but video freezes during actual calls. This pattern suggests the video encoding pipeline is the problem rather than camera access:
- Teams encodes video differently during calls than for preview (different codec, bitrate negotiation, packet delivery)
- Network-related encoding failures cause mid-call freezes that don’t appear in local preview
- CPU overload during calls (especially with screen sharing simultaneously) can overwhelm the encoder
If calls specifically cause freezing: check CPU usage in Task Manager during a call. If CPU hits 90%+ when video is active: close other applications, reduce screen sharing quality, or disable virtual background effects to free CPU for video encoding.
Quick diagnosis table
| Symptom | Likely cause | Fix |
| Camera app works, Teams shows black | Privacy permission or Teams device selection | Enable “Let desktop apps access camera”; reselect camera in Teams |
| Camera app also black | Driver or system-level privacy block | Enable top-level camera privacy toggle; reinstall driver |
| Black screen with virtual background active | GPU processing insufficient | Turn off virtual background; update GPU driver |
| Freezes during calls, not in preview | Network encoding or CPU overload | Reduce video quality; close background apps |
| No camera in dropdown | Driver not installed or device disabled | Device Manager → update driver; check error code |
| Camera option greyed out in meeting | IT meeting policy restriction | Contact IT Teams administrator |
Teams video troubleshooting resolves quickly once you establish whether the Camera app itself works. If it does, the issue is Teams-specific: permissions, device selection, or Teams configuration. If the Camera app doesn’t work either, the issue is system-level: driver, hardware, or Windows privacy settings. This single test cuts the investigation in half immediately.
Second camera and Teams automatic selection
When you plug in a USB webcam while Teams is running: Teams may not automatically switch to the new camera. It keeps using the previously selected one (even if that’s now a disconnected device showing black). After plugging in a new camera: go to Teams Settings → Devices → manually select the new camera rather than waiting for Teams to detect the switch.
Similarly, when unplugging a USB webcam mid-session: Teams often keeps showing the “last frame” rather than gracefully failing. Switching to a different camera in settings and back to the preferred one forces Teams to re-initialise the camera connection.
Teams Diagnostic information
During a call where video is having issues: click the three dots → Call health. This shows real-time stats including video send and receive rates, packet loss, and encoding frame rates. If video send shows 0 fps or very low rates: Teams is encoding no frames — a software or permissions issue. If it shows frames being sent but received is 0: a network issue is dropping the video packets. This diagnostic is available only during active calls and provides the fastest insight into whether the problem is local (sending) or network (delivery).
The Call health data is also useful for historical review: after a call with video problems, the call details appear in Teams → Calendar → click the past meeting → Call analytics (requires Teams admin access in enterprise environments). The analytics show exactly when video degraded during the call and what caused it, helping distinguish between one-time issues and persistent problems worth addressing.
Teams in browser vs Teams desktop app
The browser version of Teams (teams.microsoft.com) handles camera access differently from the desktop app. Browser-based camera access uses the browser’s permission system rather than Windows privacy settings. If Teams desktop has camera issues but Teams web works: the desktop app has a configuration problem. The reverse (web fails, desktop works) means the browser hasn’t been granted camera permission — click the camera icon in the browser’s address bar to grant access.
For meetings where the desktop app is misbehaving: using Teams in a browser (Chrome or Edge) is a reliable fallback for the session while the desktop issue is investigated. Browser Teams supports most meeting features including screen sharing and virtual backgrounds, with slightly less performance than the native app.
Background noise suppression and video interaction
Teams’ noise suppression feature processes audio in real time. High noise suppression combined with active video encoding increases CPU demand significantly. On lower-powered machines: the combined CPU load causes video frame drops even when the camera itself is working correctly. Teams Settings → Devices → Noise suppression → reduce from “High” to “Low” or “Auto” when experiencing video quality issues alongside audio. The CPU reduction often stabilises video frame rates.
During video calls, Teams also runs echo cancellation, automatic gain control, and background blur alongside video encoding — each contributing to CPU usage. Resource management becomes important on machines with 4 or fewer CPU cores or less than 8 GB RAM running Teams with multiple features active simultaneously. See also Teams Virtual Background Not Working for a related case.
