How to test mic and camera before a Microsoft Teams meeting
There are two pre-call checks worth running. The browser check is faster and works on every platform Teams runs on — the Teams built-in Make a test call exists too, but it is only in the desktop app on Windows and Mac, not the web or mobile clients. Do the browser check first; use the Teams test call only if you want to confirm round-trip audio with a recorded playback.
- 1
Open Clipy's free mic and camera test
Go to clipy.online/mic-webcam-test in any modern browser (Chrome, Edge, Safari 14.1+, Firefox). When the prompt appears, click Allow to grant the page access to your camera and microphone.
- 2
Confirm the live camera preview
Within a second you should see yourself in the live preview tile. That is the exact frame Microsoft Teams will see when you join a meeting. If the tile is black, jump to the troubleshooting section below.
- 3
Speak and watch the mic level meter
Say a few words. The audio level bar should bounce as you talk. If the bar stays flat, your microphone is muted at the OS level, blocked from the browser, or the wrong input device is selected — use the dropdown to switch.
- 4
Switch devices if you use a headset or external webcam
Use the camera and microphone dropdowns to pick the exact hardware you will use in the meeting — for example, an external Logitech webcam, AirPods, or a Yeti USB mic. The preview and level meter update instantly so you can confirm Teams will see the right devices.
- 5
Run the Teams built-in test call (optional, desktop only)
In the Teams desktop app for Windows or Mac, open Settings and more (the three dots in the top-right), choose Settings, then Devices. Under Audio settings click Make a test call. Test Call Bot guides you through recording a short message, plays it back, and shows a summary so you can fix anything the browser test missed.
- 6
Join the Teams meeting from the pre-join screen
From the Teams meeting invite, click Join. The pre-join screen shows your current camera, mic, and speaker selections with a live camera preview. Confirm the dropdowns match what you tested, toggle background blur if you need it, then click Join now.
Source: Microsoft Support, Manage your call settings in Microsoft Teams.
Why Microsoft Teams can't hear you
If your mic works in the browser test above but Teams still shows you as silent, the failure is almost always one of these four causes. Fix them in order; you will not need to reach the bottom.
Mic muted at the OS level. Windows: Settings > System > Sound > Input — check the input volume isn't at 0 and the device isn't disabled. macOS: System Settings > Sound > Input — confirm the right device is selected and the input level meter responds when you speak. An OS-level mute blocks the signal before it ever reaches Teams.
Teams has the wrong default mic selected. Open Teams > Settings and more (three dots, top-right) > Settings > Devices. Under Audio settings, set Microphone to the exact device you tested in the browser. Laptops often expose three or four inputs (built-in array, headset mic, Bluetooth, virtual mic from OBS) and Teams sometimes picks the wrong one after a reboot.
Another app holds an exclusive lock on the mic. Only one app can capture from the microphone at a time on Windows and macOS. If Zoom, Loom, OBS, a browser tab, or a meeting recorder grabbed the mic first, Teams gets silence. Quit the other app fully (check the system tray and the menu bar — not just the visible window), then reopen Teams.
IT admin policy or app permission block. On managed devices, an IT admin policy can block microphone access for Teams or for specific apps. Windows: Settings > Privacy > Microphone — confirm Microsoft Teams is allowed. macOS: System Settings > Privacy & Security > Microphone — confirm Microsoft Teams is ticked. If the toggle is greyed out, your IT team controls it.
Camera issues on Microsoft Teams
When Teams shows a black tile or a generic camera icon instead of your face, one of these five things is going on.
Another app is holding the camera. Only one app can read from the webcam at a time on Windows and macOS. If you keep the browser-based mic and camera test open in another tab, or Zoom is in the background, Teams sees nothing. Close anything that might have grabbed the camera, then restart Teams (Settings and more > Quit, then relaunch — the close button alone leaves Teams running).
Wrong camera is selected in Teams. Open Settings > Devices. Under Camera, you should see a small live preview of the selected device. If the preview is black or shows the wrong feed, click the dropdown and pick the correct webcam (built-in FaceTime camera, Logitech C920/Brio, external 4K cam, etc.).
Virtual camera not detected. OBS Virtual Camera, Snap Camera, Nvidia Broadcast and similar virtual cams have to be running before you open Teams. If you start them after Teams is launched, the dropdown won't see them. Quit Teams completely, start the virtual cam, then reopen Teams.
Hardware accelerated GPU encoding glitch. On some Windows laptops a stale hardware acceleration state hands Teams a frozen frame. Settings > General > scroll to Application — toggle Disable GPU hardware acceleration (requires restarting Teams) off and back on. Counterintuitive but it clears the cached encoder state.
Laptop privacy shutter is closed. Physical webcam covers are common on ThinkPads, Framework laptops, some Dell XPS models, and any MacBook with a third-party privacy sticker. The browser test will fail too if the shutter is closed, so this is easy to spot — the camera dropdown shows the device but the preview stays black.
Why a browser check works for Teams
Microsoft Teams reads from the same OS-level camera and microphone the browser does. On macOS that is the AVCapture subsystem; on Windows it is the Windows Media Foundation pipeline. When the browser's WebRTC getUserMedia call returns a working MediaStream, Teams calling that same API gets the same stream — modulo per-app permission toggles, which are easy to spot once you know to check.
That is why the 30-second browser test catches almost every hardware-level Teams problem before the meeting starts. The Teams-specific surface to verify on top is just the in-app device picker at Settings > Devices and the operating system permission for Microsoft Teams itself (Windows Privacy settings, macOS Privacy & Security).
The Teams built-in test call, explained
Microsoft ships a feature called Make a test call inside the Teams desktop app. The path is Settings and more (the three dots in the top-right) > Settings > Devices > Audio settings > Make a test call. A bot called Test Call Bot picks up, asks you to record a short message, plays it back, and shows a summary of how your mic, speaker, and camera performed.
Two things to know. First, this feature is not available in Teams on the web and not available in Teams mobile — only the desktop client on Windows and Mac. Second, Microsoft says the recording is deleted immediately after the call, so nothing is retained on their side.
When to use it: when you want round-trip playback (hear yourself the way the other person will hear you, including any echo or room noise) and not just a level meter. When to skip it: when you are on Teams on the web or mobile, or when you just need a fast yes/no on whether the hardware is alive — use the browser check then.
Privacy: nothing is recorded or uploaded
The Clipy mic and camera test runs entirely in your browser. Camera frames render straight from the MediaStream into a <video> element on the page — no MediaRecorder, no canvas capture, no upload. The mic audio is analyzed locally by a Web Audio AnalyserNode to draw the level meter and then dropped. You can open the browser network tab and watch zero requests go out while the test is running.
When you close the tab, the browser releases the camera and microphone automatically. Your webcam indicator light turns off. No background process keeps the device open.