Camera or microphone not working in browser meetings
Troubleshoot permission prompts, wrong input devices, and meeting tabs with no audio.
Video meetings involve several separate permission layers: the website, the browser, the operating system, and the actual camera or microphone. When a meeting app shows a black preview or silent input, jumping straight to reinstalling the browser can waste time. Work from the physical device inward, then verify which site has permission. Remember that an access request is not proof that a website is trustworthy.
Check site, browser, system, and device separately. Do not enter passwords on unverified pages or bypass browser security warnings.
Check the physical and system level
Make sure a hardware privacy shutter is open and the correct camera or microphone is connected. Check whether another application is already using or controlling the device. In system settings, confirm that the browser itself is allowed to access camera and microphone. On a work computer, administrators may restrict access. Do not install unknown “driver fixer” utilities as a shortcut.
Confirm the browser’s per-site permissions
Browsers commonly allow camera and microphone permissions per website. Inspect the exact domain in the address bar; fake meeting links are a known risk. Set permission to Ask or Allow only for the intended meeting service. In Safari on Mac, the Websites section of Safari Settings includes Camera and Microphone choices. If permission was previously denied, change it there and refresh the trusted meeting page.
Select the right input within the meeting app
The browser may have permission while the meeting software has selected the laptop microphone instead of the headset. Choose a device in the call application’s own audio settings and make a short local test. If the hardware works elsewhere but not in the browser, inspect a browser permission or profile issue. If it fails across apps, focus on the operating system or hardware.
Avoid unnecessary permission escalation
A site should not need permanent camera access merely to display an ordinary page. After a one-time session, you may return its setting to Ask. If browser extensions interfere with the meeting UI, test a clean profile or temporary reduced-extension session rather than disabling all security tools. Do not share screenshots of meetings, recordings, or private documents in public support forums.
Build a pre-meeting checklist
Before an important call, load the meeting service directly, verify the account, test audio and camera in a preview, and confirm the browser version is supported. If the service demands an update, use an official download route. Keep a phone dial-in or approved alternate device available for critical sessions; that is often a better contingency than risky emergency setting changes.
How this looks in practice
In a remote interview, the meeting platform sees the external webcam but not the microphone. The browser permission indicator is green, so the next check is the microphone selected inside the meeting settings. Switching from the laptop’s built-in mic to the connected headset resolves the problem. Clearing cookies or resetting every website permission would not have addressed the wrong-input setting.
Your short checklist
- Check hardware shutter and connection.
- Check OS permission for browser.
- Verify the meeting URL is trusted.
- Set per-site browser permission.
- Select correct input inside the app.
- Return one-time permissions to Ask later.
Official documentation and verification
These publisher links support the browser behavior and instructions discussed above. BrowserSignal’s example cases are illustrative scenarios, not claims of hands-on vendor testing.
Menu labels, software versions and policies can change. If a device is managed by an employer or school, follow its instructions. Avoid sharing passwords, tokens, or private account details with support forums.
Use the interactive Pathfinder, then record what actually fixed the issue.