How to Disable WebRTC on Chrome (2026)

WebRTC can expose your real IP address even when you’re connected to a VPN. Chrome doesn’t give you a built-in toggle to disable it, but a couple of extensions fix the problem in under a minute.

Here’s what works.

---

Why WebRTC leaks matter

WebRTC is the browser technology that powers in-browser video calls, voice chat, and file sharing. It works by establishing direct peer-to-peer connections — and to do that, it needs to know your real IP address. The problem is it can hand that IP to websites even when your VPN is active, bypassing the tunnel entirely.

This is a WebRTC leak. It’s one of the most common ways VPN users unknowingly expose their real location.

---

Method 1: WebRTC Leak Prevent extension

The most targeted fix — blocks WebRTC leaks without disabling the technology entirely.

1. Open Chrome and go to the Chrome Web Store.
2. Search for WebRTC Leak Prevent.
3. Click Add to Chrome and confirm the install.
4. The extension runs automatically — no configuration needed.

This keeps WebRTC functional for video calls while blocking the IP exposure. Best option if you use Google Meet, Teams, or any browser-based calling in Chrome.

---

Method 2: uBlock Origin

If you already have uBlock Origin installed, you can block WebRTC leaks from within it without adding another extension.

1. Click the uBlock Origin icon in your toolbar.
2. Open the Dashboard and go to the Settings tab.
3. Check Prevent WebRTC from leaking local IP addresses.

Same result as above — leak blocked, WebRTC still functional.

---

Verify it worked

Go to veilock.com/webrtc-leaks/ with your VPN connected and run the test. If no real IP appears in the WebRTC section — or only your VPN’s IP shows — the leak is closed.

Run this again after any Chrome update. Updates occasionally reset extension permissions or browser behavior worth confirming.

---

A note on Chrome vs Firefox

Chrome doesn’t let you disable WebRTC at the browser level — there’s no equivalent to Firefox’s about:config toggle. Extensions are the only route. If you want a no-extension solution, Firefox lets you disable WebRTC completely in about 30 seconds through its settings. Worth knowing if you’re flexible on browser choice.

---

How Veilock handles WebRTC

Veilock blocks WebRTC leaks at the network level, so your real IP can’t be exposed through browser-based WebRTC requests regardless of which browser you’re using. Combined with an extension, you get two independent layers — neither relying on the other.

Test your WebRTC leak

---

Common questions

Does disabling WebRTC break video calls in Chrome? The extensions above block IP leaks without disabling WebRTC entirely, so browser-based video calls continue to work. If you fully disabled WebRTC, tools like Google Meet would stop functioning.

Why can’t I disable WebRTC in Chrome settings directly? Chrome doesn’t expose a WebRTC toggle in its settings UI. Google has historically resisted adding one. Extensions are the supported workaround.

Does my VPN protect against WebRTC leaks automatically? Not all VPNs do. Some handle WebRTC at the network level, others don’t. Veilock does. If you’re unsure about your current provider, the leak test at veilock.com/webrtc-leaks/ will tell you immediately.

Do I need to redo this after Chrome updates? Occasionally. Extensions generally persist across updates, but it’s worth running the leak test after major Chrome version updates to confirm everything’s still working.

Does this work on Chrome for Android? Chrome for Android doesn’t support extensions, so the methods above don’t apply. On Android, using a VPN that handles WebRTC at the network level — like Veilock — is the practical solution.