Enable WebRTC by allowing camera and microphone access in the browser, then confirm that WebRTC is not blocked in advanced settings or extensions. Chrome makes this mostly a site-permission issue. Firefox gives you a clearer master switch through about:config, which is useful when video calls refuse to start for no obvious reason.
TLDR: In Chrome, open site settings and allow the camera and microphone for the calling website. In Firefox, make sure media.peerconnection.enabled is set to true, then approve camera and microphone prompts. For example, if a 20-person sales team has 6 users unable to join a WebRTC meeting, the fix is often browser permissions in Chrome, while Firefox problems are more likely tied to a disabled WebRTC preference or privacy add-on.
What WebRTC Does
WebRTC stands for Web Real-Time Communication. It lets websites run voice calls, video meetings, screen sharing, live support chat, and peer-to-peer data transfers without a separate desktop app.
Google Meet, Discord web calls, Slack huddles, telehealth portals, interview platforms, and customer support tools often depend on it. If WebRTC is disabled, blocked, or starved of permissions, the result is familiar and annoying: black video, silent audio, endless “connecting” messages, or a meeting page that simply gives up.
Chrome WebRTC Settings Explained
Chrome does not offer a simple “WebRTC on/off” button in regular settings. That drives people crazy, because a failed call feels like it should have one obvious fix. In most cases, WebRTC is already enabled in Chrome. What blocks it is usually a camera permission, microphone permission, blocked pop-up, VPN rule, extension, or company policy.
How to Enable WebRTC in Chrome
- Open Chrome.
- Go to the website that needs WebRTC, such as your meeting or support platform.
- Click the lock icon or site controls icon near the address bar.
- Select Site settings.
- Set Camera to Allow.
- Set Microphone to Allow.
- Return to the website and reload the page.
You can also check global permissions:
- Open Settings.
- Go to Privacy and security.
- Select Site settings.
- Open Camera and choose the correct device.
- Open Microphone and choose the correct device.
- Review the list of blocked sites and remove the website if needed.
If Chrome asks for permission and you click Block, the browser remembers that choice. That single click can waste 10 minutes during a call setup. Always check the blocked list before reinstalling anything.
Chrome Flags and Enterprise Restrictions
Most users should not need Chrome flags to enable WebRTC. In managed workplaces, however, an administrator may use policies that restrict media access, screen sharing, or WebRTC network behavior. If the browser says “managed by your organization,” personal settings may not be enough.
Extensions can also interfere. Privacy extensions, script blockers, ad blockers, and VPN extensions may block peer connections or device access. Test in an incognito window with extensions disabled, or use a fresh Chrome profile. If WebRTC starts working there, the browser itself is not the real problem.
Firefox WebRTC Settings Explained
Firefox handles WebRTC differently. Like Chrome, it uses camera and microphone permissions. Unlike Chrome, it also exposes a direct WebRTC preference in advanced settings. This makes Firefox easier to diagnose when WebRTC has been switched off on purpose.
How to Enable WebRTC in Firefox
- Open Firefox.
- Type about:config in the address bar.
- Accept the warning if it appears.
- Search for media.peerconnection.enabled.
- Make sure the value is set to true.
- If it is set to false, click the toggle button to change it.
- Restart Firefox if the site still fails to detect WebRTC.
After that, check site permissions:
- Open the WebRTC website.
- Click the lock icon in the address bar.
- Review camera and microphone permissions.
- Remove any blocked permission.
- Reload the page and approve the browser prompts.
Firefox also has strict privacy controls. Some users disable WebRTC to reduce IP address exposure. That choice can be reasonable, but it will break browser-based calls. If you need both privacy and WebRTC, use a reputable VPN, keep Firefox updated, and test the service before an actual meeting.
Chrome vs Firefox: Key Differences
| Feature | Chrome | Firefox |
|---|---|---|
| Default WebRTC status | Usually enabled | Usually enabled |
| Main control point | Site permissions | Site permissions plus about:config |
| Master WebRTC switch | No simple regular setting | Yes, through media.peerconnection.enabled |
| Common blocker | Blocked camera or microphone | Disabled preference or privacy extension |
| Best quick test | New profile or incognito mode | Check about:config first |
The practical difference is simple. In Chrome, assume WebRTC is on and check permissions first. In Firefox, check the WebRTC preference first if nothing works at all, then check permissions.
How to Test Whether WebRTC Works
Use a trusted WebRTC test page or the diagnostics page provided by your meeting platform. Check three things:
- Camera detection: The correct webcam should appear.
- Microphone detection: The input meter should move when you speak.
- Peer connection: The browser should create a successful connection.
If the camera works but the peer connection fails, the issue may be a firewall, VPN, proxy, or corporate network rule. If nothing is detected, the issue is more likely browser permissions, operating system permissions, or a device driver.
Do Not Forget Operating System Permissions
Browser settings are only one layer. Windows, macOS, Android, and iOS also control camera and microphone access. A browser may be allowed inside Chrome or Firefox but blocked by the operating system.
- On Windows, check Settings > Privacy & security > Camera and Microphone.
- On macOS, check System Settings > Privacy & Security.
- On Android, check the browser app permissions.
- On iPhone or iPad, review browser permissions in iOS settings, though browser behavior may be limited by Apple’s WebKit rules.
Privacy and IP Address Concerns
WebRTC can reveal network information needed to create real-time connections. Modern browsers have added protections, including local IP masking methods, but privacy concerns still exist. This matters for users who rely on VPNs, proxy tools, or strict network separation.
If privacy is a serious requirement, avoid random “WebRTC leak fix” extensions from unknown publishers. Use browser settings, trusted VPN software, and documented enterprise policies. Bad extensions can create more risk than WebRTC itself.
Fast Troubleshooting Checklist
- Reload the website after changing permissions.
- Confirm the correct camera and microphone are selected.
- Remove the site from the browser’s blocked list.
- Disable privacy or script-blocking extensions for a test.
- Try a private window or a clean browser profile.
- Check operating system camera and microphone permissions.
- In Firefox, confirm media.peerconnection.enabled is true.
- Ask IT about firewall or managed browser policies if you are on a work device.
Chrome is best treated as permission-driven, while Firefox gives you both permissions and a direct WebRTC switch. If you need the fastest fix, start with the site’s camera and microphone access. If Firefox still fails, check about:config. If Chrome still fails, suspect extensions, managed policies, or the network before blaming WebRTC itself.
