Browser meeting microphone not working: permissions and checks
Denied mic permission is the usual reason voice never starts. Allow the site, wear headphones, close extra tabs.
You joined a no-login room. Cursors move and the board updates, but peers hear silence. Treat that as a capture failure, not a wrong room ID.
People searching browser meeting microphone not working often already clicked Allow, or opened the link inside a chat app. Check site permission, the current input device, and whether a second page is recording.
Why voice fails before the picture
Browser-meeting audio is local capture, then WebRTC. Permission, device contention, and in-app browsers beat “the room is broken.”
Site permission denied
Allow the microphone for this site when prompted. After a deny, change the lock-icon setting and reload. That is the most common reason voice never starts.
In-app browsers
Embedded windows from chat apps often block getUserMedia. Copy the link into standalone Chrome, Edge, Firefox, or Safari.
A second page is recording
Another meeting tab, a recorder, or a system app holding the same mic causes silence or echo. Keep one room open. Prefer headphones.
Fix capture first, then the network
Give this tab the microphone, then decide if the problem is echo or no connection.
-
1
Allow, then reload the room
In the lock icon, set the microphone to Allow for figmeet. Reload after any change. An existing session will not rebind the device by itself.
-
2
Headphones, and stop double capture
Headphones cut echo. If you hear yourself, close other tabs or apps that might hold the mic. Leave only this room.
-
3
Standalone browser; switch network if needed
Skip in-app browsers. If it is still fully silent, try a phone hotspot or disable the VPN to test WebRTC. Limits are on the features page.
Match the symptom before you recreate the room
| Symptom | Check first | On figmeet |
|---|---|---|
| Nobody hears anyone | Site microphone permission | Allow, then reload |
| Echo or you hear yourself | Headphones and other live tabs | Voice first; cameras optional |
| Allowed, still fully mute | In-app browser, VPN, firewall | Switch browser or network |
A working room ID is not an open microphone
After you create or join on figmeet, the browser asks for the mic. A custom ID such as sprint-sync only decides who enters. It does not replace permission. Steps: guide. Caps: features.
# Site settings
Microphone: Allow
Then reload the room
Let this tab own the microphone before you blame the firewall. Most silence stops at permission or a second capture tab.
- Permission
- It is per site, not per room ID. After a new device or cleared site data, Allow again.
- WebRTC
- Media is peer-to-peer or relayed. If permission is fine and everyone is mute, then try VPN and the corporate network.
Still silent?
I already clicked Allow. Why is it still dead before reload?
The live session does not rebind the device. After a permission change, reload or rejoin the room.
Can I fix this on a phone browser?
Joining and talking work. Keep the tab in the foreground and allow the browser to use the microphone in system settings.
Does figmeet offer phone dial-in?
No. Meetings that need PSTN stay in an enterprise suite. Browser rooms only capture from the page.
Video works but voice does not. Is that the camera cap?
The camera cap limits video seats. Silence still starts with microphone permission and whether another tab holds the device.