Browser-based video calling feels almost unremarkable now — click a link, grant camera access, talk to someone. The technology making that possible without installing anything is called WebRTC, and it's worth understanding at a basic level, both because it's genuinely interesting and because it explains why video chat behaves the way it does.
WebRTC (Web Real-Time Communication) is an open standard, developed jointly by the W3C and the IETF, that lets browsers exchange audio, video, and data directly with each other — no plugin, no separate app, no download. Every major browser supports it natively: Chrome, Safari, Firefox, and Edge. Before WebRTC existed, real-time browser communication generally required something like Flash or a separate downloaded client, both of which carried their own security and compatibility headaches.
Here's a detail that surprises people: WebRTC itself doesn't include a built-in way for two browsers to actually find each other. That part, called signaling, has to be built separately, typically using WebSocket or a similar connection, to pass along the technical details — codecs, network information — needed before a direct connection can start. This is a deliberate design choice, not an oversight: it keeps WebRTC flexible enough to work across very different kinds of applications, from video chat to file sharing to live streaming, each of which can build whatever signaling approach fits its own needs.
Most devices sit behind a router or firewall that hides their real network address from the open internet, which creates a real problem: how do two browsers find a path to each other if neither one has a directly reachable address? WebRTC solves this with a process called ICE (Interactive Connectivity Establishment), which tests several possible paths and picks the best one.
Helps a device discover its own public-facing address, so the other side knows where to send data.
Acts as a relay for the rare cases where a direct connection genuinely can't be established — certain strict firewalls, for instance.
Under normal conditions, the connection ends up genuinely peer-to-peer once ICE finishes its work. TURN exists specifically as a fallback for the cases where that's not possible, not as the default path. We go into this in more depth, including the one honest exception worth knowing about TURN, in our guide to how P2P video calling actually works.
Security in WebRTC isn't a setting you can turn off — it's built into the standard itself. Every connection uses DTLS (Datagram Transport Layer Security) and SRTP (Secure Real-Time Transport Protocol) to encrypt audio, video, and data. An unencrypted WebRTC connection simply isn't possible by the standard's own design, which is a meaningfully different guarantee than an app that encrypts by policy but could technically choose not to.
Even a delay of a few hundred milliseconds is noticeable in conversation — it shows up as talking over each other, an odd pause before a response, or video that feels slightly out of sync with audio. Because WebRTC routes media directly between two devices rather than through a central server most of the time, there's simply less distance for the data to travel, which is a meaningful part of why browser-based video calling can feel as immediate as it does.
The same direct-connection design that helps latency also has a real privacy implication: when video travels directly between two devices rather than through a central server, there's nothing for that server to store, even if it wanted to. This isn't a policy choice that could be quietly reversed — it's a property of how the connection is built. It's worth being precise about what this does and doesn't guarantee, though, since the privacy benefit is architectural rather than purely cryptographic — we cover that distinction honestly in our encryption details guide.
WebRTC isn't unique to random video chat — it's the same underlying technology behind telemedicine consultations, virtual classrooms with screen sharing, in-browser customer support widgets, and most video calling features built directly into a website rather than a separate app. The same handful of building blocks (signaling, ICE, STUN/TURN, DTLS-SRTP) show up across all of them, just assembled differently depending on what the application actually needs.
One detail worth knowing if you've ever noticed video quality shift mid-call without you doing anything: WebRTC is built to adapt automatically to whatever bandwidth is actually available, lowering resolution and detail rather than letting the call drop entirely when a connection gets weaker. This is deliberate — a slightly blurrier picture that stays connected is more useful than a sharp one that keeps failing. We go into this in more depth, including a genuinely useful trick about backgrounds that actually helps on a weak connection, in our guide on improving video quality on a weak connection.
It's worth being honest about the difference between established, current technology and reasonable future speculation. Everything described above — signaling, ICE, STUN/TURN, mandatory encryption — is how WebRTC works today, not a future aspiration. Looking ahead, broader 5G availability should continue improving mobile video quality generally, and ongoing improvements to video compression are a genuinely active area of work across the industry. Treat anything framed as a future trend as industry-wide speculation rather than a specific feature any particular platform has built — that distinction matters more than it might seem.
None of this needs to be understood to actually use video chat — the entire point is that it works invisibly in the background every time a call connects. But knowing roughly how it works explains a few things that otherwise seem mysterious: why certain strict networks cause connection trouble, why encryption is a given rather than a feature to advertise, and why no app download is needed for any of it to function. If you're curious about the connection side specifically, including what happens when it doesn't go smoothly, our connection errors guide covers that in practical detail.