WebRTC is the technology that powers browser video calls (Google Meet, Discord, WhatsApp Web). It's useful — but by design it can reveal your real IP address to any website, bypassing your VPN. Here's how to test for a leak and shut it down.

Why WebRTC leaks your IP

To connect peers directly, WebRTC asks a STUN server "what's my IP from your perspective?" The answer comes back as a JavaScript variable the page can read. This happens before your VPN sees the traffic in some configurations, so even a connected VPN can fail to mask it.

How to test

Connect your VPN. Visit any WebRTC leak test site (browserleaks.com/webrtc is solid). Compare the IPs the page detects with your real IP from our IP checker (run without VPN first to know your real one). If the WebRTC page shows that real IP while VPN is connected, you're leaking.

Fix in Firefox

Visit about:config, search media.peerconnection.enabled, set it to false. This fully disables WebRTC. Video calls in Firefox will break — re-enable when you need them.

Fix in Chrome, Edge, Brave

These Chromium browsers don't have a direct toggle. Install WebRTC Network Limiter (Google's own extension) and set it to "Use my proxy server." Brave has a built-in setting: brave://settings/privacy → WebRTC IP handling policy → Disable non-proxied UDP.

Fix in Safari

Safari exposes fewer WebRTC leaks by default. For extra safety: Develop menu → WebRTC → uncheck Enable Legacy WebRTC API. Enable the Develop menu first in Settings → Advanced.

Try it now

Curious what your IP is showing the world right now? Check your IP address & location instantly with our free tool — no signup, nothing stored. Or trace any other IP to see its geolocation, ISP, and network details.