Only 8 spots left$15 $2/seat/month for life for the next 8 founding teams.Claim your spot →

Glossary

What is WebRTC?

WebRTC (Web Real-Time Communication) is the open standard that lets web browsers and apps send live audio, video and data directly, with no plugin or download. It is what makes a phone call from a browser tab possible: the browser captures the microphone, encrypts the audio and streams it to a voice provider, which connects it to ordinary phone numbers. Chrome, Edge, Firefox and Safari all support it.

Updated · Reviewed by Jaffar Jawed

Key takeaways

  • WebRTC became an official W3C Recommendation and IETF standard in January 2021.
  • WebRTC encrypts all media; audio travels over SRTP with keys exchanged through DTLS.
  • WebRTC does not define signaling: each app or provider decides how two ends find each other and set up the call.
  • On Twilio, the browser (Voice SDK) leg of a call costs $0.004 a minute on top of the phone leg (US pricing, checked November 2026).

What is WebRTC (Web Real-Time Communication)?

WebRTC (Web Real-Time Communication) is the open standard that lets a browser send and receive live audio and video without a plugin, and it is two things: a set of JavaScript APIs in the browser, specified by the W3C (W3C WebRTC), and a set of network protocols specified by the IETF. The main APIs are getUserMedia, which asks for the microphone or camera, RTCPeerConnection, which carries the audio and video, and RTCDataChannel, which carries arbitrary data. Google released the first open-source implementation in 2011, and the specifications became formal standards in 2021 (web.dev announcement).

For voice, WebRTC handles the hard parts of real-time audio in the browser: echo cancellation, noise suppression, jitter buffers that smooth out uneven packet arrival, and codecs such as Opus that adapt to the connection. A web page only has to request the microphone and open a connection; the browser does the rest, which is why browser softphones need no installation.

How does WebRTC work for phone calls?

A WebRTC call starts with signaling, an exchange of messages that describe each side’s codecs and network addresses in a format called SDP. WebRTC leaves signaling to the application, so voice providers use their own, often WebSockets carrying SIP or a proprietary protocol. Next comes ICE: each side gathers candidate addresses, asks a STUN server for its public address, and, if a firewall blocks direct paths, relays media through a TURN server. Once a path works, encrypted audio flows over SRTP.

For calls to phone numbers, the other end of the WebRTC connection is not a person but a media gateway run by the voice provider. The gateway converts the browser’s Opus audio to the codec the phone network uses and places the call on the public network. That is why a browser call has two legs, the browser leg and the phone leg, and why providers such as Twilio price them separately.

How is WebRTC different from SIP and a regular phone line?

WebRTC, SIP and the public phone network are layers that often appear in the same call. The table shows where each fits.

Where WebRTC fits next to SIP and the phone network
TechnologyWhat it isWhere it runsEncryptionTypical role in a sales call
WebRTCBrowser standard for real-time mediaBrowsers and appsRequired (DTLS-SRTP)Carries the rep’s voice from the browser to the provider
SIPSignaling protocol for VoIP calls (RFC 3261)Phone systems, desk phones, SIP trunksOptional (TLS and SRTP)Connects phone systems and carriers
Public phone networkCarriers’ network of mobiles and landlinesCarrier switchesVariesCarries the call to the lead’s phone

What WebRTC call problems are common?

When a browser call fails, the cause is usually the device, the network or a permission rather than WebRTC itself, so these checks fix most problems without the provider’s help.

  • No audio either way: the microphone permission was blocked for the site, or another app holds the microphone.
  • Calls connect but one side is silent: a firewall or VPN blocks UDP media, and no TURN relay is available.
  • Robotic or choppy audio: packet loss or jitter on Wi-Fi; a wired connection usually fixes it.
  • Echo: laptop speakers feed back into the microphone; use a headset.
  • Calls drop when the laptop sleeps or the tab is discarded to save memory.

Is WebRTC secure?

Yes, by design. The standard does not allow unencrypted media: audio and video are encrypted with SRTP using keys negotiated over DTLS, and browsers only give pages access to the microphone over HTTPS and with the user’s permission. The encryption covers the path from the browser to the other WebRTC endpoint, which for phone calls is the provider’s gateway. From there the call joins the public phone network like any other call, so account security and the provider’s practices also matter.

When is WebRTC calling not the right fit?

Browser calling depends on a computer with a working microphone, a stable connection and an open tab. It suits reps at a desk and teams that want nothing installed. It suits field staff poorly, as well as sites with weak internet and workflows that must ring when no computer is on; those need a mobile app, call forwarding or a carrier line. Mobile browsers are another limit: providers often support only some of them for calling, so check before relying on a phone’s browser.

How does WebRTC (Web Real-Time Communication) relate to Rapidialer?

Rapidialer is a web dialer built on Twilio’s Voice JavaScript SDK, which uses WebRTC. Reps call from a desktop browser with nothing to install, inbound calls ring on any page of the web app, and the Chrome extension makes and answers single calls beside other sites. Twilio bills the browser leg at $0.004 a minute and the phone leg at $0.014 to your own account; see Twilio’s cost per minute. The Twilio softphone page covers setup, and there are no native mobile apps.

WebRTC (Web Real-Time Communication): questions and answers

Do I need to install anything to use WebRTC?

No. WebRTC is built into current versions of Chrome, Edge, Firefox and Safari, so a web page can use it directly. The only step is granting the site permission to use your microphone, and camera for video, the first time. Apps on desktops and phones can also include WebRTC libraries, but for browser calling there is nothing to download.

Is WebRTC the same as VoIP?

WebRTC is one way of doing VoIP. VoIP is the broad idea of carrying voice over internet protocols; WebRTC is a specific standard that brings real-time audio and video into browsers and apps. A browser softphone uses WebRTC to reach a provider, and the provider may then use SIP and the phone network to complete the call, which are other VoIP pieces.

Can WebRTC call regular phone numbers?

Not on its own. WebRTC connects browsers and apps to each other or to servers. To reach a mobile or landline, the browser connects to a voice provider’s gateway, such as Twilio’s, which places the call on the public phone network. The provider supplies the phone number people see and bills for the phone leg of the call.

How much bandwidth does a WebRTC voice call use?

Very little. The Opus codec most browsers use for voice runs well at tens of kilobits per second, and adapts down on poor connections. What matters more is a steady connection: high latency, jitter or packet loss hurt call quality long before bandwidth runs out, so a wired connection or strong Wi-Fi is better than raw speed.

What are STUN and TURN servers?

They help WebRTC connections cross home and office routers. A STUN server tells a browser what public address it appears from, so the two ends can try a direct path. A TURN server relays the media when a direct path is blocked, for example by a strict firewall. Voice providers run both for their customers, so users never configure them.

Does WebRTC work on mobile phones?

Mobile browsers support WebRTC, and many apps use it inside. Browser calling on phones is less reliable than on desktops, though: tabs are paused in the background, and incoming calls cannot ring a closed browser. Voice providers often list which mobile browsers they support, and most offer native mobile SDKs with push notifications for calling apps.

Start today

Import your list and make your first call today

Connect Twilio, upload a CSV and start dialing.