WaveTalkStart talking

Blog

How Does Random Voice Chat Work? A Plain Explanation

By the WaveTalk Team · October 10, 2026 · 4 min read

Short answer: you join a waiting queue, a server pairs you with someone else waiting, the two browsers exchange connection details through that server, and then audio flows between them — either directly, or through a relay that hides both addresses. The whole thing takes two or three seconds.

Here is each step, in plain terms.

1. You join a queue

Pressing Start puts you in a pool of people also waiting. The server holds that pool and looks for a pair.

Filters narrow who you can be paired with. Interests match against what the other person chose; a country filter restricts by where they are. Narrower filters mean better matches and longer waits — that trade is unavoidable and no site has solved it.

2. The server pairs two people

This is just matchmaking: two compatible people waiting, paired, told about each other. The server does not carry your audio at this stage. Its job is introductions.

What it knows about you is worth asking any site. A well-built one needs almost nothing: a temporary id, your country, your chosen interests. It does not need a name, an email or a phone number to pair two people.

3. The browsers negotiate a connection

This is WebRTC, the technology browsers use for real-time audio. Each side gathers a list of addresses it can be reached on — its "ICE candidates" — and sends the list to the other through the signalling server.

This is the step where privacy is decided, and most people never hear about it. That list of addresses includes your public IP. If the two browsers then connect directly, each one holds the other's address, and any browser's WebRTC debug page will display it. No hacking involved; it is how the protocol works when nobody intervenes.

4. Audio flows — directly, or through a relay

Two possibilities, and the difference is the whole privacy story:

Direct (peer-to-peer)Relayed (TURN)
Who sees your IPThe other personThe relay operator only
What they can inferYour city, your ISPNothing about you
LatencyLowestA few ms more
Cost to the siteAlmost nothingBandwidth, every minute
Common defaultYesNo — it has to be chosen and paid for

A TURN server sits in the middle and forwards the audio, so neither side ever learns the other's address. It costs real money per minute of every call, which is why sites that do it tend to say so and sites that do not tend to say nothing. More on what that exposes.

The audio itself is encrypted with DTLS-SRTP, which is part of WebRTC rather than an add-on. That means a relay forwards packets it cannot listen to.

5. Skipping starts the loop again

Pressing End tears down the connection and drops you back into the queue. Nothing about the previous call persists unless the site chose to store it — which, again, is a choice. On a site that stores nothing, the conversation genuinely stops existing when it ends.

Why there is no app

Everything above runs in a browser. WebRTC is built into Chrome, Safari, Firefox and Edge, so a random voice chat site needs no download, no app store and no install. A site that insists on an app is choosing that for other reasons — usually notifications, or an identity to attach to you.

What this means when you pick a site

Four questions, all answerable in a couple of minutes:

  1. Does it relay calls? The single biggest privacy difference, and it is

invisible unless the site states it.

  1. What does it need to pair you? Anything beyond a country and some

interests is being collected for another reason.

  1. Does anything persist after the call? Silence on this is an answer.
  2. Does it work in the browser? If not, ask why not.

WaveTalk relays every call through Cloudflare, so the person you talk to never sees your IP address, and keeps nothing: no account, no recording, and chat messages gone when the call ends.

Related

Questions people ask

How does random voice chat work?

You join a waiting pool, a matchmaking server pairs you with someone else waiting, the two browsers exchange connection details through that server, and audio then flows between them — either directly or through a relay. It takes two or three seconds and needs no app, because WebRTC is built into every modern browser.

Can the other person see my IP in a random voice chat?

On a direct peer-to-peer connection, yes — WebRTC hands each side the other's address while setting up the call, and that reveals their city and internet provider. On a site that routes calls through a TURN relay, no: the only address either side sees belongs to the relay.

Do random voice chat sites need an app?

No. WebRTC is built into Chrome, Safari, Firefox and Edge, so these sites run in a browser with nothing installed. A site that requires an app is choosing that for other reasons, usually notifications or a persistent identity.

How do chat sites decide who you talk to?

A server holds everyone currently waiting and pairs two compatible people. Interests match against what the other person selected, and country filters restrict by location. Narrower filters produce better matches and longer waits.

Is random voice chat encrypted?

The audio is, by default — WebRTC uses DTLS-SRTP, which is part of the protocol rather than a feature on top. That holds even on relayed calls: the relay forwards packets it cannot listen to.