What Is WebRTC?
WebRTC lets browsers set up real-time peer-to-peer audio, video and data connections without a plugin — using signaling and ICE candidate gathering rather than routing every call through one central server.
WebRTC privacy guides covering ICE candidates, STUN, browser behavior, VPN leaks, and practical tests.
WebRTC lets browsers set up real-time peer-to-peer audio, video and data connections without a plugin — using signaling and ICE candidate gathering rather than routing every call through one central server.
WebRTC lets your browser learn its own public IP address for real-time features like video calls — and under the wrong conditions, a page can read that address even through a VPN.
WebRTC's ICE candidate-gathering process learns your public address by design — modern browser protections limit what a page can extract from that process, but don't eliminate the underlying exposure entirely.
A WebRTC leak test compares every address your browser's real-time connection feature reveals against your actual HTTP exit IPs — here's how to run one and read the result.
Before disabling WebRTC entirely over leak concerns, check specifically whether the exposed address actually bypasses your VPN tunnel — many results that look alarming turn out to be expected or easily fixed with a narrower change.
WebRTC privacy behavior has changed meaningfully across browser versions — mDNS masking, tightened permission models, and evolving relay policies mean older assumptions about WebRTC exposure may no longer apply.
STUN servers let a browser learn its own public-facing address for connection setup — a narrow, specific job that doesn't relay the actual call media itself.
Distinguishing an expected VPN exit candidate from an unexpected ISP-assigned one is the key skill for reading a WebRTC leak test result correctly.
Testing directly, rather than relying on outdated flag-based instructions, is the reliable way to check Chrome's current WebRTC leak behavior — which is shaped by extensions, enterprise policy, and VPN interaction, not a fixed setting.
Firefox offers more direct, built-in privacy controls over WebRTC than some other browsers — testing first clarifies whether you actually need to use them.
Edge is Chromium-based and shares much of Chrome's WebRTC behavior, but enterprise policies, extensions and OS-level network paths specific to Edge deployments can still produce different results.
Safari's WebRTC privacy story includes a distinctive piece — iCloud Private Relay — with its own boundaries and interaction with VPN routing worth understanding separately from other browsers.