Why turning off WebRTC breaks video calls
Learn why blocking WebRTC can stop browser calls, how to restore camera and audio access, and how to check for a VPN-related IP leak.
You turned off WebRTC to protect your privacy, and now a browser video call will not connect, or its audio and video keep dropping. The two problems can be related: many browser calling services use WebRTC to send live audio and video.
You can check whether a WebRTC restriction is involved, restore the browser features the call needs, and still investigate whether your VPN exposes your real IP address. The VPN Leak Test checks for real IP leaks through WebRTC or IPv6 while a VPN is connected. It does not test call quality.
Check whether a WebRTC restriction is causing the call problem
- Connect your VPN if you use one, then open the VPN Leak Test. Run the check and note whether it reports a real IP leak through WebRTC or IPv6.
- Think about what changed before calls stopped working. Check privacy extensions, browser settings, and VPN settings for an option that blocks or limits WebRTC. The setting name and location depend on the product.
- In the browser, open the site controls beside the address bar and check whether the calling page is allowed to use the camera and microphone.
- If you find a WebRTC restriction, temporarily allow WebRTC for the calling page or turn off that restriction briefly. Reload the page and try joining a call again.
- If it is safe for your situation, compare the call with the VPN connected and disconnected. Disconnecting may expose your regular internet address, so do not do this on a sensitive call or network where that matters.
Change one setting at a time and reload the call page after each change. That makes it easier to identify the cause and restore the privacy setting you need afterward.
What the results mean
The call works after WebRTC is allowed
A browser, extension, or VPN setting was likely blocking a feature the call needs. This does not mean the camera or microphone is faulty. You may be able to allow WebRTC only for the calling site instead of disabling protection everywhere.
The VPN Leak Test reports a real IP through WebRTC
Your browser exposed an address the VPN was meant to hide during the test. A restriction may reduce that exposure, but blocking WebRTC can also prevent some calls from connecting. Look for a VPN setting that protects against WebRTC leaks while still allowing calls, or contact the VPN provider for advice on its options. Do not assume that disabling your VPN is the only fix.
The test does not report a WebRTC leak
That is useful evidence for the tested browser and VPN connection at that moment. It does not prove that every app, browser, or network is leak-free, and it does not show whether a video call can connect. Keep troubleshooting the call separately.
The call still fails after you allow WebRTC
The cause may be a blocked camera or microphone permission, a network that restricts call traffic, or a problem with the calling service. A successful WebRTC check cannot confirm that your camera, microphone, or network can carry a live call.
How to fix it
- Undo the recent WebRTC block. If an extension or privacy feature has a WebRTC setting, test with it disabled or set to allow the calling site. Change only that option, then reload the call page. If the setting is managed by work or school, ask the administrator rather than trying to bypass it.
- Allow the site to use your camera and microphone. Use the site controls beside the address bar to allow both devices, then reload the page. In the call's own settings, select the camera and microphone you intend to use.
- Check operating system privacy access. In Windows 11, open Settings › Privacy & security › Camera and Settings › Privacy & security › Microphone. Turn on access for the device and allow desktop apps to access it. On macOS, open System Settings › Privacy & Security › Camera and System Settings › Privacy & Security › Microphone, then allow your browser.
- Review the VPN's WebRTC protection. A VPN may have an option to prevent WebRTC leaks, but its behavior varies. Check the provider's instructions for a setting that protects your IP without blocking browser calls. Avoid turning off the VPN's protection permanently just to make one call work.
- Restart the browser and close other call apps. Quit and reopen the browser, then try again. Another app may already be using the camera or microphone, or the browser may not have applied a changed permission until it restarted.
- Try another trusted network. If WebRTC is allowed and device permissions are correct, a router, firewall, or managed network may be blocking the traffic a call needs. If calls work on a different network, ask the network administrator about restrictions rather than changing device privacy settings at random.
Why video calls use WebRTC
WebRTC is a set of browser technologies for real-time audio, video, and data. A call uses it to find a working route between participants, sometimes directly and sometimes through a relay server. The route-finding process can involve network addresses, which is why privacy tools may restrict WebRTC to reduce IP exposure.
Turning off or heavily limiting WebRTC can stop a call from finding a route, or make it fall back to a slower or less reliable connection. A privacy tool that hides or limits address information is not necessarily the same as disabling the entire technology. The right choice depends on whether you need calls to work and what protection your VPN or browser provides.
A VPN Leak Test checks for a specific kind of IP exposure while the VPN is on. It is not a general privacy audit, and it cannot confirm that a video call is working correctly.
